Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

FAH-Client 8 not working on Ubuntu Server

https://foldingforum.org/viewtopic.php?t=41784

Page 1 of 2

FAH-Client 8 not working on Ubuntu Server

Posted: Fri Aug 02, 2024 3:54 am
by DoctorBob
I am having issues getting fah-client 8.3.18 working with our headless Ubuntu Server (24.04 LTS x86_64).
I access the server over our local area network via ssh.

I have disabled ufw while troubleshooting this issue.

Here is the installation procedure:
* sudo apt update && sudo apt upgrade -y
* sudo apt install ocl-icd-opencl-dev


CUDA Installation: https://developer.nvidia.com/cuda-downl ... ion=Ubuntu target_version=20.04&target_type=deb_network

* wget https://developer.download.nvidia.com/c ... -1_all.deb
* sudo dpkg -i cuda-keyring_1.1-1_all.deb
* sudo apt-get update
* sudo apt-get -y install cuda-toolkit-12-6


Fah-client 8 installation:
* wget https://download.foldingathome.org/rele ... _amd64.deb
* sudo apt install fah-client_8.3.18_amd64.deb

Installation output:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'fah-client' instead of '/home/robert/downloads/folding@home/fah-client_8.3.18_amd64.deb'
The following NEW packages will be installed:
fah-client
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/2,993 kB of archives.
After this operation, 8,119 kB of additional disk space will be used.
Get:1 /home/robert/downloads/folding@home/fah-client_8.3.18_amd64.deb fah-client amd64 8.3.18 [2,993 kB]
Selecting previously unselected package fah-client.
(Reading database ... 184916 files and directories currently installed.)
Preparing to unpack .../fah-client_8.3.18_amd64.deb ...
Unpacking fah-client (8.3.18) ...
Setting up fah-client (8.3.18) ...

The Folding@home client is now installed

File locations:

Logs: /var/log/fah-client
Data: /var/lib/fah-client

Service commands:

systemctl status --no-pager -l fah-client
sudo systemctl start fah-client
sudo systemctl stop fah-client
sudo systemctl restart fah-client

Access the web interface by going to:

https://v8-3.foldingathome.org/

Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

Restarting services...

Service restarts being deferred:
systemctl restart NetworkManager.service
systemctl restart systemd-logind.service
systemctl restart wpa_supplicant.service

No containers need to be restarted.

User sessions running outdated binaries:
robert @ session #479: sshd[11668]
robert @ user manager service: systemd[11678]

No VM guests are running outdated hypervisor (qemu) binaries on this host.
N: Download is performed unsandboxed as root as file '/home/robert/downloads/folding@home/fah-client_8.3.18_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)



Log file after installation:


*********************** Log Started 2024-08-02T02:56:30Z ***********************
02:56:30:I1:*********************** Folding@home Client ***********************
02:56:30:I1: Version: 8.3.18
02:56:30:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
02:56:30:I1: Org: foldingathome.org
02:56:30:I1: Copyright: 2023-2024, foldingathome.org
02:56:30:I1: Homepage: https://foldingathome.org/
02:56:30:I1: License: GPL-3.0-or-later
02:56:30:I1: URL: https://v8-3.foldingathome.org/
02:56:30:I1: Date: Jul 12 2024
02:56:30:I1: Time: 13:26:31
02:56:30:I1: Revision: 99ae953ee7b1c0b3070161cfcf9150184f76bd96
02:56:30:I1: Branch: master
02:56:30:I1: Compiler: GNU 8.3.0
02:56:30:I1: Options: -Wsuggest-override -faligned-new -std=c++17 -fsigned-char
02:56:30:I1: -ffunction-sections -fdata-sections -O3 -funroll-loops -fno-pie
02:56:30:I1: Platform: linux 4.19.0-26-cloud-amd64
02:56:30:I1: Bits: 64
02:56:30:I1: Mode: Release
02:56:30:I1: Args: --config=/etc/fah-client/config.xml
02:56:30:I1: --log=/var/log/fah-client/log.txt
02:56:30:I1: --log-rotate-dir=/var/log/fah-client/
02:56:30:I1: Config: /etc/fah-client/config.xml
02:56:30:I1:****************************** CBang ******************************
02:56:30:I1: Version: 1.7.2
02:56:30:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
02:56:30:I1: Org: Cauldron Development
02:56:30:I1: Copyright: Cauldron Development, 2003-2024
02:56:30:I1: Homepage: https://cauldrondevelopment.com/
02:56:30:I1: License: LGPL-2.1-or-later
02:56:30:I1: Date: Jun 24 2024
02:56:30:I1: Time: 13:29:44
02:56:30:I1: Revision: 1b05ea96f0ed3043c32b78a66dbf50a9b2002289
02:56:30:I1: Branch: master
02:56:30:I1: Compiler: GNU 8.3.0
02:56:30:I1: Options: -Wsuggest-override -faligned-new -std=c++17 -fsigned-char
02:56:30:I1: -ffunction-sections -fdata-sections -O3 -funroll-loops -fno-pie
02:56:30:I1: -fPIC
02:56:30:I1: Platform: linux 4.19.0-26-cloud-amd64
02:56:30:I1: Bits: 64
02:56:30:I1: Mode: Release
02:56:30:I1:***************************** System ******************************
02:56:30:I1: CPU: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
02:56:30:I1: CPU ID: GenuineIntel Family 6 Model 23 Stepping 6
02:56:30:I1: CPUs: 2
02:56:30:I1: Memory: 1.91GiB
02:56:30:I1:Free Memory: 283.30MiB
02:56:30:I1: OS Version: 6.8
02:56:30:I1:Has Battery: false
02:56:30:I1: On Battery: false
02:56:30:I1: Hostname: folding-laptop
02:56:30:I1: UTC Offset: 10
02:56:30:I1: PID: 43942
02:56:30:I1: CWD: /var/lib/fah-client
02:56:30:I1: Exec: /usr/bin/fah-client
02:56:30:I1:*******************************************************************
02:56:30:I2:<config/>
02:56:30:I1:Opening Database
02:56:30:I1:F@H ID = 8HIHNQrqeevL1SJYTwhQ3YOIuRcc7QeRf1Nk8pxCBE4
02:56:30:I3:Loading default group
02:56:30:I3:Loading default resource group
02:56:30:I1:Listening for HTTP on 127.0.0.1:7396
02:56:30:I3:Loaded 0 wus.
^[[93m02:56:30:W :OpenCL not supported: clGetPlatformIDs() returned -1001^[[0m
^[[93m02:56:30:W :CUDA not supported: cuInit() returned 100^[[0m
03:21:52:I1:OUT1:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:21:53:I1:OUT1:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:21:53:E :OUT1:HTTP_BAD_REQUEST: ^[[0m
03:22:09:I1:OUT2:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:22:10:I1:OUT2:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:22:10:E :OUT2:HTTP_BAD_REQUEST: ^[[0m
03:22:32:I1:OUT3:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:22:34:I1:OUT3:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:22:34:E :OUT3:HTTP_BAD_REQUEST: ^[[0m
03:23:07:I1:OUT4:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:23:09:I1:OUT4:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:23:09:E :OUT4:HTTP_BAD_REQUEST: ^[[0m
03:23:59:I1:OUT5:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:24:00:I1:OUT5:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:24:00:E :OUT5:HTTP_BAD_REQUEST: ^[[0m
03:25:16:I1:OUT6:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:25:17:I1:OUT6:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:25:17:E :OUT6:HTTP_BAD_REQUEST: ^[[0m
03:27:10:I1:OUT7:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:27:12:I1:OUT7:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:27:12:E :OUT7:HTTP_BAD_REQUEST: ^[[0m
03:30:02:I1:OUT8:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:30:03:I1:OUT8:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:30:03:E :OUT8:HTTP_BAD_REQUEST: ^[[0m
03:34:04:I1:OUT9:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:34:05:I1:OUT9:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:34:05:E :OUT9:HTTP_BAD_REQUEST: ^[[0m
03:38:05:I1:OUT10:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:38:07:I1:OUT10:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:38:07:E :OUT10:HTTP_BAD_REQUEST: ^[[0m
03:42:07:I1:OUT11:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:42:08:I1:OUT11:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:42:08:E :OUT11:HTTP_BAD_REQUEST: ^[[0m
03:46:09:I1:OUT12:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:46:10:I1:OUT12:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m03:46:10:E :OUT12:HTTP_BAD_REQUEST: ^[[0m
03:50:11:I1:OUT13:> PUT https://api.foldingathome.org/machine/8 ... 1Nk8pxCBE4 HTTP/1.1
03:50:12:I1:OUT13:< HTTP/1.1 400 HTTP_BAD_REQUEST


It was not necessary to install CUDA as this laptop's nVidia device does not support it.


Fah-client service is running:
* sudo service fah-client status

● fah-client.service - Folding@home Client
Loaded: loaded (/usr/lib/systemd/system/fah-client.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-08-02 13:21:51 AEST; 9min ago
Main PID: 44196 (fah-client)
Tasks: 3 (limit: 2265)
Memory: 9.4M (peak: 10.3M)
CPU: 1.098s
CGroup: /system.slice/fah-client.service
└─44196 /usr/bin/fah-client --config=/etc/fah-client/config.xml --log=/var/log/fah-client/log.txt --log-rotate-dir=/var/log/fah-client/

Aug 02 13:21:51 folding-laptop systemd[1]: Started fah-client.service - Folding@home Client.


Even though the fah-client service is running the laptop is not folding. The CPU is idling.

I then created a account at: https://v8-3.foldingathome.org/machines (from another PC on our network).
Once the account was created and I logged in I see under the Machines tab:
No folding machines found.
Login or install the Folding@home client software.
If you are using Brave browser, please use "Shields Down" for this site.

Here is the html source for the above page:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8"/>
<link rel="icon" href="/favicon.ico"/>
<link rel="stylesheet" href="/css/font-awesome.min.css">
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<title>Folding@home Client</title>
<script type="module" crossorigin src="/assets/index-e66b4b71.js"></script>
<link rel="stylesheet" href="/assets/index-b63d00fc.css">
</head>
<body>
<div id="app"></div>

</body>
</html>



However, the Stats tab does show my status details so I know I am correctly logged in.

The fah-client configuration file: /etc/fah-client/config.xml:
</config>

Not sure what to add to the config.xml file and in what format.
I did try to update the config.xml file like this (account-token masked here):
<config>
<account-token v="##########################################"/>
<machine-name v="Folding Laptop"/>
</config>


I restarted the fah-client service but the Machines tab did not change, the laptop is not folding.

I also tried to log into https://beta.foldingathome.org/machines, https://v8-3.foldingathome.org/account and http://127.0.0.1:7396 using elinks and lynx on the Ubuntu server but it just produces a blank page.
Not sure if this was necessary, on our Internet router I port forwarded 7396 to the fah-client laptop.

So at this point in time, I am stuck.
How do I get fah-client folding and the web interface to show the machine?

PS. Now I get a "Getting project causes failedAPI error: TypeError: NetworkError when attempting to fetch resource." error when I try to login at: https://beta.foldingathome.org/machines
(03/08/2024) I can now login again. Not sure why the above was happening.

Bug filled fun!

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Fri Aug 02, 2024 5:39 am
by calxalot
Can you ping api.foldingathome.org from your server?

Maybe try installing the debug build?
The debug log might show more info.

https://download.foldingathome.org/rele ... _amd64.deb

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Fri Aug 02, 2024 5:40 am
by DoctorBob
Can you ping api.foldingathome.org from your server?
Yes, both from my PC and the Ubuntu server laptop:
* ping api.foldingathome.org
PING api.foldingathome.org (3.136.33.72) 56(84) bytes of data.
64 bytes from mail.foldingathome.org (3.136.33.72): icmp_seq=1 ttl=52 time=229 ms
64 bytes from mail.foldingathome.org (3.136.33.72): icmp_seq=2 ttl=52 time=229 ms
64 bytes from mail.foldingathome.org (3.136.33.72): icmp_seq=3 ttl=52 time=229 ms

--- api.foldingathome.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 228.946/229.018/229.132/0.081 ms

I will try the debug version. Thank you for that...


I removed fah-client and installed fah-client (debug)

* sudo apt install /home/robert/downloads/folding@home/'fah-client_8.3.18_amd64 (Debug).deb'

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'fah-client' instead of '/home/robert/downloads/folding@home/fah-client_8.3.18_amd64 (Debug).deb'
The following NEW packages will be installed:
fah-client
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/16.6 MB of archives.
After this operation, 79.6 MB of additional disk space will be used.
Get:1 /home/robert/downloads/folding@home/fah-client_8.3.18_amd64 (Debug).deb fah-client amd64 8.3.18 [16.6 MB]
Selecting previously unselected package fah-client.
(Reading database ... 184916 files and directories currently installed.)
Preparing to unpack .../fah-client_8.3.18_amd64 (Debug).deb ...
Unpacking fah-client (8.3.18) ...
Setting up fah-client (8.3.18) ...

The Folding@home client is now installed

File locations:

Logs: /var/log/fah-client
Data: /var/lib/fah-client

Service commands:

systemctl status --no-pager -l fah-client
sudo systemctl start fah-client
sudo systemctl stop fah-client
sudo systemctl restart fah-client

Access the web interface by going to:

https://v8-3.foldingathome.org/

Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
N: Download is performed unsandboxed as root as file '/home/robert/downloads/folding@home/fah-client_8.3.18_amd64 (Debug).deb' couldn't be accessed by use r '_apt'. - pkgAcquire::Run (13: Permission denied)


Fah-client service status:
sudo service fah-client status
● fah-client.service - Folding@home Client
Loaded: loaded (/usr/lib/systemd/system/fah-client.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-08-02 15:56:06 AEST; 50s ago
Main PID: 4124 (fah-client)
Tasks: 2 (limit: 2265)
Memory: 14.7M (peak: 15.2M)
CPU: 2.767s
CGroup: /system.slice/fah-client.service
└─4124 /usr/bin/fah-client --config=/etc/fah-client/config.xml --log=/var/log/fah-client/log.txt --log-rotate-dir=/var/log/fah-client/

Aug 02 15:56:06 folding-laptop systemd[1]: Started fah-client.service - Folding@home Client.



Logfile:

*********************** Log Started 2024-08-02T05:56:06Z ***********************
05:56:06:I1:*********************** Folding@home Client ***********************
05:56:06:I1: Version: 8.3.18
05:56:06:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
05:56:06:I1: Org: foldingathome.org
05:56:06:I1: Copyright: 2023-2024, foldingathome.org
05:56:06:I1: Homepage: https://foldingathome.org/
05:56:06:I1: License: GPL-3.0-or-later
05:56:06:I1: URL: https://v8-3.foldingathome.org/
05:56:06:I1: Date: Jul 12 2024
05:56:06:I1: Time: 13:26:39
05:56:06:I1: Revision: 99ae953ee7b1c0b3070161cfcf9150184f76bd96
05:56:06:I1: Branch: master
05:56:06:I1: Compiler: GNU 8.3.0
05:56:06:I1: Options: -Wsuggest-override -faligned-new -std=c++17 -fsigned-char -g -Wall
05:56:06:I1: -Werror -fno-pie
05:56:06:I1: Platform: linux 4.19.0-26-cloud-amd64
05:56:06:I1: Bits: 64
05:56:06:I1: Mode: Debug
05:56:06:I1: Args: --config=/etc/fah-client/config.xml
05:56:06:I1: --log=/var/log/fah-client/log.txt
05:56:06:I1: --log-rotate-dir=/var/log/fah-client/
05:56:06:I1: Config: /etc/fah-client/config.xml
05:56:06:I1:****************************** CBang ******************************
05:56:06:I1: Version: 1.7.2
05:56:06:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
05:56:06:I1: Org: Cauldron Development
05:56:06:I1: Copyright: Cauldron Development, 2003-2024
05:56:06:I1: Homepage: https://cauldrondevelopment.com/
05:56:06:I1: License: LGPL-2.1-or-later
05:56:06:I1: Date: Jun 24 2024
05:56:06:I1: Time: 13:29:43
05:56:06:I1: Revision: 1b05ea96f0ed3043c32b78a66dbf50a9b2002289
05:56:06:I1: Branch: master
05:56:06:I1: Compiler: GNU 8.3.0
05:56:06:I1: Options: -Wsuggest-override -faligned-new -std=c++17 -fsigned-char -g -Wall
05:56:06:I1: -Werror -fno-pie -fPIC
05:56:06:I1: Platform: linux 4.19.0-26-cloud-amd64
05:56:06:I1: Bits: 64
05:56:06:I1: Mode: Debug
05:56:06:I1:***************************** System ******************************
05:56:06:I1: CPU: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
05:56:06:I1: CPU ID: GenuineIntel Family 6 Model 23 Stepping 6
05:56:06:I1: CPUs: 2
05:56:06:I1: Memory: 1.91GiB
05:56:06:I1:Free Memory: 756.37MiB
05:56:06:I1: OS Version: 6.8
05:56:06:I1:Has Battery: false
05:56:06:I1: On Battery: false
05:56:06:I1: Hostname: folding-laptop
05:56:06:I1: UTC Offset: 10
05:56:06:I1: PID: 4124
05:56:06:I1: CWD: /var/lib/fah-client
05:56:06:I1: Exec: /usr/bin/fah-client
05:56:06:I1:*******************************************************************
05:56:06:I2:<config/>
05:56:06:I1:Opening Database
05:56:06:I1:Generating RSA key....++++-.............................................................................................................................................................................................................++++-
05:56:09:I1:F@H ID = _ffmj42qvi9EVTRTfGfy7DF6RwPKM3_K-lRsX7xzqeY
05:56:09:I3:Loading default group
05:56:09:I3:Loading default resource group
05:56:09:I1:Listening for HTTP on 127.0.0.1:7396
05:56:09:I3:Loaded 0 wus.
05:56:09:I1:OUT1:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m05:56:09:D3:CON1:Failed to write request^[[0m
^[[93m05:56:09:W :Failed to update GPUs^[[0m
05:56:14:I1:OUT2:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m05:56:14:D3:CON2:Failed to write request^[[0m
^[[93m05:56:14:W :Failed to update GPUs^[[0m
05:56:25:I1:OUT3:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m05:56:25:D3:CON3:Failed to write request^[[0m
^[[93m05:56:25:W :Failed to update GPUs^[[0m
05:56:47:I1:OUT4:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m05:56:47:D3:CON4:Failed to write request^[[0m
^[[93m05:56:47:W :Failed to update GPUs^[[0m
05:57:32:I1:OUT5:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m05:57:32:D3:CON5:Failed to write request^[[0m
^[[93m05:57:32:W :Failed to update GPUs^[[0m
05:59:02:I1:OUT6:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m05:59:02:D3:CON6:Failed to write request^[[0m
^[[93m05:59:02:W :Failed to update GPUs^[[0m
06:02:02:I1:OUT7:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m06:02:02:D3:CON7:Failed to write request^[[0m
^[[93m06:02:02:W :Failed to update GPUs^[[0m
06:08:03:I1:OUT8:> GET https://api.foldingathome.org/gpus HTTP/1.1
^[[92m06:08:03:D3:CON8:Failed to write request^[[0m
^[[93m06:08:03:W :Failed to update GPUs^[[0m

I still cannot log into https://beta.foldingathome.org/machines
Fah-client is not folding on server.
(03/08/2024) I changed to: https://v8-3.foldingathome.org/machines I can now log into my account.

PS. I confused myself. When I orginally installed fah-client 8, the last line of the logfile showed:
^[[93m08:11:57:W :CUDA not supported: Failed to open dynamic library 'libcuda.so': libcuda.so: cannot open shared object file: No such file or directory^[[0m

Our previous laptop did have a nVidia device. Our current replacement laptop does not. I should not have installed the CUDA Toolkit. Anyhow I have completely removed the CUDA Toolkit and restarted the laptop.

Updated logfile:

*********************** Log Started 2024-08-02T08:11:56Z ***********************
08:11:56:I1:*********************** Folding@home Client ***********************
08:11:56:I1: Version: 8.3.18
08:11:56:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
08:11:56:I1: Org: foldingathome.org
08:11:56:I1: Copyright: 2023-2024, foldingathome.org
08:11:56:I1: Homepage: https://foldingathome.org/
08:11:56:I1: License: GPL-3.0-or-later
08:11:56:I1: URL: https://v8-3.foldingathome.org/
08:11:56:I1: Date: Jul 12 2024
08:11:56:I1: Time: 13:26:39
08:11:56:I1: Revision: 99ae953ee7b1c0b3070161cfcf9150184f76bd96
08:11:56:I1: Branch: master
08:11:56:I1: Compiler: GNU 8.3.0
08:11:56:I1: Options: -Wsuggest-override -faligned-new -std=c++17 -fsigned-char -g -Wall
08:11:56:I1: -Werror -fno-pie
08:11:56:I1: Platform: linux 4.19.0-26-cloud-amd64
08:11:56:I1: Bits: 64
08:11:56:I1: Mode: Debug
08:11:56:I1: Args: --config=/etc/fah-client/config.xml
08:11:56:I1: --log=/var/log/fah-client/log.txt
08:11:56:I1: --log-rotate-dir=/var/log/fah-client/
08:11:56:I1: Config: /etc/fah-client/config.xml
08:11:56:I1:****************************** CBang ******************************
08:11:56:I1: Version: 1.7.2
08:11:56:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
08:11:56:I1: Org: Cauldron Development
08:11:56:I1: Copyright: Cauldron Development, 2003-2024
08:11:56:I1: Homepage: https://cauldrondevelopment.com/
08:11:56:I1: License: LGPL-2.1-or-later
08:11:56:I1: Date: Jun 24 2024
08:11:56:I1: Time: 13:29:43
08:11:56:I1: Revision: 1b05ea96f0ed3043c32b78a66dbf50a9b2002289
08:11:56:I1: Branch: master
08:11:56:I1: Compiler: GNU 8.3.0
08:11:56:I1: Options: -Wsuggest-override -faligned-new -std=c++17 -fsigned-char -g -Wall
08:11:56:I1: -Werror -fno-pie -fPIC
08:11:56:I1: Platform: linux 4.19.0-26-cloud-amd64
08:11:56:I1: Bits: 64
08:11:56:I1: Mode: Debug
08:11:56:I1:***************************** System ******************************
08:11:56:I1: CPU: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
08:11:56:I1: CPU ID: GenuineIntel Family 6 Model 23 Stepping 6
08:11:56:I1: CPUs: 2
08:11:56:I1: Memory: 1.91GiB
08:11:56:I1:Free Memory: 1.50GiB
08:11:56:I1: OS Version: 6.8
08:11:56:I1:Has Battery: false
08:11:56:I1: On Battery: false
08:11:56:I1: Hostname: folding-laptop
08:11:56:I1: UTC Offset: 10
08:11:56:I1: PID: 943
08:11:56:I1: CWD: /var/lib/fah-client
08:11:56:I1: Exec: /usr/bin/fah-client
08:11:56:I1:*******************************************************************
08:11:56:I2:<config/>
08:11:56:I1:Opening Database
08:11:56:I1:F@H ID = _ffmj42qvi9EVTRTfGfy7DF6RwPKM3_K-lRsX7xzqeY
08:11:56:I3:Loading default group
08:11:56:I3:Loading default resource group
08:11:56:I1:Listening for HTTP on 127.0.0.1:7396
08:11:56:I3:Loaded 0 wus.
^[[93m08:11:57:W :OpenCL not supported: clGetPlatformIDs() returned -1001^[[0m
^[[93m08:11:57:W :CUDA not supported: Failed to open dynamic library 'libcuda.so': libcuda.so: cannot open shared object file: No such file or directory^[[0m

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sat Aug 03, 2024 1:56 am
by DoctorBob
calxalot wrote: ↑Fri Aug 02, 2024 5:39 am Maybe try installing the debug build?
The debug log might show more info.
Is the bug log different from /var/log/fah-client/log.txt?
Is it located somewhere else?

I added --log-debug=true to fah-client and restarted the service.

This is the additional information I see at the end of the logfile:
02:03:00:I1:OUT1:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:03:00:D3:CON1:Failed to write request^[[0m
^[[91m02:03:00:E :OUT1:Failed response: EOF^[[0m
02:03:15:I1:OUT2:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:03:16:D3:CON2:Failed to write request^[[0m
^[[91m02:03:16:E :OUT2:Failed response: EOF^[[0m
02:03:38:I1:OUT3:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:03:38:D3:CON3:Failed to write request^[[0m
^[[91m02:03:38:E :OUT3:Failed response: EOF^[[0m
02:04:11:I1:OUT4:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:04:11:D3:CON4:Failed to write request^[[0m
^[[91m02:04:11:E :OUT4:Failed response: EOF^[[0m
02:05:02:I1:OUT5:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:05:02:D3:CON5:Failed to write request^[[0m
^[[91m02:05:02:E :OUT5:Failed response: EOF^[[0m
02:06:17:I1:OUT6:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:06:17:D3:CON6:Failed to write request^[[0m
^[[91m02:06:17:E :OUT6:Failed response: EOF^[[0m
02:17:37:I1:REQ7:< GET / HTTP/1.1
02:17:37:I1:REQ7:> HTTP/1.1 307 HTTP_TEMPORARY_REDIRECT
02:18:57:I1:OUT8:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:18:57:D3:CON8:Failed to write request^[[0m
^[[91m02:18:57:E :OUT8:Failed response: EOF^[[0m
02:21:47:I1:OUT9:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:21:48:D3:CON9:Failed to write request^[[0m
^[[91m02:21:48:E :OUT9:Failed response: EOF^[[0m

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sat Aug 03, 2024 3:12 am
by calxalot
Seems that, somehow, the service client running as user "fah-client" is not able to connect to the api server.

Is it running in a VM or container?

Do you use an http proxy?

Is IPv4 enabled?

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sat Aug 03, 2024 4:02 am
by DoctorBob
calxalot wrote: ↑Sat Aug 03, 2024 3:12 am Seems that, somehow, the service client running as user "fah-client" is not able to connect to the api server.

Is it running in a VM or container?

Do you use an http proxy?

Is IPv4 enabled?
No VMs or containers running on the laptop. Fah-client is running on bare metal.
No http proxy running on the laptop or on our network.

Yes, network device on the laptop is configured for IPv4:
* ifconfig
enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.5.11 netmask 255.255.255.0 broadcast 192.168.5.255
inet6 fe80::21e:68ff:fe5f:84bd prefixlen 64 scopeid 0x20<link>
ether 00:1e:68:5f:84:bd txqueuelen 1000 (Ethernet)
RX packets 80114 bytes 28287332 (28.2 MB)
RX errors 0 dropped 4 overruns 0 frame 0
TX packets 18275 bytes 217241347 (217.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 438 bytes 40281 (40.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 438 bytes 40281 (40.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


I have also disabled ufw while troubleshooting this issue.

The logfile is showing these entries near the end of the file:
^[[91m04:14:12:E :OUT37:HTTP_BAD_REQUEST: ^[[0m
04:18:13:I1:OUT38:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
04:18:14:I1:OUT38:< HTTP/1.1 400 HTTP_BAD_REQUEST

Opening link: https://api.foldingathome.org/machine/_ ... lRsX7xzqeY in Firefox:
JSON
error "Machine not found"
status 404

Headers
Access-Control-Allow-Credentials true
Access-Control-Allow-Headers DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range,Set-Cookie,Authorization
Access-Control-Allow-Methods POST,PUT,GET,OPTIONS,DELETE
Cache-Control max-age=0
Connection keep-alive
Content-Type application/json
Date Sat, 03 Aug 2024 04:59:02 GMT
Server nginx/1.18.0
Transfer-Encoding chunked
Vary Origin
Accept text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
Accept-Encoding gzip, deflate, br
Accept-Language en-US,en;q=0.5
Connection keep-alive
Host api.foldingathome.org
Referer https://foldingforum.org/
Sec-Fetch-Dest document
Sec-Fetch-Mode navigate
Sec-Fetch-Site cross-site
Sec-Fetch-User ?1
Sec-GPC 1
Upgrade-Insecure-Requests 1
User-Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0


user "fah-client"
My username from version 7 is: doctorbob
My Client login for version 8 is: *************@hotmail.com

Do I need to change user "fah-client" to either "doctorbob" or "***********@hotmail.com" and, if so, how?

At webpage: https://v8-3.foldingathome.org/account my username is: doctorbob
Team: 0
Cause: any
Node: node1.foldingathome.org

* ping node1.foldingathome.org
PING node1.foldingathome.org (3.130.125.139) 56(84) bytes of data.
64 bytes from ec2-3-130-125-139.us-east-2.compute.amazonaws.com (3.130.125.139): icmp_seq=1 ttl=250 time=230 ms
64 bytes from ec2-3-130-125-139.us-east-2.compute.amazonaws.com (3.130.125.139): icmp_seq=2 ttl=250 time=230 ms
64 bytes from ec2-3-130-125-139.us-east-2.compute.amazonaws.com (3.130.125.139): icmp_seq=3 ttl=250 time=229 ms

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 12:51 am
by calxalot
The Linux installer will create an unprivileged user and team named "fah-client" on your computer.
The service client runs as this user and group for improved security.

This has nothing to do with your user name in fah account or on this forum, or your personal account on your computer.

You should redact your emails, unless you like spam.

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 12:54 am
by calxalot

Code: Select all

error "Machine not found"
might be normal if the client has never been linked to an account.

Do you still see this?

Code: Select all

02:06:17:I1:OUT6:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:06:17:D3:CON6:Failed to write request^[[0m
^[[91m02:06:17:E :OUT6:Failed response: EOF^[[0m

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 1:01 am
by calxalot
You might try

1. stop the client
sudo systemctl stop fah-client

2. add your account-token to /etc/fah-client/config.xml
sudo nano /etc/fah-client/config.xml

3. delete /var/lib/fah-client/client.db (this will make it like a first run)
sudo rm /var/lib/fah-client/client.db

4. start client
sudo systemctl start fah-client

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 4:48 am
by DoctorBob
You should redact your emails, unless you like spam.
Can I log into https://v8-3.foldingathome.org/machines using my username instead of my email address?
Not sure how to go about doing a redact of one's email address.


Do you still see this?

Code: Select all

02:06:17:I1:OUT6:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:06:17:D3:CON6:Failed to write request^[[0m
^[[91m02:06:17:E :OUT6:Failed response: EOF^[[0m
This is what I am currently seeing in the /var/log/fah-client/log.txt logfile:
04:17:03:I1:OUT325:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
04:17:04:I1:OUT325:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m04:17:04:E :OUT325:HTTP_BAD_REQUEST: ^[[0m

I no longer see:
02:06:17:I1:OUT6:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:06:17:D3:CON6:Failed to write request^[[0m
^[[91m02:06:17:E :OUT6:Failed response: EOF^[[0m



You might try
1. stop the client
* sudo systemctl stop fah-client (stopped successfully)

2. add your account-token to /etc/fah-client/config.xml
* sudo vi /etc/fah-client/config.xml
added (token masked here):
<config>
<account-token v="#######################################"/>
<machine-name v="Folding Laptop"/>
</config>

3. delete /var/lib/fah-client/client.db (this will make it like a first run)
* sudo rm /var/lib/fah-client/client.db (file deleted)

4. start client
* sudo systemctl start fah-client (started successfully)

I then logged into my account at https://v8-3.foldingathome.org/machines
Machine tab:
No folding machines found.
Login or install the Folding@home client software.
If you are using Brave browser, please use "Shields Down" for this site.

Here is a directory listing of the newly created client.db file:
* dir /var/lib/fah-client/
total 248K
-rw-r--r-- 1 fah-client fah-client 28K Aug 4 14:22 client.db
-rw-r--r-- 1 fah-client fah-client 219K Aug 2 17:28 gpus.json



Still no joy!

PS. I have also turned off ublock Origin and DuckDuckGo protection in Firefox for https://v8-3.foldingathome.org/machines

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 5:33 am
by calxalot
DoctorBob wrote: ↑Sun Aug 04, 2024 4:48 am
You should redact your emails, unless you like spam.
Can I log into https://v8-3.foldingathome.org/machines using my username instead of my email address?
Not sure how to go about doing a redact of one's email address.
No, you cannot.
I was simply saying you should remove it from posts in this thread.
Do you still see this?

02:06:17:I1:OUT6:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:06:17:D3:CON6:Failed to write request^[[0m
^[[91m02:06:17:E :OUT6:Failed response: EOF^[[0m
This is what I am currently seeing in the /var/log/fah-client/log.txt logfile:
04:17:03:I1:OUT325:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
04:17:04:I1:OUT325:< HTTP/1.1 400 HTTP_BAD_REQUEST
^[[91m04:17:04:E :OUT325:HTTP_BAD_REQUEST: ^[[0m

I no longer see:
02:06:17:I1:OUT6:> PUT https://api.foldingathome.org/machine/_ ... lRsX7xzqeY HTTP/1.1
^[[92m02:06:17:D3:CON6:Failed to write request^[[0m
^[[91m02:06:17:E :OUT6:Failed response: EOF^[[0m
That's good.
Actually, no good if you are seeing bad request still after setting account-token.
Does account-token appear in the client log near startup?
1. stop the client
* sudo systemctl stop fah-client (stopped successfully)

2. add your account-token to /etc/fah-client/config.xml
* sudo vi /etc/fah-client/config.xml
added (token masked here):
<config>
<account-token v="#######################################"/>
<machine-name v="Folding Laptop"/>
</config>

3. delete /var/lib/fah-client/client.db (this will make it like a first run)
* sudo rm /var/lib/fah-client/client.db (file deleted)

4. start client
* sudo systemctl start fah-client (started successfully)

I then logged into my account at https://v8-3.foldingathome.org/machines
Machine tab:
No folding machines found.
Login or install the Folding@home client software.
If you are using Brave browser, please use "Shields Down" for this site.

Here is a directory listing of the newly created client.db file:
* dir /var/lib/fah-client/
total 248K
-rw-r--r-- 1 fah-client fah-client 28K Aug 4 14:22 client.db
-rw-r--r-- 1 fah-client fah-client 219K Aug 2 17:28 gpus.json



Still no joy!

PS. I have also turned off ublock Origin and DuckDuckGo protection in Firefox for https://v8-3.foldingathome.org/machines
Did you then login to your account in Web Control?
If you see the message to login, I don't think you are logged in.

Did you get a verify email and use the link?

After login, look in Account settings to make sure your client is linked.

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 5:44 am
by calxalot
What errors do you see in your web browser javascript console?

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 6:07 am
by DoctorBob
I was simply saying you should remove it from posts in this thread.
I see! Thank you, I have now redacted my email address in this post.

I am having difficulty logging back into my account. In Firefox I get a blank page at https://v8-3.foldingathome.org/machines
I switched to MS Edge and I see this error when I log in:
Multiple messages
Getting project causes failed
API error: TypeError: Failed to fetch

Signing in failed
API error: TypeError: Failed to fetch

This happens often when I login and logout a couple of times but it clears after waiting for 30 minutes or so.

Did you then login to your account in Web Control?
Web Control; is that: https://v8-3.foldingathome.org/account
If so, then yes I have.
I know that I am logged in (when I can login), when I select the Stats tab I see my username and donor stats.


Did you get a verify email and use the link?
Yes I did. Received 30/07/2024 at 10:54am
https://v8-3.foldingathome.org/verify/#########################################
When I select the link now, I see:
API call GET /verify/######################################### failed
API error: TypeError: NetworkError when attempting to fetch resource.


After login, look in Account settings to make sure your client is linked.
Where on the page will I find this?



What errors do you see in your web browser javascript console?
Once I can log back into my account I will have a look at the javascript console for errors.

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 6:34 am
by calxalot
You will see linked and possibly unlinked machines at bottom of account settings.
https://v8-3.foldingathome.org/account

FYI In v8.4.2, the machine linking has moved to the individual machine settings pages.
Not helpful if you see no machines when logged in.

There is a picture in the client guide
https://foldingathome.org/v8-3-client-guide/

Re: FAH-Client 8 not working on Ubuntu Server

Posted: Sun Aug 04, 2024 8:18 am
by DoctorBob
You will see linked and possibly unlinked machines at bottom of account settings.
https://v8-3.foldingathome.org/account
This is what I see when I log into https://v8-3.foldingathome.org/machines under the Machines tab:
Image


This is what I see in the Stats tab:
Image


This is what I see at https://v8-3.foldingathome.org/account
Image


What errors do you see in your web browser javascript console?
Not sure if this is the javascript console output. I found this if Firefox --> Web Developer Tools --> Inspector

Code: Select all

Web Control Version 8.3.18 index-78d84421.js:3643:83906
Object { account: {} }
index-78d84421.js:3643:83639
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Connecting to wss://node1.foldingathome.org/ws/account index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
broadcast: 
Object { cmd: "state", time: "2024-08-01T23:17:42.126Z", state: "fold" }
index-78d84421.js:3643:70298
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
Firefox can’t establish a connection to the server at ws://127.0.0.1:7396/api/websocket. index-78d84421.js:3643:67444
The connection to ws://127.0.0.1:7396/api/websocket was interrupted while the page was loading. index-78d84421.js:3643:67444
Connecting to ws://127.0.0.1:7396/api/websocket index-78d84421.js:3643:67404
All times are UTC
Page 1 of 2

Powered by phpBB® Forum Software © phpBB Limited