Client suddenly stopped being able to connect to get new WU

If you think it might be a driver problem, see viewforum.php?f=79

Moderators: Site Moderators, FAHC Science Team

Post Reply
Prettz
Posts: 19
Joined: Sat Oct 17, 2009 6:47 pm

Client suddenly stopped being able to connect to get new WU

Post by Prettz »

My client is unable to connect to the server for GPU work units. This occurred while it was running uninterrupted for a few days, without problems, until I checked in on it last night, and saw it couldn't download a new WU and had given up. I've tried restarting FAH several times and restarting the computer, with no effect. I have the latest video drivers.

Here is an example log:

Code: Select all

19:03:15:FS01:Unpaused
19:03:16:WU01:FS01:Connecting to 13.59.134.176:8080
19:03:16:WU01:FS01:Assigned to work server 192.0.2.1
19:03:16:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GB205 [GeForce RTX 5070] from 192.0.2.1
19:03:16:WU01:FS01:Connecting to 192.0.2.1:8080
19:03:18:26:127.0.0.1 GET /api/updates?_=1765479779413&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:20:30:127.0.0.1 GET /api/updates?_=1765479779414&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:23:30:127.0.0.1 GET /api/updates?_=1765479779415&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:26:26:127.0.0.1 GET /api/updates?_=1765479779416&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:27:26:127.0.0.1 GET /api/updates?_=1765479779417&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:28:26:127.0.0.1 GET /api/updates?_=1765479779418&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:31:30:127.0.0.1 GET /api/updates?_=1765479779419&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:33:26:127.0.0.1 GET /api/updates?_=1765479779420&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:36:26:127.0.0.1 GET /api/updates?_=1765479779421&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:37:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
19:03:37:WU01:FS01:Connecting to 192.0.2.1:80
19:03:39:30:127.0.0.1 GET /api/updates?_=1765479779422&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:41:26:127.0.0.1 GET /api/updates?_=1765479779423&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:44:26:127.0.0.1 GET /api/updates?_=1765479779424&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:47:30:127.0.0.1 GET /api/updates?_=1765479779425&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:49:26:127.0.0.1 GET /api/updates?_=1765479779426&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:52:26:127.0.0.1 GET /api/updates?_=1765479779427&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:55:30:127.0.0.1 GET /api/updates?_=1765479779428&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:58:26:127.0.0.1 GET /api/updates?_=1765479779429&sid=3c33fa8421edc63f9c2ff3237369f875
19:03:58:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1: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.
19:03:58:WU01:FS01:Connecting to 13.59.134.176:8080
19:03:59:WU01:FS01:Assigned to work server 192.0.2.1
19:03:59:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GB205 [GeForce RTX 5070] from 192.0.2.1
19:03:59:WU01:FS01:Connecting to 192.0.2.1:8080
19:04:00:26:127.0.0.1 GET /api/updates?_=1765479779430&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:03:30:127.0.0.1 GET /api/updates?_=1765479779431&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:06:26:127.0.0.1 GET /api/updates?_=1765479779432&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:08:26:127.0.0.1 GET /api/updates?_=1765479779433&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:11:30:127.0.0.1 GET /api/updates?_=1765479779434&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:14:26:127.0.0.1 GET /api/updates?_=1765479779435&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:15:26:127.0.0.1 GET /api/updates?_=1765479779436&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:17:26:127.0.0.1 GET /api/updates?_=1765479779437&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:18:26:127.0.0.1 GET /api/updates?_=1765479779438&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:18:26:127.0.0.1 GET /api/updates?_=1765479779439&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:19:30:127.0.0.1 GET /api/updates?_=1765479779440&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:20:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
19:04:20:WU01:FS01:Connecting to 192.0.2.1:80
19:04:21:26:127.0.0.1 GET /api/updates?_=1765479779441&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:23:30:127.0.0.1 GET /api/updates?_=1765479779442&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:24:26:127.0.0.1 GET /api/updates?_=1765479779443&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:25:30:127.0.0.1 GET /api/updates?_=1765479779444&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:27:26:127.0.0.1 GET /api/updates?_=1765479779445&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:29:30:127.0.0.1 GET /api/updates?_=1765479779446&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:30:30:127.0.0.1 GET /api/updates?_=1765479779447&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:31:30:127.0.0.1 GET /api/updates?_=1765479779448&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:33:30:127.0.0.1 GET /api/updates?_=1765479779449&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:34:30:127.0.0.1 GET /api/updates?_=1765479779450&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:35:30:127.0.0.1 GET /api/updates?_=1765479779451&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:36:30:127.0.0.1 GET /api/updates?_=1765479779452&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:37:30:127.0.0.1 GET /api/updates?_=1765479779453&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:38:30:127.0.0.1 GET /api/updates?_=1765479779454&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:39:30:127.0.0.1 GET /api/updates?_=1765479779455&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:40:26:127.0.0.1 GET /api/updates?_=1765479779456&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:41:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1: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.
19:04:41:26:127.0.0.1 GET /api/updates?_=1765479779457&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:42:26:127.0.0.1 GET /api/updates?_=1765479779458&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:44:30:127.0.0.1 GET /api/updates?_=1765479779459&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:48:26:127.0.0.1 GET /api/updates?_=1765479779460&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:49:26:127.0.0.1 GET /api/updates?_=1765479779461&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:50:26:127.0.0.1 GET /api/updates?_=1765479779462&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:51:26:127.0.0.1 GET /api/updates?_=1765479779463&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:52:26:127.0.0.1 GET /api/updates?_=1765479779464&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:54:30:127.0.0.1 GET /api/updates?_=1765479779465&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:57:30:127.0.0.1 GET /api/updates?_=1765479779466&sid=3c33fa8421edc63f9c2ff3237369f875
19:04:59:WU01:FS01:Connecting to 13.59.134.176:8080
19:04:59:WU01:FS01:Assigned to work server 192.0.2.1
19:04:59:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GB205 [GeForce RTX 5070] from 192.0.2.1
19:04:59:WU01:FS01:Connecting to 192.0.2.1:8080
19:05:00:26:127.0.0.1 GET /api/updates?_=1765479779467&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:02:30:127.0.0.1 GET /api/updates?_=1765479779468&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:05:30:127.0.0.1 GET /api/updates?_=1765479779469&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:08:26:127.0.0.1 GET /api/updates?_=1765479779470&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:10:30:127.0.0.1 GET /api/updates?_=1765479779471&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:13:30:127.0.0.1 GET /api/updates?_=1765479779472&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:16:26:127.0.0.1 GET /api/updates?_=1765479779473&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:18:30:127.0.0.1 GET /api/updates?_=1765479779474&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:20:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
19:05:20:WU01:FS01:Connecting to 192.0.2.1:80
19:05:21:30:127.0.0.1 GET /api/updates?_=1765479779475&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:24:26:127.0.0.1 GET /api/updates?_=1765479779476&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:27:30:127.0.0.1 GET /api/updates?_=1765479779477&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:28:30:127.0.0.1 GET /api/updates?_=1765479779478&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:29:30:127.0.0.1 GET /api/updates?_=1765479779479&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:30:30:127.0.0.1 GET /api/updates?_=1765479779480&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:31:30:127.0.0.1 GET /api/updates?_=1765479779481&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:32:26:127.0.0.1 GET /api/updates?_=1765479779482&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:34:30:127.0.0.1 GET /api/updates?_=1765479779483&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:35:26:127.0.0.1 GET /api/updates?_=1765479779484&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:38:30:127.0.0.1 GET /api/updates?_=1765479779485&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:39:26:127.0.0.1 GET /api/updates?_=1765479779486&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:40:26:127.0.0.1 GET /api/updates?_=1765479779487&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:41:26:127.0.0.1 GET /api/updates?_=1765479779488&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:41:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1: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.
19:05:42:26:127.0.0.1 GET /api/updates?_=1765479779489&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:43:26:127.0.0.1 GET /api/updates?_=1765479779490&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:46:30:127.0.0.1 GET /api/updates?_=1765479779491&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:48:26:127.0.0.1 GET /api/updates?_=1765479779492&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:51:26:127.0.0.1 GET /api/updates?_=1765479779493&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:54:30:127.0.0.1 GET /api/updates?_=1765479779494&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:56:26:127.0.0.1 GET /api/updates?_=1765479779495&sid=3c33fa8421edc63f9c2ff3237369f875
19:05:59:26:127.0.0.1 GET /api/updates?_=1765479779496&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:02:30:127.0.0.1 GET /api/updates?_=1765479779497&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:04:26:127.0.0.1 GET /api/updates?_=1765479779498&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:07:26:127.0.0.1 GET /api/updates?_=1765479779499&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:10:30:127.0.0.1 GET /api/updates?_=1765479779500&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:11:30:127.0.0.1 GET /api/updates?_=1765479779501&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:12:30:127.0.0.1 GET /api/updates?_=1765479779502&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:13:30:127.0.0.1 GET /api/updates?_=1765479779503&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:14:30:127.0.0.1 GET /api/updates?_=1765479779504&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:15:26:127.0.0.1 GET /api/updates?_=1765479779505&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:16:26:127.0.0.1 GET /api/updates?_=1765479779506&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:17:26:127.0.0.1 GET /api/updates?_=1765479779507&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:20:30:127.0.0.1 GET /api/updates?_=1765479779508&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:21:30:127.0.0.1 GET /api/updates?_=1765479779509&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:22:30:127.0.0.1 GET /api/updates?_=1765479779510&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:23:30:127.0.0.1 GET /api/updates?_=1765479779511&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:24:30:127.0.0.1 GET /api/updates?_=1765479779512&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:25:26:127.0.0.1 GET /api/updates?_=1765479779513&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:27:30:127.0.0.1 GET /api/updates?_=1765479779514&sid=3c33fa8421edc63f9c2ff3237369f875
19:06:36:WU01:FS01:Connecting to 13.59.134.176:8080
19:06:36:WU01:FS01:Assigned to work server 192.0.2.1
19:06:36:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GB205 [GeForce RTX 5070] from 192.0.2.1
19:06:36:WU01:FS01:Connecting to 192.0.2.1:8080
19:06:57:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
19:06:57:WU01:FS01:Connecting to 192.0.2.1:80
19:07:18:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1: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.
19:09:13:WU01:FS01:Connecting to 13.59.134.176:8080
19:09:13:WU01:FS01:Assigned to work server 192.0.2.1
19:09:13:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GB205 [GeForce RTX 5070] from 192.0.2.1
19:09:13:WU01:FS01:Connecting to 192.0.2.1:8080
19:09:34:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
19:09:34:WU01:FS01:Connecting to 192.0.2.1:80
19:09:56:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1: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.
I'm at a loss as to what could have changed, since it had been running just fine. I don't know what the repeated calls to /api/updates is about, either. What is that?
Top
muziqaz
Posts: 2341
Joined: Sun Dec 16, 2007 6:22 pm
Hardware configuration: 9950x, 9950x3d, 7950x3d, 5950x, 5800x3d
7900xtx, RX9070, Radeon 7, 5700xt, 6900xt, RX550, Intel B580
Location: London
Contact:
Contact muziqaz

Re: Client suddenly stopped being able to connect to get new WU

Post by muziqaz »

What is your username on FAH?
FAH Omega tester
Image
Top
Prettz
Posts: 19
Joined: Sat Oct 17, 2009 6:47 pm

Re: Client suddenly stopped being able to connect to get new WU

Post by Prettz »

muziqaz wrote: ↑Thu Dec 11, 2025 7:27 pm What is your username on FAH?
It's Prettz. Why?
Top
muziqaz
Posts: 2341
Joined: Sun Dec 16, 2007 6:22 pm
Hardware configuration: 9950x, 9950x3d, 7950x3d, 5950x, 5800x3d
7900xtx, RX9070, Radeon 7, 5700xt, 6900xt, RX550, Intel B580
Location: London
Contact:
Contact muziqaz

Re: Client suddenly stopped being able to connect to get new WU

Post by muziqaz »

Prettz wrote: ↑Fri Dec 12, 2025 11:43 pm
muziqaz wrote: ↑Thu Dec 11, 2025 7:27 pm What is your username on FAH?
It's Prettz. Why?
Checking if you were blacklisted or something, which doesn't look to be the case.
Are you on wifi by any chance?
FAH Omega tester
Image
Top
Prettz
Posts: 19
Joined: Sat Oct 17, 2009 6:47 pm

Re: Client suddenly stopped being able to connect to get new WU

Post by Prettz »

muziqaz wrote: ↑Fri Dec 12, 2025 11:56 pm
Prettz wrote: ↑Fri Dec 12, 2025 11:43 pm
muziqaz wrote: ↑Thu Dec 11, 2025 7:27 pm What is your username on FAH?
It's Prettz. Why?
Checking if you were blacklisted or something, which doesn't look to be the case.
Are you on wifi by any chance?
Not on wifi, and I confirmed that I can still connect to get a CPU work unit, although I no longer run those.
I've also tried deleting files from the folder in AppData. I don't really know what does what, but I deleted everything in the work and configs folders, and FAHControl.db, with no effect. Are there any other files I can try to edit or delete? Or maybe just uninstall the whole thing?
Top
muziqaz
Posts: 2341
Joined: Sun Dec 16, 2007 6:22 pm
Hardware configuration: 9950x, 9950x3d, 7950x3d, 5950x, 5800x3d
7900xtx, RX9070, Radeon 7, 5700xt, 6900xt, RX550, Intel B580
Location: London
Contact:
Contact muziqaz

Re: Client suddenly stopped being able to connect to get new WU

Post by muziqaz »

Prettz wrote: ↑Sat Dec 13, 2025 3:18 am
muziqaz wrote: ↑Fri Dec 12, 2025 11:56 pm
Prettz wrote: ↑Fri Dec 12, 2025 11:43 pm
It's Prettz. Why?
Checking if you were blacklisted or something, which doesn't look to be the case.
Are you on wifi by any chance?
Not on wifi, and I confirmed that I can still connect to get a CPU work unit, although I no longer run those.
I've also tried deleting files from the folder in AppData. I don't really know what does what, but I deleted everything in the work and configs folders, and FAHControl.db, with no effect. Are there any other files I can try to edit or delete? Or maybe just uninstall the whole thing?
Deleting files while FAH is still installed in general is a bad idea. best to uninstall FAH first, then delete the remaining files. Is this windows or linux, btw?
FAH Omega tester
Image
Top
toTOW
Site Moderator
Posts: 6525
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:
Contact toTOW

Re: Client suddenly stopped being able to connect to get new WU

Post by toTOW »

You should reinstall FAHClient, you probably removed the wrong file. :(
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
Top
Prettz
Posts: 19
Joined: Sat Oct 17, 2009 6:47 pm

Re: Client suddenly stopped being able to connect to get new WU

Post by Prettz »

Just to update, none of this stuff worked, so I just stopped running it.
Top
Joe_H
Site Admin
Posts: 8306
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4
Location: W. MA

Re: Client suddenly stopped being able to connect to get new WU

Post by Joe_H »

Well you were still running the v7 client, could have corrupted the settings or control database files. Did you delete all the data when you uninstalled the client?

In any case your WU requests for the GPU were being diverted to a non-WS address to keep the client from hammering the servers. That is shown here:

Code: Select all

19:03:15:FS01:Unpaused
19:03:16:WU01:FS01:Connecting to 13.59.134.176:8080
19:03:16:WU01:FS01:Assigned to work server 192.0.2.1
19:03:16:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GB205 [GeForce RTX 5070] from 192.0.2.1
19:03:16:WU01:FS01:Connecting to 192.0.2.1:8080
IP address 192.0.2.1 is in a reserved IP block for documentation. It is not a public IP address.

Typically that would be due to either being blacklisted or making a WU request for a non-compatible combination of OS and hardware. For example we used to have folders on macOS systems who figured out how to override the default v7 client settings to not create GPU folding slots, those requests could not be filled. On the server side they used to result in many repeated assignment failures, hence the code added to divert them away from the work servers. You were already asked to confirm your username, that showed no blacklisting. Other WU requests that would get similar handling would be for unrecognized CPUs, or GPU WU requests from ARM based systems.

Fixing things for v7 gets troublesome as many persons who used to have experience with fixing it have long since moved onto v7 clients. I personally have not worked on fixing up a broken setup in years and have forgotten much. If you want to stay with v7 it may take fully uninstalling the client and then completely removing the work and data directory before reinstalling. You may want to keep a copy of the config.xml file to use for copy/pasting of user, team and passkey settings. Otherwise install the current v8.5.5 client and use the copy for the same purpose.
Image
Top
calxalot
Site Moderator
Posts: 1790
Joined: Sat Dec 08, 2007 1:33 am
Location: San Francisco, CA
Contact:
Contact calxalot

Re: Client suddenly stopped being able to connect to get new WU

Post by calxalot »

Would an IP ban only be temporary?
Top
Joe_H
Site Admin
Posts: 8306
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4
Location: W. MA

Re: Client suddenly stopped being able to connect to get new WU

Post by Joe_H »

What is showing in the log is not an IP ban, but the diversion that was coded into the server code to keep bad requests from hammering the work servers. The client was not blocked from getting CPU WU requests fulfilled. Joseph may still have which conditions triggered that documented somewhere. I do know requests from Macs with GPU slots created bypassing normal setup was one of them. The rest I have forgotten in the several years since that was done.
Image
Top
Post Reply

Return to “GPU Projects and FahCores”