Error 502 – Bad Gateway

Hi @kickthefog,
“Error 502 – Bad Gateway” typically comes either from your server itself or a proxy that might be sitting in front of the server.

If you had blocked an IP incorrectly, that would likely have affected all your pages and not just the Firewall page in Wordfence.

What does the “Error 502 – Bad Gateway” page look like? Is there any indication on it where it was served from?

Hi, Thank you for the reply.

The error only occurs when I click “Firewall”. All other parts of wordfence work fine for me so i don’t believe I did anything “too” stupid when blocking the IP. I’ve blocked lots of them in the past with success.

Below is the exact page that appears when I click on “firewall” if that helps.

THANK YOU for your assistance. ??

Error Page displayed:

”
ERROR 502 – BAD GATEWAY
Why am I seeing this page?
The server that your request has reached is acting as a gateway or proxy to fulfil the request made by your client.

Web Browser => Web Front-End => Web Back-End

This server (Web Front-End) received an invalid response from an upstream (Web Back-End) server it accessed to fulfil the request.

In most cases this will not mean that the upstream server is down, but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.

This problem is most commonly caused when there is a problem with IP communications between the Web Front and Back-Ends. Before you attempt to resolve this problem you should clear your browser cache completely.

Our support staff will be happy to assist you in resolving this issue. Please contact our Live Support or reply to any Tickets you may have received from our technicians for further assistance.
“

Hi again @kickthefog,
Sorry for the late reply. I think this page is being served by your web host and I’m wondering if you’ve tried reaching out to them to see why it might be happening?

Thank you for the reply.

No I have not yet reached out to them… however… Just for fun I tried it again today and it is working. So I think you were right that it was something on the host side. Either it self corrected or they did something. Either way, I’m happy it works now.

Thanks for your help.
??

Hi @kickthefog!

Okay, thanks for the update! I did not expect that to fix itself but that’s great news. Best of luck for now!