Page 1 of 2
No machines on upgrade from v7
Posted: Wed Jan 14, 2026 12:01 pm
by HaloJones
So Windows 11, local client is running, browser screen shows no machines. I do not know where to start to see why this is happening. config.xml is identical to v7 config. the passkey is identical to the same passkey I have used for ever.
If I may say, the web page about v8 is very blase about how simple this all should be.
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 8:04 pm
by calxalot
Is the client in the sys tray?
What browser?
Brave needs shields down.
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 8:07 pm
by calxalot
Does your config.xml alter the allow/deny lists?
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 10:05 pm
by muziqaz
HaloJones wrote: ↑Wed Jan 14, 2026 12:01 pm
So Windows 11, local client is running, browser screen shows no machines. I do not know where to start to see why this is happening. config.xml is identical to v7 config. the passkey is identical to the same passkey I have used for ever.
If I may say, the web page about v8 is very blase about how simple this all should be.
Installation guide for v8 would be your guide to shake off the presumption that v8 is very blase about simplicity
https://foldingathome.org/v8-5-client-guide/
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 11:12 pm
by HaloJones
Code: Select all
<config>
<!-- Folding Core -->
<core-priority v='low'/>
<!-- Folding Slot Configuration -->
<cause v='CANCER'/>
<!-- HTTP Server -->
<allow v='192.168.0.0/24'/>
<!-- Network -->
<proxy v=':8080'/>
<!-- Remote Command Server -->
<password v='redacted'/>
<!-- Slot Control -->
<pause-on-battery v='false'/>
<pause-on-start v='true'/>
<power v='full'/>
<!-- User Information -->
<passkey v='redacted/>
<team v='131'/>
<user v='HaloJones'/>
<!-- Folding Slots -->
<slot id='0' type='GPU'>
<pci-bus v='1'/>
<pci-slot v='0'/>
</slot>
</config>
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 11:29 pm
by HaloJones
calxalot wrote: ↑Wed Jan 14, 2026 8:04 pm
Is the client in the sys tray?
What browser?
Brave needs shields down.
client is in the systray. logs are fine and show it is running normally, any browser - firefox, edge, all the same.
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 11:30 pm
by HaloJones
calxalot wrote: ↑Wed Jan 14, 2026 8:07 pm
Does your config.xml alter the allow/deny lists?
see above, yes, there is an "allow" section.
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 11:39 pm
by calxalot
allow MUST include 127.0.0.1
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 11:42 pm
by calxalot
you didn't need it with v7 because of non-standard behavior to make configuring remote access easier.
v8 follows normal behavior with allow/deny.
Re: No machines on upgrade from v7
Posted: Wed Jan 14, 2026 11:44 pm
by calxalot
I think v7 treated the default deny "0/0" as deny none when a password was set.
Re: No machines on upgrade from v7
Posted: Thu Jan 15, 2026 9:36 am
by HaloJones
I deleted the config.xml and it is now working. An upgrade install should either upgrade existing config files or replace them. Not checking for a suitable configuration seems like a missed opportunity.
Re: No machines on upgrade from v7
Posted: Thu Jan 15, 2026 9:43 am
by calxalot
You are welcome to create an enhancement request re, I guess, validating/updating config.xml on upgrade install or v8 client first run.
https://github.com/FoldingAtHome/fah-cl ... tet/issues
You might want to search existing open and closed issues for a similar issue.
Re: No machines on upgrade from v7
Posted: Thu Jan 15, 2026 9:46 am
by calxalot
Currently, v8 never writes to config.xml.
Re: No machines on upgrade from v7
Posted: Thu Jan 15, 2026 9:49 am
by calxalot
Always adding 127.0.0.1 to internal allow list would probably be a good idea.
Others have had this problem.
Re: No machines on upgrade from v7
Posted: Fri Jan 16, 2026 8:32 pm
by toTOW
The latest beta fixes the issue of config.xml errors preventing the client from starting :
v8.5.6 changedlog wrote:- Failing ``config.xml`` load logs error but is now non-fatal.