Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fah-gpu behind a proxy #24

Open
eingemaischt opened this issue Dec 17, 2021 · 2 comments
Open

fah-gpu behind a proxy #24

eingemaischt opened this issue Dec 17, 2021 · 2 comments

Comments

@eingemaischt
Copy link

Hi,

I do need to set a proxy server - while this is no problem in docker, and docker normally adds these settings to the container, the fah client seems to ignore them.

So the container is stuck at
~/fah# docker logs fah0
13:18:19:Downloading GPUs.txt from assign1.foldingathome.org:80
13:18:19:Connecting to assign1.foldingathome.org:80

How can I set the proxy inside the container?

@eingemaischt
Copy link
Author

I added proxy-enable and proxy to the config.xml but itt didn't do anything.

I tried to start it manually inside the container with FAHClient --chdir /fah --proxy-enable --proxy address:3128
, it stated two warninge (
13:29:49:WARNING:Option 'proxy-enable' already set to 'true' reseting to 'true'.
13:29:49:WARNING:Option 'proxy' already set to 'host:3128' reseting to 'host:3128'.
)
and it worked...

@beberg
Copy link
Contributor

beberg commented Feb 15, 2022

Following the README, the client should be using the config.xml setup in $HOME/fah/config.xml so should follow any proxy settings there. The container is designed to never need flags added, etc.

You can run the container with -ti instead of -d, and --configure at the end to do all configuration, like this:

docker run --name fah0 -ti --user "$(id -u):$(id -g)" --volume $HOME/fah:/fah foldingathome/fah-gpu:latest --configure

Does that help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants