Stuck sending results 13.82.98.119

[FoldingStorm]

Code: Select all

13:47:34:WU02:FS01:0x22:Completed 1000000 out of 1000000 steps (100%)
13:47:54:WU02:FS01:0x22:Saving result file ..\logfile_01.txt
13:47:54:WU02:FS01:0x22:Saving result file checkpointState.xml
13:47:55:WU02:FS01:0x22:Saving result file checkpt.crc
13:47:55:WU02:FS01:0x22:Saving result file positions.xtc
13:47:55:WU02:FS01:0x22:Saving result file science.log
13:47:55:WU02:FS01:0x22:Folding@home Core Shutdown: FINISHED_UNIT
13:47:56:WU02:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
13:47:56:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
13:47:56:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
13:47:56:WU02:FS01:Connecting to 13.82.98.119:8080
13:48:17:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
13:48:17:WU02:FS01:Connecting to 13.82.98.119:80
13:48:39:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
13:48:39:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
13:48:39:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
13:48:39:WU02:FS01:Connecting to 13.82.98.119:8080
13:49:00:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
13:49:00:WU02:FS01:Connecting to 13.82.98.119:80
13:49:22:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
13:49:39:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
13:49:39:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
13:49:39:WU02:FS01:Connecting to 13.82.98.119:8080
13:50:02:WU02:FS01:Upload 0.26%
13:50:02:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
13:51:16:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
13:51:16:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
13:51:16:WU02:FS01:Connecting to 13.82.98.119:8080
13:51:38:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
13:51:38:WU02:FS01:Connecting to 13.82.98.119:80
13:51:59:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
13:53:53:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
13:53:53:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
13:53:53:WU02:FS01:Connecting to 13.82.98.119:8080
13:54:14:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
13:54:14:WU02:FS01:Connecting to 13.82.98.119:80
13:54:35:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
13:58:08:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
13:58:08:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
13:58:08:WU02:FS01:Connecting to 13.82.98.119:8080
13:58:29:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
13:58:29:WU02:FS01:Connecting to 13.82.98.119:80
13:58:50:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
14:04:59:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:04:59:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:04:59:WU02:FS01:Connecting to 13.82.98.119:8080
14:05:20:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:05:20:WU02:FS01:Connecting to 13.82.98.119:80
14:05:21:WU02:FS01:Upload 0.13%
14:05:45:WU02:FS01:Upload 0.26%
14:05:45:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
14:15:07:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:15:07:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:15:07:WU02:FS01:Connecting to 13.82.98.119:8080
14:15:28:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:15:28:WU02:FS01:Connecting to 13.82.98.119:80
14:15:43:WU02:FS01:Upload 0.13%
14:16:16:WU02:FS01:Upload 0.26%
14:16:16:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
14:16:44:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:16:44:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:16:44:WU02:FS01:Connecting to 13.82.98.119:8080
14:17:06:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:17:06:WU02:FS01:Connecting to 13.82.98.119:80
14:17:27:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
14:19:21:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:19:21:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:19:21:WU02:FS01:Connecting to 13.82.98.119:8080
14:20:59:WU02:FS01:Upload 0.26%
14:20:59:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
14:23:36:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:23:36:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:23:36:WU02:FS01:Connecting to 13.82.98.119:8080
14:24:25:WU02:FS01:Upload 0.26%
14:24:25:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
14:30:27:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:30:27:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:30:27:WU02:FS01:Connecting to 13.82.98.119:8080
14:30:48:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:30:48:WU02:FS01:Connecting to 13.82.98.119:80
14:30:48:WU02:FS01:Upload 0.13%
14:31:13:WU02:FS01:Upload 0.26%
14:31:13:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
14:41:33:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:41:33:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:41:33:WU02:FS01:Connecting to 13.82.98.119:8080
14:41:54:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:41:54:WU02:FS01:Connecting to 13.82.98.119:80
14:42:15:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
14:47:59:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:47:59:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:47:59:WU02:FS01:Connecting to 13.82.98.119:8080
14:49:36:WU02:FS01:Upload 0.26%
14:49:36:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
14:49:36:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:49:36:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:49:36:WU02:FS01:Connecting to 13.82.98.119:8080
14:49:58:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:49:58:WU02:FS01:Connecting to 13.82.98.119:80
14:50:19:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
14:52:14:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:52:14:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:52:14:WU02:FS01:Connecting to 13.82.98.119:8080
14:52:35:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:52:35:WU02:FS01:Connecting to 13.82.98.119:80
14:52:56:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
14:56:28:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
14:56:28:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
14:56:28:WU02:FS01:Connecting to 13.82.98.119:8080
14:56:49:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
14:56:49:WU02:FS01:Connecting to 13.82.98.119:80
14:56:50:WU02:FS01:Upload 0.13%
14:57:58:WU02:FS01:Upload 0.26%
14:57:58:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
15:03:19:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
15:03:19:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
15:03:19:WU02:FS01:Connecting to 13.82.98.119:8080
15:04:58:WU02:FS01:Upload 0.26%
15:04:59:WARNING:WU02:FS01:Exception: Failed to send results to work server: Transfer failed
15:14:25:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13874 run:0 clone:1 gen:24 core:0x22 unit:0x000000260d5262775e7adc2fc6930287
15:14:25:WU02:FS01:Uploading 48.10MiB to 13.82.98.119
15:14:25:WU02:FS01:Connecting to 13.82.98.119:8080
15:14:46:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
15:14:46:WU02:FS01:Connecting to 13.82.98.119:80
15:15:07:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.

Not to mention the massive score drop, due to the server being acting up for hours on end now. The client not trying again for an ever increasing (very long) time period upon failures doesn't help either.

[Neil-B]

https://apps.foldingathome.org/serverstats is showing an uptime of minutes for that server and it has a CS so hopefully it has just been restarted to resolve the issue you are having.

[thatonedude]

I am also having issues with the server. I have been trying to submit completed work all day. I also note that now the server shows as down again

I have also tried exiting out entirely and restarting the client/system.

Code: Select all

*********************** Log Started 2020-04-15T20:15:25Z ***********************
20:15:26:WU03:FS01:Sending unit results: id:03 state:SEND error:NO_ERROR project:14416 run:0 clone:924 gen:7 core:0x22 unit:0x0000000d0d5262775e84c8a798ad31f1
20:15:26:WU03:FS01:Uploading 92.84MiB to 13.82.98.119
20:15:26:WU03:FS01:Connecting to 13.82.98.119:8080
20:15:47:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
20:15:47:WU03:FS01:Connecting to 13.82.98.119:80
*********************** Log Started 2020-04-15T20:15:25Z ***********************
20:15:26:WU03:FS01:Sending unit results: id:03 state:SEND error:NO_ERROR project:14416 run:0 clone:924 gen:7 core:0x22 unit:0x0000000d0d5262775e84c8a798ad31f1
20:15:26:WU03:FS01:Uploading 92.84MiB to 13.82.98.119
20:15:26:WU03:FS01:Connecting to 13.82.98.119:8080
20:15:47:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
20:15:47:WU03:FS01:Connecting to 13.82.98.119:80
20:16:08:WARNING:WU03:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
20:16:09:WU03:FS01:Sending unit results: id:03 state:SEND error:NO_ERROR project:14416 run:0 clone:924 gen:7 core:0x22 unit:0x0000000d0d5262775e84c8a798ad31f1
20:16:09:WU03:FS01:Uploading 92.84MiB to 13.82.98.119
20:16:09:WU03:FS01:Connecting to 13.82.98.119:8080
20:16:30:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
20:16:30:WU03:FS01:Connecting to 13.82.98.119:80
20:16:51:WARNING:WU03:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
20:17:46:WU03:FS01:Sending unit results: id:03 state:SEND error:NO_ERROR project:14416 run:0 clone:924 gen:7 core:0x22 unit:0x0000000d0d5262775e84c8a798ad31f1
20:17:46:WU03:FS01:Uploading 92.84MiB to 13.82.98.119
20:17:46:WU03:FS01:Connecting to 13.82.98.119:8080
20:18:07:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
20:18:07:WU03:FS01:Connecting to 13.82.98.119:80
20:18:28:WARNING:WU03:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
20:20:23:WU03:FS01:Sending unit results: id:03 state:SEND error:NO_ERROR project:14416 run:0 clone:924 gen:7 core:0x22 unit:0x0000000d0d5262775e84c8a798ad31f1
20:20:23:WU03:FS01:Uploading 92.84MiB to 13.82.98.119
20:20:23:WU03:FS01:Connecting to 13.82.98.119:8080
20:20:44:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
20:20:44:WU03:FS01:Connecting to 13.82.98.119:80
20:21:05:WARNING:WU03:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
20:24:37:WU03:FS01:Sending unit results: id:03 state:SEND error:NO_ERROR project:14416 run:0 clone:924 gen:7 core:0x22 unit:0x0000000d0d5262775e84c8a798ad31f1
20:24:38:WU03:FS01:Uploading 92.84MiB to 13.82.98.119
20:24:38:WU03:FS01:Connecting to 13.82.98.119:8080
20:24:59:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
20:24:59:WU03:FS01:Connecting to 13.82.98.119:80
20:25:20:WARNING:WU03:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.
20:31:29:WU03:FS01:Sending unit results: id:03 state:SEND error:NO_ERROR project:14416 run:0 clone:924 gen:7 core:0x22 unit:0x0000000d0d5262775e84c8a798ad31f1
20:31:29:WU03:FS01:Uploading 92.84MiB to 13.82.98.119
20:31:29:WU03:FS01:Connecting to 13.82.98.119:8080
20:31:51:WARNING:WU03:FS01:WorkServer connection failed on port 8080 trying 80
20:31:51:WU03:FS01:Connecting to 13.82.98.119:80
20:32:12:WARNING:WU03:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: 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.

[PantherX]

Welcome to the F@H Forum thatonedude,

Please note that if the Server is down on the Status page, that would indicate a problem on the Server end so restarting your client/system unfortunately won't fix that.

Once that Server (or Collection Server) is available, the client will automatically upload the completed WU.

[FoldingStorm]

It's not using the collection server for some reason, and still didn't upload the results. Continues to fail to upload, meanwhile score goes towards zero very quickly. If there are server isssues it should really give you credit. Not sure how, since I get the cheating possibility and generally agree with how it's being done, but still...
I mean it's an Azure server, that shouldn't be down like ever...

[durval]

Exact same issue here:

Code: Select all

22:40:40:WU02:FS01:Connecting to 13.82.98.119:8080
22:42:51:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
22:42:51:WU02:FS01:Connecting to 13.82.98.119:80
22:45:02:WARNING:WU02:FS01:Exception: Failed to send results to work server: Failed to connect to 13.82.98.119:80: Connection timed out

Rinse and repeat, over and over again -- this has been happening for hours already, and I have already finished two other WUs, so it's a big queue here with nowhere to go

When the server comes back up and we are all able to upload the work done, won't our QRBs get penalized? What about timeouts (or worse, deadlines)?

Cheers,
-- Durval.

[durval]

Hello @FoldingStorm,

I mean it's an Azure server, that shouldn't be down like ever...

Azure?! Eeech :-/ Coming from Microsoft, the makers of the most unstable OSes ever (Windows and its ilk), this doesn't surprise me at all...

[durval]

Hi Neil,

https://apps.foldingathome.org/serverstats is showing an uptime of minutes for that server and it has a CS so hopefully it has just been restarted to resolve the issue you are having.

What exactly means "having a CS"?

Thanks in advance for any clarification,
-- Durval.

[Joe_H]

A Collection Server may be defined for a project as an alternate place to upload to if the Work Server is unavailable. It has to have been defined at the time a WU was downloaded.

[durval]

A Collection Server may be defined for a project as an alternate place to upload to if the Work Server is unavailable. It has to have been defined at the time a WU was downloaded.

Thanks for the info, @Joe_H. My client is just trying the server at 13.82.98.119 over and over again, without trying any other IP addresses -- this server is marked on the server table with "Has CS: Yes", so I guess that it was not so today at 2020-04-15T09:04:16Z when it downloaded this WU

[durval]

Another question: the server status page is showing this particular server has been down for over 8 hours already. What's the big deal with bringing it up? As it is a cloud server, isn't it supposed to be able to be brought back in a matter of minutes (at least it is so with AWS -- Azure probably is worse, but even then this delay sounds too large).

[PantherX]

...When the server comes back up and we are all able to upload the work done, won't our QRBs get penalized? What about timeouts (or worse, deadlines)?...

When the Server is back online, it will be able to process incoming WUs based on the hardware and bandwidth limitations. Unfortunately, your QRB would be impacted as it is calculated from the time the new WU was assigned to your system to when the completed WU was successfully uploaded.

If the WU reaches the Timeout date, the WS will make a note of it and will reassign it. If you complete that WU and upload it, you will get base points.

If the WU reaches the Expiration date, the client on yous system will delete it automatically.

Another question: the server status page is showing this particular server has been down for over 8 hours already. What's the big deal with bringing it up? As it is a cloud server, isn't it supposed to be able to be brought back in a matter of minutes (at least it is so with AWS -- Azure probably is worse, but even then this delay sounds too large).

Down isn't a simple status like an unplugged LAN cable. It means that the Server is not assigning new WUs nor is receiving completed WUs (viewtopic.php?f=18&t=17794). Investigation will require human effort to perform whatever fix is needed and the time it needs. If you're copying TBs of data, it can take a while depending on many factors.

[durval]

Hello @PantherX,

Thanks for the explanations. Just a small matter:

Another question: the server status page is showing this particular server has been down for over 8 hours already. What's the big deal with bringing it up? As it is a cloud server, isn't it supposed to be able to be brought back in a matter of minutes (at least it is so with AWS -- Azure probably is worse, but even then this delay sounds too large).

Down isn't a simple status like an unplugged LAN cable. It means that the Server is not assigning new WUs nor is receiving completed WUs (viewtopic.php?f=18&t=17794). Investigation will require human effort to perform whatever fix is needed and the time it needs. If you're copying TBs of data, it can take a while depending on many factors.

My client is reporting "Connection timed out", so (with all due respect) I beg to differ: it's not some "logical" problem like not assigning new WUs -- on the contrary, it means the IP address assigned to the server is not answering. It could be because the server has crashed (the OS, not the F@H software), it has been powered down, or even (sorry) that its LAN cable has indeed been unplugged. Otherwise we would be seeing other errors like "Connection reset".

Anyway, the server just came back, and responded to the upload by dumping my hard-earned WU:

00:26:50:WU04:FS01:Upload complete
00:26:50:WU04:FS01:Server responded WORK_QUIT (404)
00:26:50:WARNING:WU04:FS01:Server did not like results, dumping

Does that mean that it was all in vain?

[Epsilon_Process]

The server was up for a while, but is down again as shown in Server Stats. It could just be extremely backlogged.

When capturing with Wireshark, I got continuous TCP Retransmissions, even when just hitting http://13.82.98.119:8080 with a web browser.

So I guess we need to wait a little longer.

[VAcharonD1]

I'm still timing out when trying to connect. My WU is going to time out soon, too.