After installing today's (actually yesterday's, depending on your time zone) updates

I could not reach LinuxQuestions.org.

All the other sites I tried worked as they should, but not here.......

So, I reverted to the previous version of networks-scripts, but that didn't solve the problem.

Then I reverted to the previous sysvinit-scripts package, and bingo, that solved it.

Just FYI, for FWIW.

Same thing here, but independent of computers. So I assume a network or site problem.

jlinkels

1 members found this post helpful.

cwizardone --

Slackware64 14.2 + MultiLib here ...

I was seeing the same 502 Error before and after I installed today's irssi-1.0.7-x86_64-1_slack14.2.txz

OK now ... based on what I've read about it, 502 bad gateway nginx errors are beyond our control ?

-- kjh

1 members found this post helpful.

Perhaps, by the time I had reverted to the previous sysvinit-scripts package,
the site problem had been resolved?
The terminal is still open so i'll re-install the new packages and try again.

Funny, we are so accustomed to visit linuxquestions without issue that if the site is down we begin to troubleshoot our system!

3 members found this post helpful.

what makes you think that a 502 http error is related to your system setup?

2 members found this post helpful.

You're correct.
I've re-installed the new packages and was able to connect.

Thanks to everyone for taking the time to reply.

I did a search and came across a few pages on how to correct "502 bad gateway nginx" errors. From that I gathered it could be a system problem.

There are online tools to test websites, I used:
http://nibbler.silktide.com/

As soon as it reported same issue (502 http error) I knew that problem was on linuxquestions side

1 members found this post helpful.

I went to http://www.isitdownrightnow.com/ and they said that they couldn't reach LQ from about 1:30 AM until 9:00 AM (local time).

502 Errors are server side errors. Something like one server cannot talk to another.

2 members found this post helpful.

I was checking LQ for problems with the latest updates. I have been out of town for three weeks so I was looking for gotchas. Got the 502 and just went on with the massive update. Done now and here reading this! I just figured it would be back up as quick as possible.

1 members found this post helpful.

It is not that stupid. I have been working for years on high power shortwave transmitters. Those were extremely complicated beasts, with only very complicated hardwired control and safety systems. In the HF part it was impossible to measure anyway, and measurements in the logic were often erroneous because of the high field strength. So often the only way for fault location was observation, deduction and logical thinking. Among the technicians there was one golden rule: "if there is a problem, start looking in the first place where maintenance was done, or something had changed". This proved true in the majority of the problems. So it is a sound rule to start looking where you changed something last.

jlinkels

1 members found this post helpful.

I had the problem when I got into work just a couple of hours ago. I refreshed after about 5 minutes and there were no problems afterwards.

1 members found this post helpful.

https://tools.ietf.org/html/rfc7231#section-6.6.3

6.6.3. 502 Bad Gateway

The 502 (Bad Gateway) status code indicates that the server, while
acting as a gateway or proxy, received an invalid response from an
inbound server it accessed while attempting to fulfill the request.

2 members found this post helpful.

I had it too this morning. I assumed it was a site problem and, sure enough, it had cleared up by this afternoon.

3 members found this post helpful.