After 7 hours, I still can't get anything but timeouts trying to hit my site via https (which is required as part of the authentication, so I can't log in at all) -- a few friends are reporting no problems, but at least one other person is reporting the same errors I see.
504 Gateway Time-out
nginx/0.8.54
And I'm getting this at home and at work, with no regard for browser or anything else. Help!
#1 Posted by friism Support staff on 01 Apr, 2011 06:54 AM
The server where your site was on may have been having some load-issues, which we are working on resolving. In the meantime, I have moved your site to a different server.
At no time have I been able to reproduce 504's for your site, so please let me know if the problem persists on your end.
#2 Posted by Dakuan on 01 Apr, 2011 12:38 PM
same for me :(
http://ssa.apphb.com/
#3 Posted by Jaykul on 01 Apr, 2011 01:53 PM
That's really frustrating, since I'm still getting 504's ... but only when using https (which was working, before). And I have no way of knowing how many other people might be affected, since it's a site where almost everyone visiting it will need to log in.
http://2011sg.poshcode.org/ works fine.
https://2011sg.poshcode.org/ results in a 504 every time.
Based on comments on the other thread, I tried publishing an update, or an old copy of the app, but the app itself still seems to be working (obviously, when I leave off the "s" it works fine, but I can't authenticate), and those deploys had no visible effect.
Is there anything I can do to help you detect what the problem is? Give you my IP addresses (at work I'm behind the Xerox corporate proxy which is always something like 13.13.137.1 ... and at home, well, you can do a DNS lookup on jaykul.org and that's my home IP address) so you can look it up, or anything?
By the way ... I do not get 504's connecting to http://ssa.apphb.com/ ... do you get them connecting to my site, @Dom?
#4 Posted by friism Support staff on 01 Apr, 2011 05:18 PM
@Dom, for the ssa app, it looks like you're doing synchronous requests to Flickr, and that Flickr does not respond in a timely manner. If I circumvent the load-balancer, I get YSOD's with errors like
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 68.142.214.24:80and a stacktrace out of FlickrNet.We're investigating whether we should increase nginx timeouts so that you can debug stuff like this yourselves.
@jaykul, still investigating what's going on with your app.
#5 Posted by friism Support staff on 01 Apr, 2011 05:20 PM
@jaykul when you say you get 504's for https://2011sg.poshcode.org/, is that also for simple
GET's for the frontpage, or only when you attempt to log in?#6 Posted by Jaykul on 02 Apr, 2011 12:37 AM
It was for simple GETs too.
It seems to have cleared up now ... and I'm mystified. fingers crossed
#7 Posted by Patrik Potocki on 02 Apr, 2011 02:02 PM
http://cashflow.apphb.com also getting 504 :(
friism closed this discussion on 20 Jul, 2011 11:34 PM.