Folding@Home In The Dark v8 Web Client: BETA
Super buggy work in progress, lots more features/UI updates coming.
CLIENT INFO: CREATED BY: Folding.LAR.Systems
| User | ||
|---|---|---|
| Team | ||
| Research |
| Anonymous? | |
|---|---|
| Client Settings | |
0 0
0 0
Loading...
| PCIe - gpu-id | Cuda | Open CL | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | Type | Vendor | Device | Support | Device | Platform | Compute | Driver | Compute | Driver | Platform |
Trying to connect to Folding@Home Version 8 Beta Service
Please note this folding.lar.systems web client ONLY WORKS WITH VERSION 8.0 BETA of the Folding@Home web client.
You can download it here if you have not already: https://foldingathome.org/beta/?lng=en
Connecting To Remote Hosts Requires Configuation
On The Folding Machine & Your Browser
To connect to a folding@home service instance that is not running on the same localhost as your browser/webclient you will need to do the following in summary.
Edit the folding@home config.xml on the remote folding machine to allow access on the required interfaces (IP / PORT).
For example add something like this to your "<config>" section to add IP ranges you need, be as restrictive as possible.
<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'/>
There is a good post on the folding forums with examples of the settings you can set / change.
https://foldingforum.org/viewtopic.php?t=39050&sid=df8063710143bbf55257212a9d4abfee
Restart folding@home service on the remote folding machine to allow the service to start with the new configuration. Adjust any Firewall, NAT and other security for accessing the remote machines IP/PORT from the machine you want to run the web client on.
Important: Browser Settings Required To Make This Work
On the machine/browser you are loading this webclient you will need to change the security settings of the browser to allow it to connect to the folding@home websocket connection on the remote machine which does not use SSL as it's usually only accessed on the localhost.
For Chrome Based Browsers:
This change requires going to the "Privacy & Security" settings
and setting
"Insecure Content" = "Allow" for the domain webclient.lar.systems
This can be done by clicking on the lock beside the page URL in many browsers and going to "Site Settings".
For Firefox Based Browsers:
Please try the following:
Open Firefox and type about:config in the address bar.
Accept the risk and proceed.
Search for network.websocket.allowInsecureFromHTTPS.
Set its value to true.
Alternate Approach To Not Change Browser Security Settings
If you are familar with port forwarding from other machines to the local machine you are tyring to access the webclient (using SSH etc.) you can roughly do the following:Use your favorite method or tool of choice to foward the default folding@home port 7396 from the remote folding machine you want to connect to to the localhost of the machine you want to run the webclient on.
In the webclient you then leave the localhost IP address of 127.0.0.1 and make sure the port is 7396, and the forwarding will allow your connect securly from the localhost without changing browser settings.
If you want to connect to multiple machines using this method or also have folding@home running locally on the webclinet machine already using port 7396...
You can use the same approach but when forwarding the port from the folding@home machine to the localhost IP of 127.0.0.1 on your webclient machines you can also change the port to be something other than the default and do this for each folding machine you have allowing you to specifiy the new ports still on the localhost IP in the webclient and access multiple machines.
Connect To A Remote or Non Standard LocalHost Client
Enter an IP and/or port to continue.