Closed JohnDepon closed 5 years ago
@JohnDepon I have tested in an environment with squid/3.3.8
and it works. What's the version on your side? (if you do a curl -v http://blabla.com
you will see Via: ....
- there is a good chance you can see the version there).
Also, ask the proxy administrator on the request_entities
option.
I'll be closing this as I'm unable to reproduce with a similar environment.
I had the same problem. Setting request_entities on
on squid.conf
resolved the issue for me.
I am trying to use this plugin, but I am in a unique situation where the box that's running certbot does not have direct internet access and it must use a proxy to reach outside.
I've set up the appropriate ENV variables so that certbot uses the proxy to reach the ACME servers, but that makes this plugin also use the proxy to talk to the PowerDNS API.
For some reason, Squid does not like the request being made causing certbot to fail with error:
Looking through the letsencrypt.log I can see that this error is returned by squid and not the PDNS API.
Any ideas on how to overcome this problem?