[Bug]: cURL error 6: Could not resolve host: api.github.com

[Simplegram]

Error Message and Logs

2025-May-01 04:54:10.210443 Starting deployment of Simplegram/htmx-transport-tracker:main to blue-bird-hk0cows8s800g0kgc04sso4c.
2025-May-01 04:54:10.523237 Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:1.0.8.
2025-May-01 04:54:10.819546 [CMD]: docker inspect -f '{{.State.Running}}' ik80000ock4wkss40oos4os0
2025-May-01 04:54:10.819546
2025-May-01 04:54:10.826520 Error: No such object: ik80000ock4wkss40oos4os0
2025-May-01 04:54:11.018569 [CMD]: docker rm -f ik80000ock4wkss40oos4os0
2025-May-01 04:54:11.018569 Error response from daemon: No such container: ik80000ock4wkss40oos4os0
2025-May-01 04:54:11.313407 [CMD]: docker run -d --network coolify --name ik80000ock4wkss40oos4os0 --rm -v /root/.docker/config.json:/root/.docker/config.json:ro -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/coollabsio/coolify-helper:1.0.8
2025-May-01 04:54:11.313407 d047914d4b36b5a4a82ea2259e25cbc56eee502b9f6d79a3cf5baaaa0072b5ac
2025-May-01 04:54:12.539903 Oops something is not okay, are you okay? 😢
2025-May-01 04:54:12.548050 cURL error 6: Could not resolve host: api.github.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://api.github.com/zen
2025-May-01 04:54:12.572773 Gracefully shutting down build container: ik80000ock4wkss40oos4os0
2025-May-01 04:54:12.856422 [CMD]: docker inspect -f '{{.State.Running}}' ik80000ock4wkss40oos4os0
2025-May-01 04:54:12.856422 true

Steps to Reproduce

I'm not sure but this happens after a power loss where my server automatically goes to hibernation.

1. Debian server goes to hibernation after a power loss
2. After power is restored, I wake the server and continue from hibernation
3. I went to restart a running coolify container (green and healthy server)
4. cURL error on new deployment

Example Repository URL

No response

Coolify Version

v4.0.0-beta.415

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian 12 (bookworm)

Additional Information

• Running and healthy containers from before hibernation are still running and healthy. Error comes up after restart/new deployment.
• I have restarted Docker with systemctl. After a Docker restart, running and healthy containers from before the restart are still running and healthy.
• I can access the web no problem, the only problem is on deployment
• I can successfully deploy a service (Supabase)
• I have changed my DNS nameserver
• I have switched Cloudflare Warp on and off (warp-cli disconnect and connect)
• I have changed my router's DNS
• I have tried to cURL api.github.com inside a running coolify container and it works
• I have tried to ping api.github.com inside a running coolify container and it works
• I have restarted two of my proxy servers (cloning a container to another server results in the same deployment error)

[Simplegram]

Downgrading to v4.0.0-beta.410 works for now

[Cinzya]

That usually happens due to an DNS error. I'm at least not able to replicate this on any of my Coolify instances at the moment. When you change the DNS server in the coolify settings (Settings > DNS Validation > DNS Server) you usually have to restart Coolify and / or Docker, as far as I know.

Downgrading most likely fixed it for you, because that process will restart Coolify, applying the changes of the new DNS Server. Ideally you add two DNS Servers in the Coolify settings, in case one of them is out of service or has other issues. E.g. 1.1.1.1,8.8.8.8 and then update your Coolify again.

[Simplegram]

Thank you for the recommendation. After adding a second DNS server and upgrading Coolify to v4.0.0-beta.416, the issue does not appear.