Folding Forum

Posted: **Thu Jan 26, 2023 2:58 am**

Hi,

I struggled to get 8.1.11 working and finally got it going this evening. However, now that it is running, I am not getting any WUs. You will note that I have another v7 instance of FAH on my network that has no issues and so I do not think that it is a network configuration problem.

Here is what I see in the app log.

Code: Select all

02:07:41:I1::WU5:Requesting WU assignment
02:07:41:I1:OUT21:> POST https://assign4.foldingathome.org/api/assign HTTP/1.1
02:07:42:I1:OUT21:< assign4.foldingathome.org:443 HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE
02:07:42:E ::WU5:HTTP_SERVICE_UNAVAILABLE: {"error":"No appropriate assignment"}
02:07:42:I1::WU5:Retry #10 in 8 mins 32 secs
02:16:14:I1::WU5:Requesting WU assignment
02:16:14:I1:OUT22:> POST https://assign5.foldingathome.org/api/assign HTTP/1.1
02:16:14:I1:OUT22:< assign5.foldingathome.org:443 HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE
02:16:14:E ::WU5:HTTP_SERVICE_UNAVAILABLE: {"error":"No appropriate assignment"}
02:16:14:I1::WU5:Retry #11 in 8 mins 32 secs
02:24:46:I1::WU5:Requesting WU assignment
02:24:46:I1:OUT23:> POST https://assign6.foldingathome.org/api/assign HTTP/1.1
02:24:47:I1:OUT23:< assign6.foldingathome.org:443 HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE
02:24:47:E ::WU5:HTTP_SERVICE_UNAVAILABLE: {"error":"No appropriate assignment"}
02:24:47:I1::WU5:Retry #12 in 8 mins 32 secs
02:33:19:I1::WU5:Requesting WU assignment
02:33:19:I1:OUT24:> POST https://assign1.foldingathome.org/api/assign HTTP/1.1
02:33:19:I1:OUT24:< assign1.foldingathome.org:443 HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE
02:33:19:E ::WU5:HTTP_SERVICE_UNAVAILABLE: {"error":"No appropriate assignment"}

Here is my config.xml in case that matters:

Code: Select all

<config>
  <cause v='ALZHEIMERS'/>
  <http-addresses v='0.0.0.0:7396'/>
  <allow v='127.0.0.1 10.0.0.0/8 192.168.0.0/16 172.16.0.0/12 169.254.0.0/16'/>
  <deny v='0/0'/>
  <allowed-origins v='https://app.foldingathome.org http://localhost:7396 http://<local IP>:7396'/>
  <web-root v='./fah-web-client-bastet/dist'/>
  <user v='<username>'/>
  <passkey value='<passkey>'/>
  <verbosity v='1'/>
</config>

On suggestions on how to address this?

TIA!

Posted: **Thu Jan 26, 2023 3:06 am**

If the cause dropdown is empty, the Web Control is not able to reach

https://api.foldingathome.org/project/cause

The same problem is probably blocking WU assignments.

Edit: I think these are separate issues.

Posted: **Thu Jan 26, 2023 3:13 am**

The Assignment Servers are the same for v7 and v8.
The services on the server that clients connect to may be different.

Posted: **Thu Jan 26, 2023 3:15 am**

It shouldn't matter, but cause should be lowercase now.

Note that config.xml just has the first-run default for cause (or anything exposed in Web Control).
It can only be changed via Web Control. (or websocket api)

Posted: **Thu Jan 26, 2023 3:20 am**

Okay, thank you. I have two FAH instances one on v7 and the other on 8.1.11 beta. The v7 has no problems reaching the API while 8.1.11 seems to have issues. Any suggestions on how to troubleshoot this? Could this be a beta issue?

I will fix "cause" to see if it makes a difference, but it is interesting that it is not populating in the Web GUI.

Posted: **Thu Jan 26, 2023 3:27 am**

I believe v7 only connects on ports 80, 8080.
V8 needs common https ports open.

Check you firewalls and proxies.
Actually, I think v8 doesn't support proxies yet.

Posted: **Thu Jan 26, 2023 3:33 am**

I am not sure I understand. When you say open ports, are you suggesting that I forward port 443 to the v8 FAH host? Port 443 is already forwarded to a different host for https access and so that requirement would be problematic for me. The above said, I have no outgoing port limitations like a proxy would create. I am wondering if this is a beta issue issue?

Posted: **Thu Jan 26, 2023 3:54 am**

I am no expert.

I just mean both your machine and the server running fah-client need to be able to reach all the F@H servers via https.

Some firewalls will only allow known browsers to connect.
If so, your firewall may need to specifically allow fah-client to make connections.

I am 100% sure Web Control causes popup is empty because Web Control, running in your browser, cannot reach

https://api.foldingathome.org/project/cause

Try it directly yourself, with the browser javascript console open and verbose.

Posted: **Thu Jan 26, 2023 4:01 am**

Port 443 is already forwarded to a different host for https access

That sounds proxy-like to me.

Posted: **Thu Jan 26, 2023 4:11 am**

The differences between v7 and v8 that I see are the following:

v7 has FAHClient, v8 has fah-client

v7 uses ports 80 and 8080 and HTTP, v8 is using port 443 and HTTPS

I do not see the v8 client trying on any alternate HTTPS port. But any setups to pass v7 requests to the servers will need updating to work with v8.

Posted: **Thu Jan 26, 2023 4:25 am**

Looking at cbang source, I think the client makes http(s) connections with

Code: Select all

User-Agent: cbang.org

So it doesn't try to spoof as any known browser.

Whatever firewall is used needs to not block that User-Agent.

Posted: **Thu Jan 26, 2023 4:30 am**

But the issue with causes not populating in Web Control has nothing to do with the client.

Posted: **Thu Jan 26, 2023 8:05 am**

It seems the causes popup is not populating because of an allowed-origins policy on api.foldingathome.org.
I believe it only allows origins api.foldingathome.org, app.foldingathome.org, 127.0.0.1, localhost.

For a local hosted Web Control to be fully functional, it needs to vended by a fah-client on localhost.
This client does not need to be folding.
You would add the hosts you want to control to its peers list.

But this shouldn't have anything to do with not getting WUs.
Separate problem.

Posted: **Thu Jan 26, 2023 8:13 am**

Error looks like

Code: Select all

Access to fetch at 'https://api.foldingathome.org/project/cause' from origin 'http://sanctuary:7396' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I'm not sure what I'm reading, but it seems like something Web Control could fix by adding headers.

Edit: I seem to be ignorant here
CORS is Cross-Origin Resource Sharing
There are hacks to disable this security in various web browsers, but that's not a good solution.
Best to just use https://app.foldingathome.org
Or, if you must, a localhost web control

Posted: **Thu Jan 26, 2023 9:55 am**

Could you please post the first 200 lines of your log.txt?
Verbosity 3 would be good.

Folding Forum

Not getting WUs in 8.1.11 Beta

Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta

Re: Not getting WUs in 8.1.11 Beta