Home – New Forums Other discussions Getting ‘502 Bad Gateway’ on Chrome Canary

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #978808
    adrian
    Participant
    • Total posts: 181
    Up
    0
    ::

    Just a heads up for site admins. I’m getting the following error on the latest Chrome Canary builds:

    502 Bad Gateway
    nginx/0.7.67

    It works fine with regular Chrome. These errors don’t seem to come up for older threads, only recent threads – news threads returns this error as soon as I select the thread from a list of threads. I’m not sure if it’s a relative age cutoff, or a cutoff from a specific thread creation time. Old threads with new replies don’t get the error.

    This may go away with a new build of Chrome Canary. But it’s been this way for a couple of days, so I thought a heads up was in order.

    Cheers

    #1109650
    Peter – FS Administrator
    Member
    • Total posts: 1,889
    Up
    0
    ::

    Thanks Adrian,
    Appreciate you taking the time to report this and for all the detail.
    It will help us investigate.
    Cheers
    Peter

    #1109651
    adrian
    Participant
    • Total posts: 181
    Up
    0
    ::

    OK, today’s Canary update (updates most days) seems to have resolved this.

    It really has me curious what was happening though, and if it will return. I’m guessing it’s something to do with caching on the server side that caused issues with chrome? Can’t think why else client side issues could be age of post related….

    If it comes back, I’ll do a little digging from the client side, just for kicks.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.