Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember Troubleshooting › User getting a 502 bad gateway error when trying to logout
Tagged: 502 bad gateway
- This topic has 5 replies, 3 voices, and was last updated 7 years, 3 months ago by admin.
-
AuthorPosts
-
August 4, 2017 at 3:07 pm #14143epimazzoMember
Hi there,
We’re facing a 502 bad gateway error right after an user has logout from our internal Intranet. The provider can’t figure out what’s causing such thing and I suspect being an environment issue as it’s related to nginx with Apache enabled. By disabling it, nothing happens. Keeps failing.
I then followed a few suggestions here like using this URL: example.com/some-page/?member_logout=1, but it didn’t work either.
Any idea or suggestions I can care on?
Thanks
August 4, 2017 at 4:00 pm #76154wzpModeratorWhen the error occurs; is the displayed URL valid?
And since you are dealing with an Intranet; can we assume that it’s not possible to observe the error from the outside? Is the server on the Intranet, or is it on the Internet, and the error only occurs from within the Intranet?
Google is your friend; 502 errors are known to occur when using Apache with Nginx:
- [https://askubuntu.com/questions/694669/nginx-over-apache-gives-502-bad-gateway]
- [https://stackoverflow.com/questions/41998693/nginx-giving-502-bad-gateway-error-on-port-80]
- [https://serverfault.com/questions/828218/502-bad-getaway-nginx-and-apache-servers]
You get the idea… It’s some kind of Apache/Nginx configuration issue, that has nothing to do with the plugins.
August 5, 2017 at 12:03 am #76155adminKeymasterYour hosting provider should be able to read the server’s error log and give you more info on what exactly is failing. That would be a good starting point to troubleshoot this.
August 7, 2017 at 1:32 pm #76156epimazzoMemberHey there guys,
Thaks for the valuable tips. The 2nd trick did the work. The hosting provider has made a few adjusts and we back on but unfortunately, we discovered another major issue: All internal URL links start getting 404 error nginx. This is quite weird. I then disabled APC but it didn’t work either.
So, we’re investigating the server error’s log. If you have any other possible idea or tip, I thank you.
Thanks.
August 7, 2017 at 1:47 pm #76157epimazzoMemberWZP,
I know is probably a non-plugin’s issue related.
Thanks
August 8, 2017 at 12:13 am #76158adminKeymasterI am not sure what you mean by “internal URL links”. Our plugin doesn’t use anything like that. You take the URL of a page and plug it in the plugin’s settings. If you enter the URL in the browser’s address bar and it is not rendering the page then your hosting provider will have to sort it out for you.
- [https://askubuntu.com/questions/694669/nginx-over-apache-gives-502-bad-gateway]
-
AuthorPosts
- You must be logged in to reply to this topic.