I am also willing to support beta efforts and test builds, if that is helpful. (I am running FAH in an LXC container and so can easily create and delete test machines.)
fah-client access issues with app.foldingathome.org - Github link: https://github.com/FoldingAtHome/fah-we ... /issues/76
For whatever reason, I have never been able to get web access working using app.foldingathome.org process even using shift-command-L. It feels like either a browser (Tested on multiple chrome versions) or an app permission issue. We tried all kind of permutations of settings and it would never work. I never saw any log errors even using debug and upping verbosity to 10. I am not sure exactly what is causing this, but it feels like a bug.
Suggested next steps:
- Document the ctrl-shift-l thing
- Troubleshoot to understand if this is indeed a permission issue
@calxalot suggested this, and it worked! But, it still only works by going to http://<fah_ip>:7396 and app.foldingathome.org still fails. I continue to wonder if there is a permission or browser issue as noted above. Once I got access, I had WU assignment problems.
Suggested next steps:
- Document the process of setting up the local GUI
- Back to the previous comment, check out potential permission issues
I had WU assignment issues as shown in the logs in the post linked above. The solution was to up the number of CPUs to 2. (My container has 2 CPUs.) Why did I need to do that?
Suggested next steps:
- Understand how WUs relate to # of CPUs and determine why 2 CPUs are required for WU assignment
This is still an issue for unknown reasons. I can easily access the API via both my local browser and curl on the headless server. I cannot figure out why the web client cannot populate this.
Update: For reasons that I cannot determine, the cause drop down just populated!
Suggested next steps:
- Understand the cause drop down population process and research why it would take 4+ hours to populate