Error 502 Bad Gateway for Logout

Hi @cuongpham259 and thanks for your feedback.

We noticed this behavior on some Nginx servers when there are specific configurations to work with wp-admin.

Please contact your host to see if they can help you avoid this error when you change the admin path.

John

Hi @johndarrel . Thanks for your feedback

I’m a personal server admin with Fastpanel, sorry I don’t have experience with this fix.

Can you share keywords or blog post to find out this problem. I will study to fix it.

Thanks you!

Sure,

First, make sure the config was made correctly based on your server type:
https://hidemywpghost.com/theme-not-loading-correctly-website-loads-slower/

Other sources:
https://www.itpro.com/web-hosting/30258/what-is-a-502-bad-gateway-and-how-do-you-fix-it
https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-502-bad-gateway-error-in-wordpress/

An one more,

See if you get the error when you set a redirect destination on logout:
https://hidemywpghost.com/kb/activate-security-tweaks/#redirect_on_logout

Hi @johndarrel

Thanks for sharing the document.
I will try a few more times.

Hope you can find the cause and share it here.

Hi @johndarrel

After checking the server logs I get the message ” upstream sent too big header while reading response header from upstream,” after every attempt to log out.

After a few hours digging through a discussion I found it here: https://stackoverflow.com/questions/23844761/upstream-sent-too-big-header-while-reading-response-header-from-upstream

fastcgi_buffers 16 16k; 
fastcgi_buffer_size 32k;

Adding this code to nginx config file everything works again, hope this is a good guide for later people.

Thank you for creating a great Plugin !!!

Wow, thank you for sharing this solution and I’m glad you found it.

It will definitely help us and others who get the same error message on logout.

Cheers, John