NGINX Reverse proxy

Simos

@Brophy i've try to set it on 127.0.0.1 but nothing change, nodebb look for all assets in main site path / and not in /forum/ . Doing the vhost on http://forum.mysite.tld work fine , but if i set nodebb on 127.0.0.1 and not on forum.mysite.tld i get a permission denied on websocket.

Dravere

The url configured in your config.json needs to match the URL by which you want to access the site. So if you want to access the site via https://www.mymainsite.tld/forum you have to set the url in config.json to this value.

Simos

i've modified the url in config json and now work with this config :

location /forum {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $http_host;
    proxy_set_header X-NginX-Proxy true;

    proxy_pass http://www.mysite.org:4567/forum;  # no trailing slash
    proxy_redirect off;

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

The problem is if i open https://www.mysite.org/forum it don't add the trailing slash and i try to open /forumcategories instead of /forum/categories , i've try to modify location to /forum/ but it give error if i try to open https://www.mysite.org/forum/ , any hint ?

<baris>

@Simos This is fixed on latest master, see https://github.com/NodeBB/NodeBB/issues/6949

Simos

@baris said in NGINX Reverse proxy:

sub folder install homepage gives 404 · Issue #6949 · NodeBB/NodeBB

https://community.nodebb.org/topic/13309/missing-a-trailing-slash-causes-404-on-forum-in-subfolder

GitHub (github.com)

I'm new to nodebb i'm running 1.10.2 i'll have issue with my persona child theme and my external auth plugin ?

Simos

Just upgraded to git master and solved

Simos

@baris it look nodebb look also for /assets/images in root path and not in /forum/assets/images

PitaJ

@Simos for which images?

Simos

@PitaJ for example the default user' cover background, should be because it was user already in the database with the path for my old configuration (http://forum.mysite.org) ?

Simos

I've just checked, also for new users cover it look for /assets/images and not for /forum/assets/images