Error 400

[jmaxdev]

To Reproduce

I don't know how to reproduce it, but today I opened the panel and found this error.

Current vs. Expected behavior

I should load the panel with all the projects, or at least the Dokploy UI.

Provide environment information

OS: 20.04
Arch: x86_64
Dokploy: v0.26.3
VPS Provider: No

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

Local Development

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

Same server where Dokploy is installed

Additional context

Will you send a PR to fix it?

No

[jmaxdev]

logs

dokploy.1.mxay2s13gzqt@unix    |
dokploy.1.mxay2s13gzqt@unix    | > dokploy@v0.26.3 start /app
dokploy.1.mxay2s13gzqt@unix    | > node -r dotenv/config dist/server.mjs
dokploy.1.mxay2s13gzqt@unix    |
dokploy.1.mxay2s13gzqt@unix    | Main config already exists
dokploy.1.mxay2s13gzqt@unix    | Default traefik config already exists
dokploy.1.mxay2s13gzqt@unix    | ✅ Critical initialization complete
dokploy.1.mxay2s13gzqt@unix    | Default middlewares already exists
dokploy.1.mxay2s13gzqt@unix    | Network is already initilized
dokploy.1.mxay2s13gzqt@unix    | {
dokploy.1.mxay2s13gzqt@unix    |   severity_local: 'NOTICE',
dokploy.1.mxay2s13gzqt@unix    |   severity: 'NOTICE',
dokploy.1.mxay2s13gzqt@unix    |   code: '42P06',
dokploy.1.mxay2s13gzqt@unix    |   message: 'schema "drizzle" already exists, skipping',
dokploy.1.mxay2s13gzqt@unix    |   file: 'schemacmds.c',
dokploy.1.mxay2s13gzqt@unix    |   line: '132',
dokploy.1.mxay2s13gzqt@unix    |   routine: 'CreateSchemaCommand'
dokploy.1.mxay2s13gzqt@unix    | }
dokploy.1.mxay2s13gzqt@unix    | {
dokploy.1.mxay2s13gzqt@unix    |   severity_local: 'NOTICE',
dokploy.1.mxay2s13gzqt@unix    |   severity: 'NOTICE',
dokploy.1.mxay2s13gzqt@unix    |   code: '42P07',
dokploy.1.mxay2s13gzqt@unix    |   message: 'relation "__drizzle_migrations" already exists, skipping',
dokploy.1.mxay2s13gzqt@unix    |   file: 'parse_utilcmd.c',
dokploy.1.mxay2s13gzqt@unix    |   line: '207',
dokploy.1.mxay2s13gzqt@unix    |   routine: 'transformCreateStmt'
dokploy.1.mxay2s13gzqt@unix    | }
dokploy.1.mxay2s13gzqt@unix    | Migration complete
dokploy.1.mxay2s13gzqt@unix    | Setting up cron jobs....
dokploy.1.mxay2s13gzqt@unix    | [Backup] web-server Enabled with cron: [0 0 * * *]
dokploy.1.mxay2s13gzqt@unix    | [Backup] mongo Enabled with cron: [0 0 * * *]
dokploy.1.mxay2s13gzqt@unix    | Starting log requests cleanup 0 0 * * *
dokploy.1.mxay2s13gzqt@unix    | Initializing 1 schedules
dokploy.1.mxay2s13gzqt@unix    | Initialized schedule: crawl compose ✅
dokploy.1.mxay2s13gzqt@unix    | Setting up cancel deployments....
dokploy.1.mxay2s13gzqt@unix    | Cancelled 0 deployments
dokploy.1.mxay2s13gzqt@unix    | Setting up volume backups cron jobs....
dokploy.1.mxay2s13gzqt@unix    | Initializing 3 volume backups
dokploy.1.mxay2s13gzqt@unix    | Initialized volume backup: Extension compose ✅
dokploy.1.mxay2s13gzqt@unix    | Initialized volume backup: b compose ✅
dokploy.1.mxay2s13gzqt@unix    | Initialized volume backup: pds-data compose ✅
dokploy.1.mxay2s13gzqt@unix    | Server Started on: http://0.0.0.0:3000
dokploy.1.mxay2s13gzqt@unix    | Starting Deployment Worker
dokploy.1.mxay2s13gzqt@unix    |  ⨯ Error: Failed to load external module @ai-sdk/azure: Error: ENOENT: no such file or directory, open '/app/node_modules/.pnpm/@ai-stk+azure@2.0.16_zod@3.25.32/node_modules/@ai-sdk/azure/dist/index.mjs'
dokploy.1.mxay2s13gzqt@unix    |     at Context.externalImport [as y] (.next/server/chunks/ssr/[turbopack]_runtime.js:497:15)
dokploy.1.mxay2s13gzqt@unix    |     at async (.next/server/chunks/ssr/[root-of-the-server]__5544ad29._.js:1:3762)
dokploy.1.mxay2s13gzqt@unix    |  ⨯ Error: Failed to load external module @ai-sdk/azure: Error: ENOENT: no such file or directory, open '/app/node_modules/.pnpm/@ai-stk+azure@2.0.16_zod@3.25.32/node_modules/@ai-sdk/azure/dist/index.mjs'

dokploy-postgres

▶ docker service logs dokploy-postgres
dokploy-postgres.1.af5z9xipofg4@unix    |
dokploy-postgres.1.af5z9xipofg4@unix    | PostgreSQL Database directory appears to contain a database; Skipping initialization
dokploy-postgres.1.af5z9xipofg4@unix    |
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:34:06.933 UTC [1] LOG:  starting PostgreSQL 16.11 (Debian 16.11-1.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:34:07.162 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:34:07.162 UTC [1] LOG:  listening on IPv6 address "::", port 5432
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:34:07.976 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:34:09.180 UTC [29] LOG:  database system was shut down at 2026-01-05 08:31:04 UTC
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:34:13.873 UTC [1] LOG:  database system is ready to accept connections
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:39:09.209 UTC [27] LOG:  checkpoint starting: time
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 08:39:09.490 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.136 s, sync=0.041 s, total=0.282 s; sync files=4, longest=0.023 s, average=0.011 s; distance=3 kB, estimate=3 kB; lsn=0/38AAFC8, redo lsn=0/38AAF90
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 22:24:22.776 UTC [27] LOG:  checkpoint starting: time
dokploy-postgres.1.af5z9xipofg4@unix    | 2026-01-05 22:24:23.524 UTC [27] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.521 s, sync=0.080 s, total=0.749 s; sync files=6, longest=0.064 s, average=0.014 s; distance=12 kB, estimate=12 kB; lsn=0/38AE388, redo lsn=0/38AE350

dokploy-redis

▶ docker service logs dokploy-redis
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:C 05 Jan 2026 08:33:44.983 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:C 05 Jan 2026 08:33:44.983 * Redis version=7.4.7, bits=64, commit=00000000, modified=0, pid=1, just started
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:C 05 Jan 2026 08:33:44.983 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.420 * monotonic clock: POSIX clock_gettime
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.510 * Running mode=standalone, port=6379.
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.511 * Server initialized
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.708 * Loading RDB produced by version 7.4.7
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.708 * RDB age 162 seconds
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.708 * RDB memory usage when created 1.45 Mb
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.709 * Done loading RDB, keys loaded: 3, keys expired: 1.
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.710 * DB loaded from disk: 0.199 seconds
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 08:33:45.710 * Ready to accept connections tcp
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 09:23:52.264 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 09:23:52.266 * Background saving started by pid 21
dokploy-redis.1.dlhh9zghy9rh@unix    | 21:C 05 Jan 2026 09:23:52.360 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 21:C 05 Jan 2026 09:23:52.362 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 09:23:52.367 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 10:14:22.477 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 10:14:22.478 * Background saving started by pid 22
dokploy-redis.1.dlhh9zghy9rh@unix    | 22:C 05 Jan 2026 10:14:22.555 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 22:C 05 Jan 2026 10:14:22.556 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 10:14:22.580 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 11:04:22.671 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 11:04:22.673 * Background saving started by pid 23
dokploy-redis.1.dlhh9zghy9rh@unix    | 23:C 05 Jan 2026 11:04:22.767 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 23:C 05 Jan 2026 11:04:22.769 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 11:04:22.774 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 11:55:22.978 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 11:55:22.979 * Background saving started by pid 24
dokploy-redis.1.dlhh9zghy9rh@unix    | 24:C 05 Jan 2026 11:55:23.078 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 24:C 05 Jan 2026 11:55:23.080 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 11:55:23.081 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 12:46:53.210 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 12:46:53.211 * Background saving started by pid 25
dokploy-redis.1.dlhh9zghy9rh@unix    | 25:C 05 Jan 2026 12:46:53.293 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 25:C 05 Jan 2026 12:46:53.295 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 12:46:53.313 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 13:36:53.488 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 13:36:53.489 * Background saving started by pid 26
dokploy-redis.1.dlhh9zghy9rh@unix    | 26:C 05 Jan 2026 13:36:53.581 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 26:C 05 Jan 2026 13:36:53.583 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 13:36:53.591 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 14:27:53.646 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 14:27:53.648 * Background saving started by pid 27
dokploy-redis.1.dlhh9zghy9rh@unix    | 27:C 05 Jan 2026 14:27:53.744 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 27:C 05 Jan 2026 14:27:53.746 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 14:27:53.750 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 15:20:23.835 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 15:20:23.837 * Background saving started by pid 28
dokploy-redis.1.dlhh9zghy9rh@unix    | 28:C 05 Jan 2026 15:20:23.941 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 28:C 05 Jan 2026 15:20:23.943 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 15:20:24.040 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 16:12:54.027 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 16:12:54.028 * Background saving started by pid 29
dokploy-redis.1.dlhh9zghy9rh@unix    | 29:C 05 Jan 2026 16:12:54.135 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 29:C 05 Jan 2026 16:12:54.137 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 16:12:54.231 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 17:05:24.151 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 17:05:24.152 * Background saving started by pid 30
dokploy-redis.1.dlhh9zghy9rh@unix    | 30:C 05 Jan 2026 17:05:24.234 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 30:C 05 Jan 2026 17:05:24.236 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 17:05:24.254 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 17:55:54.442 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 17:55:54.444 * Background saving started by pid 31
dokploy-redis.1.dlhh9zghy9rh@unix    | 31:C 05 Jan 2026 17:55:54.557 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 31:C 05 Jan 2026 17:55:54.559 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 17:55:54.647 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 18:45:54.697 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 18:45:54.698 * Background saving started by pid 32
dokploy-redis.1.dlhh9zghy9rh@unix    | 32:C 05 Jan 2026 18:45:54.780 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 32:C 05 Jan 2026 18:45:54.782 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 18:45:54.800 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 19:36:55.006 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 19:36:55.008 * Background saving started by pid 33
dokploy-redis.1.dlhh9zghy9rh@unix    | 33:C 05 Jan 2026 19:36:55.099 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 33:C 05 Jan 2026 19:36:55.101 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 19:36:55.110 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 20:27:55.217 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 20:27:55.218 * Background saving started by pid 34
dokploy-redis.1.dlhh9zghy9rh@unix    | 34:C 05 Jan 2026 20:27:55.280 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 34:C 05 Jan 2026 20:27:55.282 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 20:27:55.320 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 21:18:55.544 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 21:18:55.545 * Background saving started by pid 35
dokploy-redis.1.dlhh9zghy9rh@unix    | 35:C 05 Jan 2026 21:18:55.633 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 35:C 05 Jan 2026 21:18:55.635 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 21:18:55.647 * Background saving terminated with success
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 22:11:25.688 * 100 changes in 300 seconds. Saving...
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 22:11:25.690 * Background saving started by pid 36
dokploy-redis.1.dlhh9zghy9rh@unix    | 36:C 05 Jan 2026 22:11:25.769 * DB saved on disk
dokploy-redis.1.dlhh9zghy9rh@unix    | 36:C 05 Jan 2026 22:11:25.771 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
dokploy-redis.1.dlhh9zghy9rh@unix    | 1:M 05 Jan 2026 22:11:25.791 * Background saving terminated with success

Also, I used docker prune, but it doesn't seem to have worked.

[digitaldrreamer]

Same issue also just happened to us. Dashboard is completely inaccessible.