Local web console

[JL_678]

Hi,

I configured the web console in 8.1.13 beta, and it was a challenge. It works fine now, but the process was hard. You can read about it Here. If I upgrade to 8.3, is this process fixed? Is there a different way that I should think about this? THe challenge is that I have 5 servers running fah and want a common view.

As an aside, I would even be okay with a remote console, but as I recall, I could not get this to work with 8.1.13. Can I monitor my hosts remotely if I properly configure 8.3? (As I recall, the problem was that my FAH instances are running on headless servers so I could not access an FAH gui via a web browser on a machine running FAH.)

TIA!

[calxalot]

Something about your network is challenging.
Web Control v8.3 is very different than v8.1.
I cannot guarantee that v8.3 remote monitoring will work for you.

Can you access https://v8-3.foldingathome.org/ from your network?

If so, please register a new account and fill in your user, team and passkey.

You will need the account token to your account if you wish to try upgrading one client to 8.3.18 and linking it to the account.
For linking a client, see https://github.com/FoldingAtHome/fah-cl ... ssions/214

You should finish all work on a client you will upgrade.
I have not tried downgrading to v8.1, so I can't say that would be painless if you must revert.

If you cannot access the public web control, you can try installing a local 8.3.18 web control
viewtopic.php?t=39131

If v8.3.18 web control isn't in releases, see bleeding edge builds
https://master.foldingathome.org/builds/fah-client/
v8.3.17 and .18 are almost the same.

[calxalot]

Do not use web control 8.4.0 with client 8.3.

[JL_678]

Thank you. I will snapshot one machine and try upgrading and see what happens. To answer your other question, I can access that URL so hopefully I can use the web portal for management.

[JL_678]

Hi,

Just to share a quick update. The new portal works great and is much simpler than the old config! Awesome. The one weirdness is that my FAH instances skip the machine name parameter. Below is my config file, and while FAH connects fine, it ignores the supplied machine name and instead uses the host name. What am I missing?

Code: Select all

<config>
  <account-token v="<insert token>"/>
  <machine-name v="<hostname>"/>
</config>

[calxalot]

Note that account-token and machine-name in config.xml are only used on first run. After that, they live in client.db and are modified via web control. The same is true of all settings that are exposed in web control.

[JL_678]

I missed that. Thank you.

[calxalot]

For best results, config.xml should be created before installing, because the installer will start the client.

You can maybe still set account-token as long as it has remained blank. machine-name defaults to hostname on first run.

[JL_678]

Got it. Thank you again!