thanks for reponse 🙂
I identify the ns-embed plugins
@nicolas ??
@priapo so it must be something related to the reverse proxy. Maybe it's an issue caused by some weird issue between the reverse proxy and NodeBB
It was solved; here is my working Apache's nodebb.conf
:
<VirtualHost *:80>
ServerName thewizards.club
Redirect permanent / https://thewizards.club
</VirtualHost>
<VirtualHost *:443>
ServerName thewizards.club
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM
SSLCertificateFile /etc/apache2/ssl/thewizards-club/2_thewizards.club.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key.insecure
SSLCertificateChainFile /etc/apache2/ssl/thewizards-club/1_root_bundle.crt
# ServerAdmin [email protected]
<Proxy *>
Require all granted
</Proxy>
ProxyRequests off
#ProxyVia on
AllowEncodedSlashes On
#ProxyPreserveHost on
RequestHeader set X-Forwarded-Proto "https"
RewriteEngine On
RewriteCond %{REQUEST_URI} ^/socket.io [NC]
RewriteCond %{QUERY_STRING} transport=websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:4567/$1 [P,NE,L]
# NE flag == noescape
ProxyPass /socket.io http://127.0.0.1:4567/socket.io nocanon retry=0
ProxyPassReverse /socket.io http://127.0.0.1:4567/socket.io
ProxyPass / http://127.0.0.1:4567/ nocanon retry=0
ProxyPassReverse / http://127.0.0.1:4567/
ErrorLog /home/web/logs/apache/forum-error.log
CustomLog /home/web/logs/apache/forum-access.log combined
</VirtualHost>
I fixed it based on these resources:
@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.
@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 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.
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 remove the trailing slash from the URL in your nginx config.
@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?
@Michael-Pfaff yes you could do it that way, or you could use nano
to edit it from your terminal on the server itself.
@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?
@Michael-Pfaff well you need to reload nginx
@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.