Service stuck in `Instance is starting... Waiting for health checks to pass.`

[Emilien_Chauvet]

Hi koyeb team!
I am facing issues deploying a service (b21d8b0d-6428-4b37-8dbe-ca750bfcd4db for reference).
I’ve tried a couple times, the build phase goes smoothly, but the deployment gets stuck at health checks, the instance does not start.

I’ve checked

• All operational on status.koyeb
• on other services
• tried the same service in other regions () and machines ()

I might have missed something, this seems to be something on my deployment script that gets the instance stuck but the logs don’t offer much more visibility.

Anyone has encountered this issue already ?

[Pawel_Beza]

Hey @Emilien_Chauvet, indeed there might be some issues with reporting logs for your specific services, we’re looking into this.

In the meantime I checked manually your logs:

2025/07/10 07:38:04 logtail started
2025/07/10 07:38:04 Program starting: v1.76.6-AlpineLinux, Go 1.23.9: []string{"tailscaled", "--tun=userspace-networking", "--socks5-server=localhost:1055"}
2025/07/10 07:38:04 LogID: a6702d1fa16af450ab20262cce9faf5cf1564d676c3d99215bde1c0a0fa571dc
2025/07/10 07:38:04 logpolicy: using system state directory "/home/adminuser/.local/share/tailscale"
logpolicy.ConfigFromFile /home/adminuser/.local/share/tailscale/tailscaled.log.conf: open /home/adminuser/.local/share/tailscale/tailscaled.log.conf: no such file or directory
logpolicy.Config.Validate for /home/adminuser/.local/share/tailscale/tailscaled.log.conf: config is nil
2025/07/10 07:38:04 dns: [rc=unknown ret=direct]
2025/07/10 07:38:04 dns: using "direct" mode
2025/07/10 07:38:04 dns: using *dns.directManager
2025/07/10 07:38:04 flushing log.
2025/07/10 07:38:04 logger closing down
2025/07/10 07:38:04 dns: inotify addwatch: context canceled
2025/07/10 07:38:04 safesocket.Listen: listen unix /var/run/tailscale/tailscaled.sock: bind: no such file or directory
failed to connect to local tailscaled; it doesn't appear to be running

so it seems like there is some connection failure to tailscaled

[Emilien_Chauvet]

Thank you @Pawel_Beza for sharing the logs. Indeed this is helpful!
I retried and it seems to be much better now, I now have logs I can use to debug

[Emilien_Chauvet]

@Pawel_Beza I’m actually encountering the same lack of logs for another service: dc117233-5179-49a0-b26a-fb2bc1606753

Exact same symptoms: health checks are hanging forever on my side.
Am I missing something with the configs that causes that ?

For context the mentioned service was built following this piece of doc.

Thanks again!

[nicolas]

Hey! I think you used the wrong port, your environment variable sets 8080 but your Koyeb service definition sets 8000.

[Emilien_Chauvet]

That was quick @nicolas
Indeed, works like a charm now!