To Reproduce

1. curl -sSL https://dokploy.com/security/0.26.6.sh | bash after updating to v0.26.6

Current vs. Expected behavior

More of an FYI, really, if /so stumbles into this and is scared (like me -_-) that my computer will explode...

root@moops:~# curl -sSL https://dokploy.com/security/0.26.6.sh | bash
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Dokploy Security Configuration
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

👋 Hey! I noticed your Dokploy installation doesn't have
secure credentials configured yet.

📝 I'll set up unique, secure credentials for your database
automatically. This will only take a few seconds.

🔐 Generating secure credentials...
<some letters and numbers>
✅ Credentials saved securely in Docker Secrets (encrypted)
🔄 Updating database...
ALTER ROLE
🔄 Updating PostgreSQL service...
dokploy-postgres
overall progress: 1 out of 1 tasks
1/1: running
verify: Service dokploy-postgres converged
🔄 Updating Dokploy service...
dokploy
overall progress: 0 out of 1 tasks
1/1: no suitable node (host-mode port already in use on 1 node)

In any case, after running docker service & docker ps --filter "name=dokploy" it appears that my Dokploy services look healthy overall. The main dokploy service has 1/1 replicas running successfully for 2+ minutes on node , with port 3000 exposed correctly.

dokploy: 1/1 running (current task ID )
dokploy-postgres: 1/1 running
dokploy-redis: 1/1 running
foobs: 1/1 running

Previous tasks show normal shutdowns from the security script updates while older replicas were replaced cleanly.

rerunning 0.26.6.sh results in ✅ Secure credentials are already configured! (Stored securely in Docker Secrets)

Provide environment information

ubuntu:latest via Hetzner
0.26.6 :-)

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No