@Panda if you used the Ubuntu PPA, I think this only goes as far as 6.x if I recall correctly.
NodeBB socket with CloudFlare
-
@phenomlab done
-
@DownPW Also remove these lines and restart
nginx
root /home/XXXXX/domains/socket.XXXX.fr/public_html;
index index.php index.htm index.html;
-
Same
-
I see this on start log nodebb
-
-
Thereās more of an issue here - try to change any CSS or JS in the ACP, and youāll see that it does not save.
-
???
-
@DownPW Now working for me in Incognito. Can you check
-
@phenomlab said in NodeBB socket with CloudFlare:
Thereās more of an issue here - try to change any CSS or JS in the ACP, and youāll see that it does not save.
due to socket.io configuration in nodebb config.json file
Actually I have delete socket.io block and change CSS and save is good.
-
@DownPW Ok, but that now means you should not need the socket A record anymore because itās not used. From the logs, the socket is running on the siteās URL.
-
normal that it is not used (A record) @phenomlab because there currently, I do not use it because the socket.io block is removed from config.json.
Iām just in normal mode with Cloudflare :
I can put it back if you want ?
-
@DownPW It seems to be working fine without it, so Iād leave it. I see zero socket errors, so all good.
-
because Iām alone on the server.
The goal is to try to market this method before putting it into production where i have a lot of errors
And we can see that it doesnāt work when I try to reroute the web sockets in non-proxied mode. (socket error, no save when chnage in ACP, etcā¦)
I donāt know if I can make myself understood. @phenomlab
-
@DownPW Understood. Even with just the two of us connected, I was still getting the websocket error, but I think that was related to config etc. In all honesty, this is yet another reason why I stopped using CF. I know you need it to hide your IP address, but if you bypass CF for the socket, you are exposing your IP anyway.
-
I know, I know,
too badā¦ I just wanted to test this method but it seems more complex than it looks to make it work correctly
The reverse proxy method is currently too expensive for me and technically too abstract
-
@DownPW itās your only realistic option at this stage.
Related Topics
-
MogoDB v6 to v7 upgrade
Solved Configure -
-
-
-
-
restarting nodebb on boot
Unsolved Configure -
-
NodeBB 1.19.3
Solved Performance