How do you access the web GUI remotely?

[jl-678]

My FAH Debian Buster server is headless. With v7, I could access the basic client GUI remotely and while its functionality was limited, it was something. I am trying to determine how to do something similar with v8.1.11 and am currently running the client with the following command.

/usr/bin/fah-client --allow=<home_ip_range>/24 --http-addresses=<IP of local machine>:7396 --log=/var/log/fah-client/log.txt --log-rotate-dir=/var/log/fah-client/

Unfortunately, I get a 404 error when I go to http://:7396, and https://app.foldingathome.org/ is stuck on "connecting" because it cannot be run locally.

Am I missing something with the above configuration parameters? Is there something else I can do to enable this use case?

Thank you.

[kbernhagen]

You need --http-addresses=0.0.0.0:7396

You should probably always include 127.0.0.1 in allow.
You need --deny=0/0 for allow to work.
The defaults are effectively allow any, deny none.

[kbernhagen]

If you don't want to use a localhost client as a trampoline via peers,
you can load https://app.foldingathome.org/ and type Control-Shift-L to change the client.
This is stored in the browser database for the site.

[jl-678]

Okay, so I ended up with this:

/usr/bin/fah-client --allow=127.0.0.1 --deny=0/0 --http-addresses=0.0.0.0:7396 --log=/var/log/fah-client/log.txt --log-rotate-dir=/var/log/fah-client/

Then I go to the client and do the control-shift-L thing, and it sits there saying "Connecting." (The screen is static.) This is on a Debian 10 system. I also have access to an Ubuntu system if you want me try that.

What am I missing?

Edit:
I see these exceptions, but I think that they relate to my lack of a GPU. However, I wanted to include these lines in case they relate.

21:41:59:E :Exception: Failed to open dynamic library 'libcuda.so': libcuda.so: cannot open shared object file: No such file or directory
21:41:59:E :Exception: clGetPlatformIDs() returned -1001

[kbernhagen]

You need something like --allow="127.0.0.1 10.0.0.0/8 192.168.0.0/16 172.16.0.0/12 169.254.0.0/16"

You can remove the addresses that don't apply.

You should add your changes to a config.xml in the working directory for the client.

I believe by default it is a symlink to /etc/fahclient/config.xml.

You are using the systemd service as installed by the deb package?

[jl-678]

I will test that out. I am currently not using a config.xml or systemd instead am running from a simple shell script including the above command. Once I get it running correctly, I will update the config.xml accordingly. However, I find the script easier as I can watch the output.

Edit:
It might be good to log failed access like this to help with troubleshooting. Maybe I up the log level on the CLI to get that?

[kbernhagen]

Example config.xml

<config>
  <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'/>
</config>

[jl-678]

Okay, that matches v7. I assume that it will work equally well on the CLI for testing. Right? Meaning passing the data in directly to fah-client.

[kbernhagen]

If you have the debug build, don't go above verbosity 3.

[jl-678]

I am running standard. (e.g. non-debug.) I can use that version if you prefer.

[kbernhagen]

The command line overrides what is found in config.xml, if it exists. Same otherwise.

Anything exposed in Web Control is stored in client.db. For those values, config.xml is just first-run defaults.

[kbernhagen]

Try release with higher verbosity first.
I can't remember what is logged where at what verbosity.

[jl-678]

Question where is client db stored? I wonder if it has legacy data from v7 that is causing problems. I assume that it is a sqlite DB. Correct?

Here is the latest with the same issue:
/usr/bin/fah-client --allow='127.0.0.1 10.25.0.0/24' --deny=0/0 --http-addresses=0.0.0.0:7396 --log=/var/log/fah-client/log.txt --log-rotate-dir=/var/log/fah-client/ --verbosity=5

The logs look okay as far as I can tell. There are no obvious error that appear beside the aforementioned libcuda stuff, and 5 seems to be the highest verbosity. (I tried 20 and saw nothing more.)

Should I switch to the debug version?

[kbernhagen]

client.db is created in the current working directory of the running client.
v7 uses a different database ./work/client.db.
There can be no conflict.

Yes, sqlite3. Please do not try to edit it.

[kbernhagen]

What you have looks correct to me.

Assuming you're trying to connect from subnet 10.25.0.0/24.

Please try debug build verbosity 3.

[kbernhagen]

Are you running the client inside a container?

[kbernhagen]

Instead of sanctuary.local you would use your server hostname or ip.

[kbernhagen]

Actually, when it says connecting, you can possibly use Control-shift-L

[kbernhagen]

That’s not as good if you want to direct connect to multiple servers.

But once you have one client connecting, you can add others as peers.

[jl-678]

It works!!!!! I think that maybe part of the problem with the test was that going to :7396 results in the system trying to connect to 127.0.0.1 (when hitting ctr-shift-l you see this.)

Not sure if the js fixes you mentioned did anything, but I added those too.

[jl-678]

Thank you SOOOOO much! I really appreciate your patience.

Question for you. Can I help you on this project with troubleshooting or testing on one of my other systems?

BTW, the successful system is the LXC container running Ubuntu.

[jl-678]

Question: I see a bunch of this in the work unit log. Should I be concerned?

BLE: {"error":"No appropriate assignment"}
01:35:21:I1::WU3:Retry #3 in 8 secs
01:35:29:I1::WU3:Requesting WU assignment
01:35:29:I1:OUT9:> POST https://assign4.foldingathome.org/api/assign HTTP/1.1
01:35:30:I1:OUT9:< assign4.foldingathome.org:443 HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE
01:35:30:E ::WU3:HTTP_SERVICE_UNAVAIL

[kbernhagen]

Yeah! You're now an expert.
Maybe you can help others on foldingforum.org, as time permits?

I haven't heard about anyone testing high thread-count servers.
If you have anything with more than 64 threads, please report your experiences on the forum. Any Windows machines with more than 32 threads too.

Please continue to report bugs and feature requests on GitHub.
Please also check closed issues before creating a new issue.

I wouldn't worry about that log output as long as you get WU assignments.

[kbernhagen]

Did you also get https://app.foldingathome.org working?

[jl-678]

No, that did not work. I could only get there via http://ip:7396.

I am still concerned about getting jobs. I will circle back in that.

[kbernhagen]

Yea, not getting assignments is a different issue.
Please ask on https://foldingforum.org
Folks there will be familiar with the myriad ways that can break.

[jl-678]

Okay, I just wanted to be sure that it was not related to the beta. I do have a couple of questions about this:

• There is a Beta checkbox under project settings. What does that do and why would I check it?
• There is a drop down called "cause" which is unpopulated. Is something supposed to be in there?

This is particularly curious because in v7, I had the ability to choose a cause and do not seem to be able to do that in the v8 gui.

[kbernhagen]

The beta checkbox is for beta WUs.
Do not use it unless you have been told to.

The causes issue I answered on the forum.

[jl-678]

Okay, thx. I assume that you want to talk API and WUs in the forum and so I will follow-up there.

[kbernhagen]

@jcoffland please consider leaving this open with label Documentation.
I think if you close it, there will be duplication.
Thanks.

[kbernhagen]

I am attempting to keep up-to-date info on FoldingForum:
HOWTO: Allow v8 Client Remote Control
HOWTO: Local v8 Web Control