Nicolas Duchon

@hryamzik could you try replacing `-out fullchain.pem` with `-out cert.pem` in your `openssl` command ?

Not while using `simp_le` in standalone, but with `letsencrypt-nginx-proxy-companion` it's quite common to curl the challenge file in order to troubleshoot a failed domain validation. [This comment in particular](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/issues/209#issuecomment-347359735) made...

I recognize that the challenge file itself and its content are completely irrelevant to the troubleshooting process, you might as well `echo 'Hello, world' > hello-world` on the webroot and...

Agreed, just keeping every challenge file that the validation server fails to get kind of undo https://github.com/zenhack/simp_le/commit/212acd3efa6090641845bc08b63a512b082e0cb0. Do you think this (the challenge file mentioned in the error message being...

> Maybe we could just log the fact that we're deleting those files at info level instead of debug? I'd say that would be enough.

@alexharrington could you try with `nginxproxy/nginx-proxy:1642` (same as `main` branch but with #1641 merged in) ?

@alexharrington #1644 will be merged by the end of the week and will allow to disable `HTTP/2` entirely.

Could you try mounting a file to `/etc/nginx/conf.d/custom_proxy_settings.conf`, containing the following line : ```nginx http2_max_concurrent_streams 256; ``` [The exact name of the file isn't important, it just have to end...

I'm skimming through the diff between `0.8.0` and `0.9.0`, the only possibly impacting changes were the upgrade from nginx `1.19.3` to `1.19.10` and the addition of `sed -i 's/worker_connections 1024/worker_connections...

I've just pushed `nginxproxy:nginx-proxy:1642` again. It's identical to the `main` branch except for a downgrade to nginx `1.19.3`.