Shawn, I been seeing this error for the last 3 days. It only happens once a day, the first time I open the site that day. Just thought I would let ya know in case nobody else has yet. (If it's my browser or PC let me know. I didnt do a search for that error.) The following error occurred: 502 Bad Gateway nginx Code (markup):
Hmmm... I haven't seen that myself... 100% of the time, but only when you initially come to the site?
If you flip to a different browser are you able to recreate the initial issue? Maybe like a session creation thing?
I wasn't able to with IE. Do you think maybe it's because I used http in the url not https? The bookmark on my browsers toolbar was pointed to http from the old site. (i just changed it)
it just did it to me again after a restart, cached cleared and logged in again. Using https this time -- FF 19.0 and Windows 7
What if you use the normal log out button and restart browser? Just wondering if it's something weird with the initial session creation...
Well, just for good measure, I patched the web server with a new version of the SPDY protocol (which is what is used if you are on Opera, Firefox or Chrome)... It didn't say *what* fixes there are... just says "some fixes". So I guess let me know if you run into it again... http://nginx.org/patches/spdy/CHANGES.txt
Was just thinking about this again... It could actually be the SPDY thing since IE doesn't support it, and SPDY *does* do some special things when you first connect (it creates a permanent connection it reuses for you). So with it not happening with IE, but happening with Firefox... Maybe "some fixes" means, "make it work right on first connect with Firefox" lol
I've had this a few times as well, although I can't recall it happening today. I use Chrome version 25.0.1364.152 m, WinXP and I access the site through https://forums.digitalpoint.com/watched/threads I thought it may have had something to do with my adblocker playing up, but because it didn't keep occurring once I started browsing the site, I didn't pursue it. For an unrelated reason I was in the adblocker settings today and noticed I had the DP sub domains "blogs" and "advertising" in the exclude list which triggered my memory about the 502. I removed the excluded domains, restated chrome, then added "advertising" again. Not sure if that was causing the bad gateway, but thought I'd mention it. Cheers James
Nah... Ad blocker could do some weird things, but not that. After thinking about how SPDY holds connections, I had another thought... The front-end load balancer were set to drop connections after 15 seconds of being idle... made some adjustments there too. But I don't think that could cause a 502 on the web server either.
Actually, When it first happened I was going to take a screenshot but got distracted when my phone rung, when I turned back to the computer less than a minute later, the bad gateway sign was gone. I don't think I touched anything. Would SPDY dropping the connection have caused the message to disappear, or does it just time out after a while?
As far as I know, you have to click somewhere in the browser window to make it go away... Connection dropping definitely couldn't close it. Maybe the normal errors in XenForo has some really long timeout though and I just never waited long enough to see them go away on their own.