Jump to content

B1 Girls on Vacation - General Topic June #3


Recommended Posts

5 minutes ago, meran said:

this is coming straight from nginx proxy server so I believe this is a web server hosting issue . 

so you think it's just a hosting issue?  personally, i think RLC has known about this possibly happening and has been tip toeing around it.  it will be interesting to read what they say to you all when and if they do come back online.  that is, if they give any kind or explanation at all!

Link to comment
Share on other sites

Domain Name wixdns.net
Domain Extension net
Top-Level Domain (TLD) .net
TLD Type Generic Top-Level Domain (gTLD)
Registrar GoDaddy.com, LLC
Registrar WHOIS Server whois.godaddy.com
Registrar URL http://www.godaddy.com
Domain Updated Date 2018-08-31T01:03:50+02:00
Domain Creation Date 2013-09-29T11:03:09+02:00
Domain Expiry Date 2023-09-29T11:03:09+02:00
Domain Status clientdeleteprohibited
clientrenewprohibited
clienttransferprohibited
clientupdateprohibited
Nameservers ns1.p14.dynect.net
ns2.p14.dynect.net
ns3.p14.dynect.net
ns4.p14.dynect.net
DNSSEC unsigned
.net Sponsoring Organisation VeriSign Global Registry Services
.net WHOIS Server whois.verisign-grs.com
.net Registry URL http://www.verisigninc.com
Link to comment
Share on other sites

6 minutes ago, HarleyFatboy said:

so you think it's just a hosting issue?  personally, i think RLC has known about this possibly happening and has been tip toeing around it.  it will be interesting to read what they say to you all when and if they do come back online.  that is, if they give any kind or explanation at all!

yes I think because otherwise it will not be coming from reverse proxy. 
This 502 bad gateway happens when nginx reverse proxy or load balancer cant connect to the web server at the back end.

its either shut down or network issue or no service running on the server.

Link to comment
Share on other sites

2 minutes ago, meran said:

yes I think because otherwise it will not be coming from reverse proxy. 
This 502 bad gateway happens when nginx reverse proxy or load balancer cant connect to the web server at the back end.

its either shut down or network issue or no service running on the server.

i'm going to have to go with this and the reason I say that is because this has happened before and it didn't take them long at all to get it resolved and back up and running again.  this seems like more of a forced shutdown by somebody with much bigger balls!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...