Yesterday, in a post regarding the Moscow pop, I pointed out that an instance server hosted on 140.174.177.* was causing issues because it's dead! It's still dead and whenever that instance host comes up it results in a disconnect.
Please fix it.
"
2025/07/14 17:15:15 33228805 82998930 [INFO Client 324] [SHADER] Delay: OFF
2025/07/14 17:15:15 33228805 ca3a6a33 [INFO Client 324] Connecting to instance server at 140.174.177.119:6112
2025/07/14 17:15:51 33264916 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/14 17:15:51 33264916 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
The node doesn't respond to any kind of probe. It was dead yesterday and it's still dead today!
Last bumped on Jul 16, 2025, 5:46:01 PM
|
Posted byKellog#5737on Jul 14, 2025, 4:51:43 AM
|
Another day. It's still dead, Jim!
"
2025/07/15 10:57:37 11989748 ca3a6a33 [INFO Client 324] Connecting to instance server at 140.174.177.137:6112
2025/07/15 10:58:13 12025627 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/15 10:58:13 12025627 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
Oh, by the way, I can't login today because of this! Last edited by Kellog#5737 on Jul 14, 2025, 9:03:17 PM
|
Posted byKellog#5737on Jul 14, 2025, 9:00:56 PM
|
Day 4: some nodes still dead:
"
2025/07/16 09:12:44 5958494 ca3a6a33 [INFO Client 324] Connecting to instance server at 140.174.177.125:6112
2025/07/16 09:13:20 5994344 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/16 09:13:20 5994344 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
Can't login again!
Last edited by Kellog#5737 on Jul 15, 2025, 7:15:18 PM
|
Posted byKellog#5737on Jul 15, 2025, 7:10:59 PM
|
And again!
"
2025/07/16 11:12:53 13167243 ca3a6a33 [INFO Client 324] Connecting to instance server at 140.174.177.5:6112
2025/07/16 11:13:29 13203336 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/16 11:13:29 13203336 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
|
Posted byKellog#5737on Jul 15, 2025, 9:14:55 PM
|
It just continued yesterday, essentially every hour. At 17:00 I just gave up and logged out.
I've emailed support with this.
"
2025/07/16 15:37:49 29063225 ca3a6a33 [INFO Client 324] Connecting to instance server at 108.181.60.121:6112
2025/07/16 15:38:25 29098937 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/16 15:38:25 29098937 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
2025/07/16 16:05:11 30704910 ca3a6a33 [INFO Client 324] Connecting to instance server at 140.174.177.125:6112
2025/07/16 16:05:47 30740929 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/16 16:05:47 30740929 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
2025/07/16 16:09:58 30991943 ca3a6a33 [INFO Client 324] Connecting to instance server at 140.174.177.7:6112
2025/07/16 16:10:33 31027645 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/16 16:10:33 31027645 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
2025/07/16 17:07:13 34427759 ca3a6a33 [INFO Client 324] Connecting to instance server at 140.174.177.5:6112
2025/07/16 17:07:49 34463688 ca3a5130 [DEBUG Client 324] Connect time to instance server was 0ms
2025/07/16 17:07:49 34463688 aeceacbb [INFO Client 324] Abnormal disconnect: Failed to connect to instance
|
Posted byKellog#5737on Jul 16, 2025, 5:46:01 PM
|
