Is anyone else getting Bad Gateway errors while using Firefox to view the EN website?
I seem to see them with the new posts and even when I archive an idea…
502 Bad Gateway
nginx/0.6.32
Plus double posts ;)
| Bad Gateway errors on the EN website | |
|---|---|
|
Mr. Ed
mredsasyshi1
71,250
Insider Points
|
Is anyone else getting Bad Gateway errors while using Firefox to view the EN website? I seem to see them with the new posts and even when I archive an idea… 502 Bad Gateway Plus double posts ;) |
|
|
|
|
Ken Somerby
reddawg |
I use Fire Fox and never had a problem |
|
Mr. Ed
mredsasyshi1
71,250
Insider Points
|
I use the most recent version of Firefox and have never had this problem before. It seem odd that I am having it now after months of smooth sailing. I have to use the EN website in Opera to use the forums and or my dashboard now. Here is what I see with Firefox |
|
dond invents
dond
287,750
Insider Points
|
I get the problem now and then. Try deleting your edisonnation.com cookie. You will need to re-login if successful. |
|
Mr. Ed
mredsasyshi1
71,250
Insider Points
|
LOL wish it was that simple but I delete my cookies every day… ;) This problem has been on and off now for the last week. Just today it has been the entire EN website but before it was once in a while and only on the new posts. It never lasts long so I will see if it changes tomorrow… Odd that it was on this website though and no other. |
|
Mr. Ed
mredsasyshi1
71,250
Insider Points
|
I am going to uninstall Firefox and try a fresh install. I was only wondering if anyone else had got the error and as nobody said they have it has to be my end… Needed the info before I wipe the system… Thanks Dond |
|
Colonel Steve "Chris" Austin
cander09
256,250
Insider Points
|
I have seen the error, but it has been a very long time. Currently I am using: Firefox/3.5.7 I did see some comments on other forums about nginx sending too large of a cookie to FF and this will cause issues. Which could make sense, even if you clear your cookies everyday. This is one fix/hack that I found out there, unfortunately it isn’t anything you can do. EN has to make an adjustment to the nginx web server. This may not be the best solution, but they reported no further errors after doing this: http keepalive_timeout 600; upstream zimbra In nginx.conf.web.http and https add timeout values:
proxy_read_timeout 600; The nginx defaults are 60 seconds. |
|
Matt Spangard
matt
∞
Insider Points
|
Just caught this post… our tech team will look into it. If you didn’t post a ticket in the support section, please make sure you do in the future so our tech team sees it right away and can investigate/fix the issue. Thanks! |
|
Jared Pace
jdpace |
Mr. Ed, I’ve just change some settings on our load balancer that will hopefully fix this issue. Please let me know if you keep getting those error messages. Thanks Cander for pointing me in the right direction. According to our error logs some request headers being sent back were too large. Those lead to several posts suggesting to up our buffers using the following config: proxy_connect_timeout 90; proxy_send_timeout 180; proxy_read_timeout 180; proxy_buffer_size 16k; proxy_buffers 8 16k; proxy_busy_buffers_size 32k; proxy_intercept_errors on;Thanks again, |
|
Mr. Ed
mredsasyshi1
71,250
Insider Points
|
Great advice Chris… Thanks… Thanks Matt for reporting it… I didn’t even think to submit a support ticket as it was not a submission problem. Jared… Thanks for working on this. LOL I reinstalled Firefox earlier and have not seen the error but now that you made the changes I hope not to anymore. Thanks to all ;) |