Looks like your connection to NodeBB was lost, please wait while we try to reconnect.
-
I was reading for several hours for solution through NodeBB's official forum and searching through google for answers.
I just freshly installed NodeBB v1.15.3 and now I am having issues. When I open the site it shows it without any css and has error
"Looks like your connection to NodeBB was lost, please wait while we try to reconnect."
at the bottom of the site.
From logs I saw this:
So it has 2 errors, what I understand: [cache-buster] and [socket.io]
App 26532 output: 2020-11-29T10:52:49.244Z [80/26532] - [32minfo[39m: Initializing NodeBB v1.15.3 https://foorumi.vankilapalvelin.com App 26532 output: 2020-11-29T10:52:50.663Z [80/26532] - [33mwarn[39m: [cache-buster] could not read cache buster ENOENT: no such file or directory, open '/home/vankilap/public_html/foorumi/build/cache-buster' {"errno":-2,"code":"ENOENT","syscall":"open","path":"/home/vankilap/public_html/foorumi/build/cache-buster","stack":"Error: ENOENT: no such file or directory, open '/home/vankilap/public_html/foorumi/build/cache-buster'"} App 26532 output: 2020-11-29T10:52:52.386Z [80/26532] - [32minfo[39m: [socket.io] Restricting access to origin: https://foorumi.vankilapalvelin.com:* http://foorumi.vankilapalvelin.com:* https://www.foorumi.vankilapalvelin.com:* http://www.foorumi.vankilapalvelin.com:* App 26532 output: 2020-11-29T10:52:53.248Z [80/26532] - [33mwarn[39m: [plugins/nodebb-theme-persona] The plugin.json field "library" is deprecated. Please use the package.json field "main" instead. App 26532 output: 2020-11-29T10:52:53.957Z [80/26532] - [32minfo[39m: [api] Adding 0 route(s) to `api/v3/plugins` App 26532 output: 2020-11-29T10:52:53.964Z [80/26532] - [32minfo[39m: Routes added App 26532 output: 2020-11-29T10:52:53.965Z [80/26532] - [32minfo[39m: NodeBB Ready App 26532 output: 2020-11-29T10:52:53.966Z [80/26532] - [32minfo[39m: Using ports 80 and 443 is not recommend; use a proxy instead. See README.md App 26532 output: 2020-11-29T10:52:53.969Z [80/26532] - [32minfo[39m: NodeBB is now listening on: 0.0.0.0:80
My config is currently this:
{ "url": "https://foorumi.vankilapalvelin.com", "secret": "***", "database": "postgres", "port": 80, "socket.io": { "origins": "https://foorumi.vankilapalvelin.com:* http://foorumi.vankilapalvelin.com:* https://www.foorumi.vankilapalvelin.com:* http://www.foorumi.vankilapalvelin.com:*" }, "postgres": { "host": "127.0.0.1", "port": "5432", "username": "***", "password": "***", "database": "***", "ssl": "false" } }
If one of you Gurus could help me with this because I am starting to lose hope with it. I think the biggest problem is with the socket.io but not sure what is wrong with it.
-
Could you please tell us which guide (documentation) you've followed during NodeBB install process?
Your server reposponds Error 503 (Service Unavailable) from time to time.
-
Have you seen this?
[FAQ] Websockets not working due to misconfigured origins
This FAQ is applicable for the following situations: You're receiving the following error in the Javascript console: WebSocket connection to 'wss:///socket...
NodeBB Community (community.nodebb.org)
Are you using a reverse proxy? As this error says, you should be:
Using ports 80 and 443 is not recommend; use a proxy instead.
As for this:
"origins": "https://foorumi.vankilapalvelin.com:* http://foorumi.vankilapalvelin.com:* https://www.foorumi.vankilapalvelin.com:* http://www.foorumi.vankilapalvelin.com:*"
It's strongly recommended to only have a single URL for NodeBB. Also, having a
www.
when your forum is already on a subdomain is not recommended. Also, you shouldn't run your site on bothhttp
andhttps
as it can put your users at risk. -
I can get same result when changing default theme on the cloud hosting. Due to upload handling and dropping them after some time. Nothing wrong with NodeBB here.
Please try Redis or MongoDB instead of PostgreSQL. A better choice for most users.
-
Tested it again on a freshly installed server. Please wait while we try to reconnect shows when NodeBB is installed by a root user and not a normal user.
Solution: add new non-privileged system user and do not use root to install NodeBB. Such note should be included on every install guide.