Remove host port publish to fix Dokploy bind conflict

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
test2
2026-07-25 21:18:34 +03:00
co-authored by Cursor
parent fa8e886c1c
commit e8fb5ca00c
2 changed files with 5 additions and 3 deletions
+4 -1
View File
@@ -37,9 +37,12 @@ PUBLIC_HOST=ваш-домен-или-ip
POSTGRES_PASSWORD=надежный-пароль-бд
```
4. Deploy. Панель: порт `20000` (или домен через Traefik в Dokploy).
4. Deploy. Доступ через домен Dokploy (сервис `panel`, порт контейнера `20000`).
5. Вход: `/admin/login`
Не публикуйте host-порт в compose — иначе будет `port is already allocated`.
В ENV Dokploy удалите `PANEL_PORT`, если он остался от старых деплоев.
### Если Bad Gateway (502)
1. В Dokploy Domain укажите сервис **`panel`**, порт **`20000`** (не `postgres`).
+1 -2
View File
@@ -10,8 +10,7 @@ services:
condition: service_healthy
expose:
- "20000"
ports:
- "${PANEL_PORT:-20000}:20000"
# No host ports — Dokploy/Traefik routes via dokploy-network (avoids "port already allocated")
environment:
APP_NAME: ${APP_NAME:-VpnPanel}
SECRET_KEY: ${SECRET_KEY:-change-me-to-a-long-random-string}