You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The companion has been working fine for the last 6 months I've been using it, but I setup a new service last week, and the SSL certificate was not created for this one.
Digging into the issue, it seems the key and crt files are not created, similar to #1042, and when running docker exec acme-companion /app/force_renew, the creation takes forever (kind of like #1049), and returns this error:
$ docker exec reverse_proxy_acme /app/force_renew
Creating/renewal service.example.com certificates... (service.example.com)
[Mon Aug 21 22:00:45 UTC 2023] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 28
[Mon Aug 21 22:00:45 UTC 2023] Can not init api for: https://acme-v02.api.letsencrypt.org/directory.
for all services, new and old.
acme-companion image version
Info: running acme-companion version v2.2.8-14-g9fbd668
I am seeing something very similar with 2.2.9
When the Acme Companion starts it correctly outputs its version number and then nothing.
Running with DEBUG=1 yield no more logs.
Trying to execute docker exec acme-companion /app/force_renew the command just hangs indefinitely.
As it seems 2.2.9 has updated many dependencies based on depandabot recommendations maybe this is the culprit?
I tried introducing a fault where the Acme Companion did not know of the nginx-proxy container by not:
Providing the volumes-from directive
Providing the label
Providing the env var
This still did not give any error messages.
I have reverted back to 2.2.8 for now as this has fixed the problem.
Further, 2.2.8 will provide error messages for what to do when in a faulty state as described above.
Happy to help test what ever is necessary to find the problem.
There is a known issue with the version of curl currently shipped with Alpine 3.19 and 3.x kernels, causing an endless loop to hang containers, usually on startup. The 3.x kernel line has been End of Life since 2017, but some prebuilt systems such as older Synology NAS units are still running it.
While a fix has been applied to the affected upstream library we do not have an ETA for if or when it will find its way into the version of curl shipped with Alpine 3.19.
Bug description
The companion has been working fine for the last 6 months I've been using it, but I setup a new service last week, and the SSL certificate was not created for this one.
Digging into the issue, it seems the key and crt files are not created, similar to #1042, and when running
docker exec acme-companion /app/force_renew
, the creation takes forever (kind of like #1049), and returns this error:for all services, new and old.
acme-companion image version
nginx-proxy's Docker configuration
Service
docker-compose.yml
Reverse proxy
docker-compose.yml
:rendered nginx configuration
Please provide the rendered nginx configuration:
Containers logs
Please provide the logs of:
docker logs name-of-the-companion-container
Docker host
The text was updated successfully, but these errors were encountered: