Skip to content

[Bug]: Container status is unhealthy #6178

Closed
@mtavano

Description

@mtavano

Error Message and Logs

I’ve been running Coolify on my Raspberry Pi 4 for almost 3 months without any issues.
I have Tailscale installed on the Pi, configured as an exit node, and I expose the Coolify dashboard using Cloudflare Tunnels, pointing it to a subdomain I manage.

Everything worked great during the first months—I could access the dashboard from anywhere, and whenever I needed to log into the machine, Tailscale made my life easier.

But since around 3 days ago, I can’t access the dashboard anymore—not through the tunnel, nor locally.
When I check the container, I see it has a unhealthy status.

Disclaimer:
All my containers that should be managed by coolify are running as expected. Everything working properly and checked one by one and is all right.

Here are the logs from my system:

> docker ps

3dbc93cf2a61   ghcr.io/coollabsio/coolify:4.0.0-beta.420.3                         "docker-php-serversi…"   9 days ago Up 9 hours (unhealthy)          8000/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8000->8080/tcp, [::]:8000->8080/tcp

container logs

> docker logs --tail 1000 -f 3dbc93cf2a61

-------------------------------------
ℹ️  Container Information
-------------------------------------

OS:            Alpine Linux v3.22
Docker user:   www-data
Docker uid:    9999
Docker gid:    9999
OPcache:       ✅ Enabled
PHP Version:   8.4.8
Image Version: v3.5.2-15993588015

ℹ️  NOTICE (init-webserver-config): /etc/nginx/nginx.conf already exists, so we'll use the existing file.
ℹ️  NOTICE (init-webserver-config): /etc/nginx/site-opts.d/http.conf already exists, so we'll use the existing file.
ℹ️  NOTICE (init-webserver-config): /etc/nginx/site-opts.d/https.conf already exists, so we'll use the existing file.
ℹ️  NOTICE (init-webserver-config): /etc/nginx/conf.d/default.conf already exists, so we'll use the provided configuration.
[08-Jul-2025 22:48:54] NOTICE: fpm is running, pid 59
[08-Jul-2025 22:48:54] NOTICE: ready to handle connections
curl: (7) Failed to connect to localhost port 8080 after 0 ms: Could not connect to server
❌ There seems to be a failure in checking the NGINX + PHP-FPM.
curl: (7) Failed to connect to localhost port 8080 after 5 ms: Could not connect to server
HTTP Status Code: 000
✅ NGINX + PHP-FPM is running correctly.
Migration is enabled on this server.

   INFO  Nothing to migrate.

Seeder is enabled on this server.

   INFO  Seeding database.

  Running in self-hosted mode.
  Database\Seeders\OauthSettingSeeder ................................ RUNNING
  Database\Seeders\OauthSettingSeeder ............................. 86 ms DONE

  Database\Seeders\PopulateSshKeysDirectorySeeder .................... RUNNING
  Database\Seeders\PopulateSshKeysDirectorySeeder ................. 53 ms DONE

  Database\Seeders\SentinelSeeder .................................... RUNNING
  Database\Seeders\SentinelSeeder ................................. 18 ms DONE

  Database\Seeders\RootUserSeeder .................................... RUNNING

  INFO  Root user already exists. Skipping creation.

  Database\Seeders\RootUserSeeder .................................. 3 ms DONE

  Database\Seeders\CaSslCertSeeder ................................... RUNNING
  Database\Seeders\CaSslCertSeeder ............................... 902 ms DONE

Error in sending live signal: cURL error 6: Could not resolve host: undead.coolify.io (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://undead.coolify.io/v4/alive?appId=f49dea8e86b96a682579bb3ee38fa79e&version=4.0.0-beta.420.3

I'v read that there are some problems between coolify tailscare. The weird thing is that the problem just started and I have had tailscale installed from the same time as coolify and it is just now giving me problems.

Steps to Reproduce

Example Repository URL

No response

Coolify Version

v4.0.0-beta.420.3

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12 (bookworm)

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions