Open mejobloggs opened 3 years ago
Hi :blush: This snap has a daemon and a userspace service (like a daemon but in userspace), and each has its config. I'm planning to deprecate the daemon and to make a snap for that alone.
The command you use with snap stop
makes me think that you're using the daemon, even if in recent versions the daemon is folding-at-home-fcole90.client
. Its configuration is in /var/snap/folding-at-home-fcole90/common/
and owned by root.
When running folding-at-home-fcole90
as a command, it runs as a user service, and the config it uses is then the one you edited.
My recommendation is that you disable the daemon
sudo snap stop --disable folding-at-home-fcole90
sudo snap stop --disable folding-at-home-fcole90.client
so it won't run at boot. Then, add the command folding-at-home-fcole90
to your startup services, so it can run at every boot.
I hope this can help you have a smoother experience. Let me know if it works :wink:
I've edited ~/snap/folding-at-home-fcole90/common/config.xml to allow another pc on my network web access with and
If I restart my fah server and try visit the fah webpage, I get access-denied.
I then run: "sudo snap stop folding-at-home-fcole90" and "folding-at-home-fcole90"
Then I can access the fah webpage from my other pc.
How come when I restart my pc (so it's using default snap stuff) it doesn't allow the ips in the config.xml?