The Bad Gateway thing is really annoying
The Bad Gateway thing is really annoying
I'd respond to one of the other threads on "Bad Gateway" but I can't open any of the messages because I get "Bad Gateway".
This is happening more and more regularly and is making the site useless.
I find that clearing my browser cookies will fix it for a while, but then I lose all my cookies!
Can we get this fixed please!
This is happening more and more regularly and is making the site useless.
I find that clearing my browser cookies will fix it for a while, but then I lose all my cookies!
Can we get this fixed please!
Ok, I just went and found how to delete individual site cookies in Chrome.tsmall07 wrote:You can just delete the cookie for this site individually and it will fix it.
http://www.guidingtech.com/6295/delete- ... es-chrome/
However, it's still annoying that this site does this. I'd be happy to help try to fix it. This site is important to me and I'd like to make it better.
Didn't realize anyone was having this problem.
I'll log into the server via ssh and pull up the system logs this weekend (can't do it at work). The Plesk interface is for dummies so I can't review anything.
I probably need to tweak the Apache settings. Rackforce forced us onto a new server earlier this month and just ran a generic migration script. So everything is back to basic Plesk config. Pisses me off, but I usually kept notes of the changes. Would like to dump Plesk since with each update things get broken...
I'll log into the server via ssh and pull up the system logs this weekend (can't do it at work). The Plesk interface is for dummies so I can't review anything.
I probably need to tweak the Apache settings. Rackforce forced us onto a new server earlier this month and just ran a generic migration script. So everything is back to basic Plesk config. Pisses me off, but I usually kept notes of the changes. Would like to dump Plesk since with each update things get broken...
it happens to me at least every few days. It happens on two computers at home and one at work.tsmall07 wrote:It's only happened to me once since the initial problem. I think most everyone has been problem free. I don't think it's a problem with the site at this point. For some reason, your computer is trying to access the old server.
I appreciate the work it takes to keep something like this running smoothly. Thanks for doing it!Justin_FL wrote:Didn't realize anyone was having this problem.
I'll log into the server via ssh and pull up the system logs this weekend (can't do it at work). The Plesk interface is for dummies so I can't review anything.
I probably need to tweak the Apache settings. Rackforce forced us onto a new server earlier this month and just ran a generic migration script. So everything is back to basic Plesk config. Pisses me off, but I usually kept notes of the changes. Would like to dump Plesk since with each update things get broken...
Will need feedback.
Believe I tweaked the settings in the extra special place Plesk needs them to be changed @ 8:40pm EDT. Can't just change the config files in the normal config file locations, because with every update Plesk completely rewrites them. How charming. Nginx was turned back on and lost my increased buffer size tweaks after the update, so once your cookie got too big it gives you the 502s.
Believe I tweaked the settings in the extra special place Plesk needs them to be changed @ 8:40pm EDT. Can't just change the config files in the normal config file locations, because with every update Plesk completely rewrites them. How charming. Nginx was turned back on and lost my increased buffer size tweaks after the update, so once your cookie got too big it gives you the 502s.
-
- Posts: 2265
- Joined: Jul 21, 2011 8:05 PM
- Location: Rochester Hills, Michigan
- Contact:
Got this error today for the first time in a while. The bad gateway also showed this here"nginx" which you mentioned here so I thought I'd let you know. I cleared cookies to see if it would help and it has so far, but still unsure why it cropped up.Justin_FL wrote:I haven't checked the logs but found out nginx could be the problem. I turned it off through the web interface, so let me know if there is any improvement. This was something that was not installed on the old server.
Thanks for keeping this site running nearly flawless!!! You guys rock!
The site was offline on purpose for about 20-30 minutes, causing the 502 gateway error.
A certain thread had triggered a huge amount of search queries that were overwhelming the SQL server and had pegged the CPU utilization. I suspended the site for a bit to let the action settle down with the search crawler bots and such.
So yeah, please don't bother with searches, i.e. "find all posts" on a certain 40K post user since it will timeout before finishing. Get enough of these going concurrently and the website slows to a crawl, which is what was happening this AM.
A certain thread had triggered a huge amount of search queries that were overwhelming the SQL server and had pegged the CPU utilization. I suspended the site for a bit to let the action settle down with the search crawler bots and such.
So yeah, please don't bother with searches, i.e. "find all posts" on a certain 40K post user since it will timeout before finishing. Get enough of these going concurrently and the website slows to a crawl, which is what was happening this AM.
No, thank you.Jeremy wrote:Pretty much.ldsbeaker wrote:Wait, you're saying that I bumped that thread and it killed the website?
I told Skip it was his fault, but if you want to share the blame feel free to take it.
The thread still pulls up in the Google Search, but no thread exists. Dang. That was not my intent.
The thread is gone, and Chris is gone.. hummm.
-
- Posts: 2265
- Joined: Jul 21, 2011 8:05 PM
- Location: Rochester Hills, Michigan
- Contact:
Well, this all happened to me again this morning. I got the 502 3 times, 2 of which were while trying to post a reply the a thread. I tried the IP site too and nothing. I'll assume you were working on something again and I just don't have anything better to do at work at 9 am. lol
Thanks again for keeping this place running!!!
Thanks again for keeping this place running!!!
-
- Posts: 466
- Joined: Jul 06, 2013 10:25 PM
- Location: Cary, NC
This is an issue with the site. It is probably an issue with the front end webserver accessing the database.
http://en.wikipedia.org/wiki/List_of_HT ... rver_Error
If you look at the above site it details the error codes. This will need to be resolved by the system administrator.
HTH
http://en.wikipedia.org/wiki/List_of_HT ... rver_Error
If you look at the above site it details the error codes. This will need to be resolved by the system administrator.
HTH
-
- Posts: 466
- Joined: Jul 06, 2013 10:25 PM
- Location: Cary, NC
No, it isn't Google's fault. The problem manifests when server load is especially high. Site crawlers (from all the various engines) hitting the site certainly increases the load, but it should be able to handle it. We're working on it. It might be a software issue, it might be a hardware issue. It's proving to be a little tough to nail down precisely what the root of the issue is.charter21p5 wrote:So the issue is Google crawling the site causing high cpu on the SQL server?