Issue with Admin Panel since upgrade to 1.4.2

PitaJ

@teh_g yes it appears that Nginx does the same thing. I could fix this by double encoding on both ends of NodeBB or something.

priapo

@teh_g I think if you google something like nginx proxy escaping you can find solutions on stackexchange/stackoverflow so you can update your nginx config..

teh_g

@PitaJ said in Issue with Admin Panel since upgrade to 1.4.2:

@teh_g yes it appears that Nginx does the same thing. I could fix this by double encoding on both ends of NodeBB or something.

I found the fix, it was shockingly easy!

The user guide suggests using the following config for nginx:

location / {
    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://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";
}

I had to change the "proxy_pass" line to remove the trailing "/":

location / {
    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://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";
}

priapo

@teh_g Very good, that's why I always say, post your config files removing sensitive data. We would have helped you resolving this simple issue of removing the slash better.

teh_g

@priapo said in Issue with Admin Panel since upgrade to 1.4.2:

@teh_g Very good, that's why I always say, post your config files removing sensitive data. We would have helped you resolving this simple issue of removing the slash better.

I just grabbed that right from the documentation. It might be worth fixing the documentation.

Mikael Jenkler

I checked my config, no trailing slash on proxy_pass in my case. Thanks for the heads up! Its nice to learn something every day

Michael Pfaff

@teh_g I'm having the same admin dashboard issue. Would you mind walking me through what you did to check and fix this? Sorry, kind of a noob here.

PitaJ

@Michael-Pfaff remove the trailing slash from the URL in your nginx config.

Michael Pfaff

@PitaJ said in Issue with Admin Panel since upgrade to 1.4.2:

@Michael-Pfaff remove the trailing slash from the URL in your nginx config.

Can I do this just by downloading the file, editing and reuploading? Or do I need to take other steps?

PitaJ

@Michael-Pfaff yes you could do it that way, or you could use nano to edit it from your terminal on the server itself.

Michael Pfaff

@PitaJ said in Issue with Admin Panel since upgrade to 1.4.2:

@Michael-Pfaff yes you could do it that way, or you could use nano to edit it from your terminal on the server itself.

Hmmm. I removed the trailing slash and it doesn't seem to have fixed anything. Any other step I need to take?

PitaJ

@Michael-Pfaff well you need to reload nginx

Michael Pfaff

@PitaJ said in Issue with Admin Panel since upgrade to 1.4.2:

@Michael-Pfaff well you need to reload nginx

That worked! Sorry I'm such a noob, @PitaJ. Very much appreciate your assistance.