Page 2 of 4 FirstFirst 1234 LastLast
Results 21 to 40 of 66
  1. #21  
    Consecutive 504 Gateway Timeout between 5:02 and 5:09PM Pacific
  2. #22  
    All requests to m.forums.precentral.net from my Pre returns a 400 Bad Ruquest. But it works fine from my laptop (Safari 4)
    8:56pm EDT 7/29/09
  3. #23  
    Quote Originally Posted by rpboyles View Post
    All requests to m.forums.precentral.net from my Pre returns a 400 Bad Ruquest. But it works fine from my laptop (Safari 4)
    8:56pm EDT 7/29/09
    Same here, for quite a few days now.
  4.    #24  
    still looking into this stuff.

    please provide location more specific than time zone too, if you don't mind. City ideally.
  5. #25  
    Quote Originally Posted by rpboyles View Post
    All requests to m.forums.precentral.net from my Pre returns a 400 Bad Ruquest. But it works fine from my laptop (Safari 4)
    8:56pm EDT 7/29/09
    Checking again today, I again got 400 Bad Request from Pre, but fine on Safari. Cleared my cache, cookies, history. Then m.forums.precentral.net loads up just fine. Did this today at 7:15 EDT from Raleigh, NC.
  6. #26  
    Again:

    504 Gateway Time-out
    nginx

    10:22pm Pacific-Northwest

    Firefox/3.5.1
    Just call me Berd.
  7.    #27  
    New servers have arrived!! As to when we'll get them configured and installed and on the farm, I can't quite say. But the machines, they are here.
  8. #28  
    Quote Originally Posted by rpboyles View Post
    Checking again today, I again got 400 Bad Request from Pre, but fine on Safari. Cleared my cache, cookies, history. Then m.forums.precentral.net loads up just fine. Did this today at 7:15 EDT from Raleigh, NC.
    With all the weird errors happening I never thought to try this. I haven't been able to access the mobile site for nearly a week. Worked! Thanks!
  9. #29  
    On 8/6/09 at 12:15am CST from Chicago using Firefox 3.5.2 I got this:

    My Phone & My Wife's Phone Two Unlocked GSM Treo Pro's

  10. #30  
    I am getting 400 Bad Request nginx errors from my Pre, but only on some forums but not others. I am in newark, nj - at the terminal A presidents club. Going to try and clear cache / cookies / history to see if it fixes the problem

    Edit: clear cache and history did not fix it, but clear cookies seemed to do the trick
  11. #31  
    8/10/2009 10:51PM CST Chicago, IL

    504 Gateway Time-out
    My Phone & My Wife's Phone Two Unlocked GSM Treo Pro's

  12. #32  
    08/12/2009 11:56PM CST Chicago, IL FireFox 3.5.2

    504 Gateway Time-out

    08/13/2009 12:19AM CST Chicago, IL FireFox 3.5.2

    504 Gateway Time-out
    Last edited by palandri; 08/13/2009 at 12:24 AM.
    My Phone & My Wife's Phone Two Unlocked GSM Treo Pro's

  13. #33  
    8/14/09 I got two 504 Gateway Time-out starting at around 12:02am to 12:06am. Chicago, IL

    8/14/09 504 Gateway Time-out at 12:19am

    8/14/09 504 Gateway Time-out at 12:22am
    Last edited by palandri; 08/14/2009 at 12:23 AM.
    My Phone & My Wife's Phone Two Unlocked GSM Treo Pro's

  14. #34  
    One 504 Gateway Time-out today at 10:32PM Pacific
  15. #35  
    8/20/09 12:19am and 12:22am 504 Gateway Time-out Chicago, IL
    My Phone & My Wife's Phone Two Unlocked GSM Treo Pro's

  16. #36  
    8/20/09 12:19am and 12:22am 504 Gateway Time-out Chicago, IL

    Now at 12:25am trying to post this, 504 Gateway Time-out
    My Phone & My Wife's Phone Two Unlocked GSM Treo Pro's

  17. #37  
    504 Gateway Timeout at 10:30PM Pacific
  18. #38  
    504 Gateway Timeout at 10:58PM Pacific
    Just call me Berd.
  19. #39  
    I got the 400 Bad Request around 7:00 pm Pacific on my Pre's browser when trying to view the WebOS Development forum. I haven't cleared my cookies since I don't want to re-login to every forum site I visit. Wasn't the new serves supposed to fix this issue?
  20. #40  
    Can you run a tracecert from your PC to either discussion.treocentral.com or forums.precentral.net depending on how you are connecting to and send that info to either Dieter or myself via PM?

    We are thinking that the routing through Utah data center is causing the problem for west coast users.

    Thanks
Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions