Originally created by @phaidros7 on GitHub (Mar 3, 2016).
In certain environments a server cannot get HTTP[S] directly but only via a http_proxy. Would be nice to have a proxy seetting in /etc/letsencrypt.sh/config.sh for curl to use it :)
Originally created by @phaidros7 on GitHub (Mar 3, 2016).
In certain environments a server cannot get HTTP[S] directly but only via a http_proxy. Would be nice to have a proxy seetting in /etc/letsencrypt.sh/config.sh for curl to use it :)
You should be able to just set normal proxy environment variables, curl should see and use them.
See man curl under "Environment".
@lukas2511 commented on GitHub (Mar 5, 2016):
You should be able to just set normal proxy environment variables, curl should see and use them.
See `man curl` under "Environment".
@phaidros7 you can configure it in config, just use export HTTP_PROXY=... or whatever in config.sh, it should work
@lukas2511 commented on GitHub (Mar 9, 2016):
@phaidros7 you can configure it in config, just use `export HTTP_PROXY=...` or whatever in config.sh, it should work
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @phaidros7 on GitHub (Mar 3, 2016).
In certain environments a server cannot get HTTP[S] directly but only via a http_proxy. Would be nice to have a proxy seetting in /etc/letsencrypt.sh/config.sh for curl to use it :)
@lukas2511 commented on GitHub (Mar 5, 2016):
You should be able to just set normal proxy environment variables, curl should see and use them.
See
man curlunder "Environment".@phaidros7 commented on GitHub (Mar 7, 2016):
I agree, that's the way I did it, altho it'd have been nice to have it configurable in the config :_)
@lukas2511 commented on GitHub (Mar 9, 2016):
@phaidros7 you can configure it in config, just use
export HTTP_PROXY=...or whatever in config.sh, it should work