Bad Gateway, empty solutions list ( was: Network issues also affect foldit website)

Started by Bletchley Park

Bletchley Park Lv 1

Here is a trace while the foldit website was not reachable for hours and old clients died:

 11    82 ms    87 ms    82 ms  bundle-ether410.agg1.newy2.net.internet2.edu [162.252.69.4]
 12   145 ms   145 ms   144 ms  fourhundredge-0-0-0-2.4079.core1.newy32aoa.net.internet2.edu [163.253.2.122]
 13   146 ms   145 ms   145 ms  fourhundredge-0-0-0-2.4079.core1.ashb.net.internet2.edu [163.253.1.116]
 14   145 ms   146 ms   145 ms  fourhundredge-0-0-0-17.4079.core2.ashb.net.internet2.edu [163.253.1.9]
 15   146 ms   144 ms   144 ms  fourhundredge-0-0-0-1.4079.core2.clev.net.internet2.edu [163.253.1.139]
 16   145 ms   145 ms   144 ms  fourhundredge-0-0-0-2.4079.core2.eqch.net.internet2.edu [163.253.2.17]
 17   144 ms   145 ms   146 ms  fourhundredge-0-0-0-2.4079.core2.chic.net.internet2.edu [163.253.2.18]
 18   144 ms   147 ms   145 ms  fourhundredge-0-0-0-1.4079.core1.kans.net.internet2.edu [163.253.1.245]
 19   144 ms   144 ms   145 ms  fourhundredge-0-0-0-1.4079.core1.denv.net.internet2.edu [163.253.1.242]
 20   143 ms   145 ms   146 ms  fourhundredge-0-0-0-3.4079.core1.salt.net.internet2.edu [163.253.1.171]
 21   146 ms   144 ms   145 ms  fourhundredge-0-0-0-1.4079.core1.seat.net.internet2.edu [163.253.1.157]
 22   143 ms   143 ms   153 ms  198.71.47.6
 23   144 ms   143 ms   144 ms  et-7-0-0--4010.uwcr-atg-1.infra.washington.edu [209.124.188.135]
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

So any network issue is happening within the university infrastructure.

The trace is the same when the website is up, performed just now:

11    86 ms    84 ms    83 ms  bundle-ether410.agg1.newy2.net.internet2.edu [162.252.69.4]
 12   146 ms   147 ms   144 ms  fourhundredge-0-0-0-2.4079.core1.newy32aoa.net.internet2.edu [163.253.2.122]
 13   145 ms   143 ms   145 ms  fourhundredge-0-0-0-2.4079.core1.ashb.net.internet2.edu [163.253.1.116]
 14   146 ms   148 ms   144 ms  fourhundredge-0-0-0-17.4079.core2.ashb.net.internet2.edu [163.253.1.9]
 15   144 ms   143 ms   142 ms  fourhundredge-0-0-0-1.4079.core2.clev.net.internet2.edu [163.253.1.139]
 16   144 ms   144 ms   144 ms  fourhundredge-0-0-0-2.4079.core2.eqch.net.internet2.edu [163.253.2.17]
 17   144 ms   148 ms   147 ms  fourhundredge-0-0-0-2.4079.core2.chic.net.internet2.edu [163.253.2.18]
 18   165 ms   146 ms   146 ms  fourhundredge-0-0-0-1.4079.core1.kans.net.internet2.edu [163.253.1.245]
 19   147 ms   146 ms   144 ms  fourhundredge-0-0-0-1.4079.core1.denv.net.internet2.edu [163.253.1.242]
 20   147 ms   144 ms   144 ms  fourhundredge-0-0-0-3.4079.core1.salt.net.internet2.edu [163.253.1.171]
 21   146 ms   144 ms   146 ms  fourhundredge-0-0-0-1.4079.core1.seat.net.internet2.edu [163.253.1.157]
 22   142 ms   142 ms   149 ms  198.71.47.6
 23   143 ms   142 ms   144 ms  et-7-0-0--4010.uwcr-atg-1.infra.washington.edu [209.124.188.135]
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Bletchley Park Lv 1

Also today there are numerous network issues, causing chat to die, clients to die (version 39 !) Please investigate your network issues.

Bletchley Park Lv 1

Could it be that you are running a rather 'thin' server to handle all foldit traffic ?
How many parallel client sessions can you handle ? How much memory does it have ? Networking ? Network configuration (do you have multiple gateways defined by chance ?) ?

Bletchley Park Lv 1

HTTP 502

The 502 Bad Gateway error is an HTTP status code that occurs when a server acting as a gateway or proxy receives an invalid or faulty response from another server in the communication chain. This error indicates a problem with the communication between the involved servers and can result in disruption of internet services. Wikipedia

I have thousands of dollars worth of equipment exclusively allocated to your project sitting idle because the root issue is not addressed.

beta_helix Staff Lv 1

@bp we are addressing it… but it is taking way longer than we all want. :-(

We know how frustrating this is (it's extremely frustrating for us as well, especially during CASP), but we are putting all the resources at our disposal to solve this (and the sharing solutions issue). This has halted all improvements to the game, such as the Trim Tool in Lua which we had hoped to post last month.

LociOiling Lv 1

I notice that opening shared solution is working for me again on all three puzzles.

Not only that, but the list of shared solutions appeared quickly.

@jflat06 confirmed that he made a server change, which seems to have fixed things.

I still get a "can't open file" error when I try to load a shared solution, but then it works on the second attempt.

beta_helix Staff Lv 1

Yeah, we're aware of the "can't open file" error.

You can get around it by clicking Download first, then Load… but we will try to fix this bug as soon as the server issues are resolved.