Docker-letsencrypt-nginx-proxy-companion: Certificates generation process gets killed

[kaiokenx10]

Hi,

I followed this tutorial and almost everything is working fine 😄. In general I see that the certificates are tried to be created but they fail. When I do this manually by running the renewal script I get this:

[root@ip-x-x-x-x ec2-user]# docker exec -it 0df6c255c4e8 /app/force_renew
/etc/nginx/certs/subdomain.domain.com /app
Creating/renewal subdomain.domain.com certificates... (subdomain.domain.com)
/app/letsencrypt_service: line 118:   184 Killed                  /usr/bin/simp_le -f account_key.json -f key.pem -f chain.pem -f fullchain.pem -f cert.pem $params_d_str --cert_key_size=$cert_keysize --server=$acme_ca_uri --default_root /usr/share/nginx/html/
/app

The directory with the certificates has the folder called subdomain.domain.com but it is empty, same as the other shared volumes used for the process like vhost.d and html.

Thx for any help here.

[buchdag]

Hi. Were you able to troubleshoot and/or solve this?

[kaipaysen]

Hi,

I've a very similar problem. The creation just doesn't work and I really don't have a clue on how to solve this.

This is the log from docker-compose

letsencrypt-nginx-proxy-companion_1 | Sleep for 3600s
letsencrypt-nginx-proxy-companion_1 | 2018/05/30 14:10:20 Generated '/app/letsencrypt_service_data' from 4 containers
letsencrypt-nginx-proxy-companion_1 | 2018/05/30 14:10:20 Running '/app/signal_le_service'
letsencrypt-nginx-proxy-companion_1 | 2018/05/30 14:10:20 Watching docker events
letsencrypt-nginx-proxy-companion_1 | 2018/05/30 14:10:20 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
letsencrypt-nginx-proxy-companion_1 | /etc/nginx/certs/ /app
letsencrypt-nginx-proxy-companion_1 | Reloading nginx proxy (a302670b486cb71dc7bad2416e93909f1770c8f540a2ad04ecf9c8cad22c90d6)...
letsencrypt-nginx-proxy-companion_1 | Q2018/05/30 14:10:21 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
letsencrypt-nginx-proxy-companion_1 | ;2018/05/30 14:10:21 [notice] 45#45: signal process started
letsencrypt-nginx-proxy-companion_1 | Creating/renewal certificates... ()
nginx-proxy_1 | Custom dhparam.pem file found, generation skipped
nginx-proxy_1 | forego | starting dockergen.1 on port 5000
nginx-proxy_1 | forego | starting nginx.1 on port 5100
nginx-proxy_1 | dockergen.1 | 2018/05/30 14:10:20 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
nginx-proxy_1 | dockergen.1 | 2018/05/30 14:10:20 Running 'nginx -s reload'
nginx-proxy_1 | dockergen.1 | 2018/05/30 14:10:20 Watching docker events
nginx-proxy_1 | dockergen.1 | 2018/05/30 14:10:20 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
letsencrypt-nginx-proxy-companion_1 | /app/letsencrypt_service: line 136: 156 Killed /usr/bin/simp_le -f account_key.json -f key.pem -f chain.pem -f fullchain.pem -f cert.pem $params_d_str --cert_key_size=$cert_keysize --server=$acme_ca_uri --default_root /usr/share/nginx/html/
letsencrypt-nginx-proxy-companion_1 | /app
letsencrypt-nginx-proxy-companion_1 | Sleep for 3600s

Any Ideas?
Kai

[buchdag]

Was it working before ? What version of the container are you using ? What OS, Docker and Docker Composer version are you using ? Can you share your compose file ?

[kaipaysen]

a) Well it's a first time setup for this particular project but has been used in other projects in the exact same way.
b) latest
c) Linux, 18.04.0-ce, 1.21.1, build 5a3f1a3
d) yes:
docker-compose-prod.yml.txt

[buchdag]

I have no idea how memory_limit plays with this container.

Have you tried raising the limit ? Using docker stat and manually triggering /app/signal_le_service, I just saw memory usage slightly above 30 Mib.

[kaipaysen]

Good hint. This particular server had swap disabled. That's why it didn't work here but in other projects with the same setup. Cheers mate!

[buchdag]

@kaiokenx10 I suspect your issue has the same cause.

[buchdag]

No update from issue creator, closing.