Upstream Sent Too Big Header While Reading Response Header From Upstream

Hi, try the following.

Add together your homepage URL to the following characteristic Re-direct URL: located in WP Security -> Creature Force -> Cookie Based Brute Force Login Prevention.

Allow me know if the in a higher place works.

Cheers

Thread Starter mkaand

(@mkaand)

Hi,

I tried what you lot said only information technology doesn't piece of work. It redirects to my home page at present but user yet logged in. Only way to logout clear cookies.

I use Secret Word as well in same folio. What I should exercise more? I can open you lot an account for testing if you lot wish.

Edit: Thanks very much for fast answer.

• This reply was modified i year, 10 months ago past mkaand.

Hullo, lets try something different.

Can y'all enable the other Brute Strength feature Rename Login Page. Let me know if this 1 works better than the other?

Thank yous

Thread Starter mkaand

(@mkaand)

Hi,

Now its better, user can logout but I see Cloudflare Bad Gateway error after logıut. And user should go back to site manually. Hither is the log:

2020/04/21 11:37:29 [error] 32545#32545: *162588 upstream sent too big header while reading response header from upstream, customer: xx.xx.20.xx, server: mega-mount.com, request: "GET /xxxxxxx/?action=logout&redirect_to=https%3A%2F%2Fmega-mount.com%2Fen%2Fmy-account%2F&_wpnonce=xxxxxxxxxx HTTP/1.1", upstream: "http://twenty.xx.20.xx:8080/garip/?action=logout&redirect_to=https%3A%2F%2Fmega-mount.com%2Fen%2Fmy-account%2F&_wpnonce=xxxxxxx”, host: "mega-mount.com", referrer: "https://mega-mount.com/xxxxxx/?activeness=logout&redirect_to=https%3A%2F%2Fmega-mount.com%2Fen%2Fmy-account%2F&_wpnonce=yyyyyyyyyy”

wpnonce parameter returns unlike xxxxxxx and yyyyyyy

Thread Starter mkaand

(@mkaand)

Update:

I add post-obit lines to my nginx.conf file proxy section:

proxy_buffer_size 128k;
proxy_buffers four 256k;

Problem solved but another trouble show upwards. Now I do not see bad gateway fault and no more in a higher place log in header. But after logout user redirects to https://mysite.com/wp-admin/alphabetize.php

And page says Non Available.

No new error and no more big header error at logs.

Ah, so your server is an Nginx server. That explains some of the bug you are running into. Is your effect at present resolved?

Regards

Thread Starter mkaand

(@mkaand)

Still working on it. I see this:

https://trickspanda.com/auto-redirect-users-logout-wordpress/

Maybe its related with theme? I only wonder why after logout information technology redirects to https://mysite.com/wp-admin/alphabetize.php

This is likewise related your plugin I approximate. Because if I disable your plugin people can logout easily. Delight help me. Thanks.

P.S. NGINX issue solved simply other issue still continue.

Hullo, I recollect your best option is to practise a plugin/theme conflict test. For example: Disable all other plugins except ours and then carry out a test. Practise the same with your theme. For example: Test one of WordPress default themes similar Twenty 19.

Let me know how y'all go.

Thank you

Thread Starter mkaand

(@mkaand)

Hi Once more,

Later my test I can clearly say this is not related with theme it is related with AIO WP Security plugin. I researched a lot and I read following topics (same effect reported before you)

https://wordpress.org/back up/topic/logout-redirection-to-homepage-for-renamed-login-page/

I added following lawmaking to core functions.php and it works but I don't like this solution. Because I do non want to change core files. I am nonetheless looking for solution.

add_action('wp_logout','auto_redirect_after_logout');
function auto_redirect_after_logout(){
wp_redirect( home_url() );
exit();
}

Thread Starter mkaand

(@mkaand)

Hi Over again,

I stock-still that issue with installing extra plugin called:
Peter's Login Redirect

I added following variable in to settings of Peter's plugin:

All other users section Logout URL:
[variable]http_referer[/variable]

Without any modification at core files, later logout user redirects to http referrer webpage. It works perfectly. I highly recommend Peter'south plugin for AIO WP Security users

I am glad to know you constitute a solution 🙂

Thanks for your suggestion as well. I am sure this volition aid others.

Savor both plugins.

Thread Starter mkaand

(@mkaand)

Thank you for your support. I promise developers can improve cookie based protection setup. Currently my hugger-mugger showing at front-end. I don't like it simply It is OK. Developers as well improves logout office. Without Peter'southward plugin I cannot fix the event. (I don't desire to modify core files)

Hello I have the same problem. My customers cannot logout when using mobile phones due to redirection of 127.0.0.i
If I disable creature forcefulness Cookie based login protection then the problem eliminated

I tried the Peter'southward Login Redirect as mentioned by mkaand and his settings but unfortunate problem nonetheless exists.

Practice you take any other solution on that?

Cheers in advance

Thread Starter mkaand

(@mkaand)

Hi @theokefal

You should disable cookie based login page option and y'all should enabled redirect login option. Then you can use Peter'south plugin. Peter's Plugin settings:

All other users section Logout URL:
[variable]http_referer[/variable]

That's it.

Thank you for your very promt answer, I will endeavor information technology this night and requite yous results

All the best

lardnermargance.blogspot.com

Source: https://wordpress.org/support/topic/logout-issue-redirect-to-127-0-0-1/

Share :