Profile images not showing - nodebb behind nginx

smendez-hi

@pitaj I'm already in production so I will update it only if the error is solved. Otherwise i don't want to take risks because this is the only issue i have. I will try this week with my local environment and see what happens. Any issue i'll update this thread. Thanks for your help

julian

Did you also set the subfolder in nginx location block?

Please paste it here. It should have the subfolder in the location like but not in the proxy_pass line

smendez-hi

@julian The location configuration:

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;

                #rewrite ^/forum(.*) /$1 break;
                proxy_pass http://127.0.0.1:4567;
                proxy_redirect off;

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

        }

julian

@smendez-hi Personally, I used location /forum/ { in my nginx block, not sure if that makes a difference.

smendez-hi

@julian Adding the trailing / messes up the redirections to /forum. But manually changing the url to access and changing the profile image still works as before

PitaJ

I just want to confirm: are you talking about the user avatar, or the cover image on the profile page?

smendez-hi

@pitaj The user avatar. I didn't try to change the cover image.

smendez-hi

@julian Do you have the trailing slash inside the location block as well? In the proxy_pass line? http://127.0.0.1:4567/?

PitaJ

@smendez-hi I just checked, and this is fixed in at least the latest version of NodeBB. It was probably fixed long ago, though.

julian

@smendez-hi my location block:

    location /forum/ {
        client_max_body_size 200m;

        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_set_header Access-Control-Allow-Origin 'http://localhost/forum';

        proxy_pass http://127.0.0.1:4567;
        proxy_redirect off;

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

smendez-hi

Ok, thanks to both of you. In case of any news i will update this thread. But for now i will continue with this bug. We can live with this.