Remtoe server returned an error (502) Bad Gateway

[elsteve 0]

Just noticed this happening this morning around 10am EST....

any thoughts?

[Staff 9973]

Just noticed this happening this morning around 10am EST....

any thoughts?

Hello!

We had a minor problem in one of our frontends which caused an approx. 2 minutes inaccessibility to the web site (only from that frontend).

Kind regards

[mattisamac 0]

Im still getting this error trying to connect to Octantis?

[mattisamac 0]

I am getting the same issue trying to connect to any US server - is the problem still present?

[elsteve 0]

As of 12:20pm EST I am still having this issue...

[elsteve 0]

Resolved. thank you

[Staff 9973]

Hello!

The problem was caused by momentary failure of our secondary frontend caused by the datacenter provider.

Now, if you have in your hosts file the line:

85.17.207.151 airvpn.org

you force resolution of airvpn.org to the secondary frontend.

In order to allow your system to access the primary frontend in case of failure of the secondary (and viceversa), keep in your hosts file the lines:

85.17.207.151 airvpn.org

212.117.180.25 airvpn.org

so that your system will first resolve airvpn.org to 85.17.207.151 (secondary frontend). In case of failure your system will resolve airvpn.org to 212.117.180.25 (primary frontend) transparently in a matter of a few seconds.

Both frontends are absolutely identical, since they get data from a clustered database which resides in our backend servers.

If you don't keep any line in your hosts file, airvpn.org will be resolved according to DNS (currently 212.117.180.25).

Kind regards