Verification of any social account fails. Browser error says 502 BAD GateWay

I have tried to verify my social accounts, and attempted the hard refresh suggestions found on the forum, but nothing helps.

I checked the console log of my browser (Chrome and Edge) and they both give me similar errors:

Proof url returned unexpected http status 502.
              Unable to validate proof.

Is this a problem with my Blockstack browser? My OS is Windows 10.

Any help will be greatly appreciated.

Hi @janmande, this should have been resolved in the latest browser version. I recommend updating and trying to verify again as described in our FAQ. If you continue to have trouble, feel free to reach out to [email protected].

Thanks. Upgrading to latest version (v0.26.2) fixed the issue :grin:

Sounds good @janmande. Glad that fixed the issue!

Bad gateway refers to http error 502 which is mean that a server which is try to fulfill the client request received an invalid response from upstream server. It is often a network error between servers on the internet, meaning the problem wouldn’t be with your computer or internet connection. Empty or incomplete headers or response body typically caused by broken connections or server side crash can cause 502 errors if accessed via a gateway or proxy. Since it’s just a generic error, it doesn’t actually tell you the website’s exact issue.

How to Solve 502 Errors

Perform a hard-refresh in your browser. On Macs, this is done by pressing Cmd + Shift + R.

Clear your browser cache and delete cookies. Your browser may be holding on to certain files that were saved once you visited the website with a 502 error.

Change your DNS servers. If you’ve never changed them in the past you likely still have the default servers assigned to you by your ISP, try using open DNS servers such as Google’s Public DNS.

Finally, restart your computer/networking equipment. Some temporary issues with your computer and how it’s connecting to your network could be causing 502 errors, especially if you’re seeing the error on more than one website. In these cases, a restart would help.