Looks like your connection to NodeBB was lost, please wait while we try to reconnect.

[Todd]

Hello,

So I'm on a fresh NodeBB install. DigitalOcean Droplet and I have configured Nginx as proxy server. Like several others, I'm receiving the above stated error as soon as I visit the board. I am no longer able to write anything to the boards basically but they do sorta half-work in that I can navigate and read stuff. I cannot save any settings or create new threads.

This is what I got:
Nginx Config:

# Default server configuration
#
server {
        listen 80;
        #listen 443;
        #listen [::]:80;
        server_name myforums.com www.myforums.com;
        return 301 https://myforums.com$request_uri; #NOTE: Also tried #scheme and other variants
}
server {
        # SSL configuration
        #
         listen 443 ssl;
         server_name myforums.com www.myforums.com;
        # listen [::]:443 ssl default_server;
        include snippets/letsencrypt.conf;
        include snippets/ssl.conf;
        root /var/www/nodebb/myforums;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;




        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                # try_files $uri $uri/ =404;
                # Uncomment to enable naxsi on this location
                # include /etc/nginx/naxsi.rules
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Host $http_host;
                proxy_set_header X-NginX-Proxy true;

                proxy_pass http://127.0.0.1:4567/;
                proxy_redirect http://127.0.0.1:4567 https://myforums.com;

                # Socket.IO Support
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
        }

My config.json:

{
    "url": "https://myforums.com",
    "secret": "somesecret",
"bindaddress": "localhost",
    "database": "mongo",
    "port": 4567,
    "use_port":false,
    "mongo": {
        "host": "127.0.0.1",
        "port": "27017",
        "username": "myforums",
        "password": "somepass123",
        "database": "forumsdb"
    }
}

I have 2 problems:

1. No matter if I type in https://myforums.com or http://myforums.com , it redirects the user to https://www.myforums.com . I do not want the www.

2. The error message in the subject is happening when I go to my boards. I saw a StackOverflow response where the guy said to add listen port 443 to the first server block but for me, that makes the entire site go down completely.

I'm not sure what needs to be fixed here but something screwy is going on between my SSL, Nginx config, and NodeBB config. Thanks for any assistance. What I'm trying to accomplish here is have a HTTPS-ALWAYS NodeBB. Everything should be https. I dont care about www.

[PitaJ]

https://docs.nodebb.org/configuring/proxies/nginx/ could help you some.

For a start, try removing all of the www.myforums.com stuff. proxy_redirect needs to be set to off

[Todd]

@pitaj

Got it figured out. Basically, you have to form a "redirect chain" kinda. I think I was creating an infinite loop of redirection or excluding a specific case (www. for 443 and for 80 separately) in my above nginx config. I ended up having to redirect 80 http://www.domain.com, 80 http://domain.com AND 443 https://www.domain.com all to 443 https://domain.com and then that third block is where all the master logic for the activity goes, if that makes sense.

In my original post, I was combining too many of these cases into just 2 blocks. In addition, I also added location / {} and wrapped that around my return 301 statements.

This fixed the problem entirely with both the domain and the forum malfunctioning. Last but not least, I wanted to mention that I also added proxy_set_header X-Forwarded-Proto $scheme; to the main logic block near the other proxy_set settings, which fixed a csrf error as well. So we're all good now!

Very exciting stuff. I appreciate the quick replies and help. Happy to use NodeBB for my new site!