Author Topic: Bad gateway clicking show new replies (Read 5759 times)

PA0PBZ · « **on:** June 30, 2014, 03:00:17 pm »

When clicking "Show new replies to your posts" (https://www.eevblog.com/forum/unreadreplies/) in IE11 I get the "502 - Bad Gateway" reply with the greetings from Dave & gnif. This is the third time it happened in about a week, on different pc's.
I can solve it by doing a Ctrl-F5 on the page but it will come back. Chrome is not affected afaik, neither anything else on the site.
Although the 502 - Bad Gateway states that there is no need to report it, I think it was created for something else.

Any ideas out there?

nctnico · « **Reply #1 on:** June 30, 2014, 04:53:51 pm »

I have the same. I don't know the exact details but it seems the hoster has some proxy between de webserver and the internet which sometimes acts up.

PA0PBZ · « **Reply #2 on:** June 30, 2014, 05:58:48 pm »

Quote from: nctnico on June 30, 2014, 04:53:51 pm

I have the same. I don't know the exact details but it seems the hoster has some proxy between de webserver and the internet which sometimes acts up.

Yes, I am thinking the same, but why it only does this with the unread replies link I don't know. Next time I will run a wireshark trace, maybe that points to something.

rob77 · « **Reply #3 on:** June 30, 2014, 06:53:35 pm »

Quote from: PA0PBZ on June 30, 2014, 05:58:48 pm

Quote from: nctnico on June 30, 2014, 04:53:51 pm
I have the same. I don't know the exact details but it seems the hoster has some proxy between de webserver and the internet which sometimes acts up.

Yes, I am thinking the same, but why it only does this with the unread replies link I don't know. Next time I will run a wireshark trace, maybe that points to something.

wireshark... common....

if you get an application error rendered by the webserver/application, then wireshark won't help you... wireshark captures packets on your side.. you would see a normal tcp session opened , data transferred and session closed.... like any other tcp session regardless of the content transferred.

only the application or webserver logs might give you some clues, not packet capturing on the client side.

PA0PBZ · « **Reply #4 on:** June 30, 2014, 08:18:55 pm »

Sure, but it can give me a clue what triggers the 'bad gateway' response. After all, it can be solved locally by refreshing with <Ctrl><F5>.

retrolefty · « **Reply #5 on:** June 30, 2014, 08:55:39 pm »

Quote from: PA0PBZ on June 30, 2014, 03:00:17 pm

When clicking "Show new replies to your posts" (https://www.eevblog.com/forum/unreadreplies/) in IE11 I get the "502 - Bad Gateway" reply with the greetings from Dave & gnif. This is the third time it happened in about a week, on different pc's.
I can solve it by doing a Ctrl-F5 on the page but it will come back. Chrome is not affected afaik, neither anything else on the site.
Although the 502 - Bad Gateway states that there is no need to report it, I think it was created for something else.

Any ideas out there?

I had the same behavior using Chrome yesterday. Only after I hit the X showing on the top left (same button that is normally 'reload page') and then reloading the page did I get back 'unread posts'. Only happen once so not sure it will or can return.

rob77 · « **Reply #6 on:** July 01, 2014, 06:50:56 am »

Quote from: PA0PBZ on June 30, 2014, 08:18:55 pm

Sure, but it can give me a clue what triggers the 'bad gateway' response. After all, it can be solved locally by refreshing with <Ctrl><F5>.

sorry it can't... such a bad gateway error usually comes from the application's internal routing - nothing to do with the network. it's more about "to which application controller to route this URL?"

nctnico · « **Reply #7 on:** July 01, 2014, 04:04:25 pm »

Nonsense. A 502 error is a reply from a proxy server.

rob77 · « **Reply #8 on:** July 01, 2014, 04:34:54 pm »

Quote from: nctnico on July 01, 2014, 04:04:25 pm

Nonsense. A 502 error is a reply from a proxy server.

if it's throwing a 502 for a particular URL only , then obviously the proxy is part of the application because it makes application specific decisions about routing of requests based on URL.

so a real nonsense is to further discuss anything here with you guys

nctnico · « **Reply #9 on:** July 01, 2014, 10:37:49 pm »

If a browser can't find a page it will give a time-out error or host not found. If you get a 500 series error your browser has been talking through the http protocol to another server on the network but that server decided it could not fulfill the request. But don't take my word for it:
http://www.checkupdown.com/status/E502.html

macboy · « **Reply #10 on:** July 02, 2014, 12:12:43 pm »

For a while, I got the bad gateway message trying to load any page on the site. I thought that maybe my employer had blocked it or something. It turned out to be cookies. Gentlemen, clear your cookies for eevblog.com.

fillermark · « **Reply #11 on:** December 10, 2019, 06:13:24 am »

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.

mark03 · « **Reply #12 on:** December 10, 2019, 05:11:37 pm »

Funny thing is, I get these "502 bad gateway" errors *all the time* with this site (not on specific URLs like the OP, just generally). By that I mean that I run into them at least 3-4 times/year, and usually when I do, the forums are unusable and I just have to come back in several hours or a day. I don't think I have ever encountered a similar error on any other web site. So all this stuff about cookies, caches, proxies, etc. is interesting, but clearly there is something weird about eevblog.

Maybe it's Oz... left-handed vs right-handed electrons in the southern hemisphere?

tebbybabes · « **Reply #13 on:** December 25, 2019, 12:01:07 pm »

Hello. I just wanted to report that I was experiencing this error for most of yesterday on multiple devices.

I haven't changed anything and it's back to working now. Judging by the timestamps of replies on the posts that I've been reading, obviously those posters had no problem accessing the site.

Just thought I should add more anecdotal experience, in case anyone can make heads or tails of it.

Addendum - Just read a thread on bug reports. Apparently the forum experienced a DDOS attack. I guess that explains my experience yesterday.

Ranayna · « **Reply #14 on:** December 25, 2019, 12:02:53 pm »

See here: https://www.eevblog.com/forum/chat/website-error-reports/msg2843206/#msg2843206 (the topmost stickied post)

Interesting for me was that the page seemed to work on mobile, using the mobile view.

tebbybabes · « **Reply #15 on:** December 25, 2019, 12:05:34 pm »

Quote from: Ranayna on December 25, 2019, 12:02:53 pm

See here: https://www.eevblog.com/forum/chat/website-error-reports/msg2843206/#msg2843206 (the topmost stickied post)

Interesting for me was that the page seemed to work on mobile, using the mobile view.

Yep, that's the thread I saw it on. Anyway, in my case, mobile was another device I tried and it didn't like it either. At least it's back now.

ebclr · « **Reply #16 on:** December 25, 2019, 04:16:36 pm »

I got the same here, this is due to some problems on David Web provider, who uses Nginx as a cache and probably apache as the main server, When Apaches crash for any reason this bad gateway appears, David may have noted this os apache logs, If he stops Christmas to check what is going on

Koen · « **Reply #17 on:** December 25, 2019, 06:06:56 pm »

I now receive this popup from Chrome when I login :

"Change your password."
"A data breach on a site or app exposed your password. Chrome recommends changing your password on www.eevblog.com now."

shved · « **Reply #18 on:** December 25, 2019, 08:01:16 pm »

Had 502 - Bad Gateway yesterday, now all seems fine.

shved · « **Reply #19 on:** June 24, 2020, 06:46:54 pm »

Had some more bad gateway errors today.

DrG · « **Reply #20 on:** June 24, 2020, 06:54:14 pm »

Yeah, I was getting that for a couple of hours today. I was deeply offended because the returned message was cussing at me...

Code: [Select]

Connection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.

Hey, I was the SMF, Some Mother F_____!


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Bad gateway clicking show new replies (Read 5759 times)

Share me