-
Notifications
You must be signed in to change notification settings - Fork 123
Open
Description
I'm trying to add marzban node just using the official documentation. Here's docker-compose.yaml:
services:
marzban-node:
build: .
#image: gozargah/marzban-node:latest
restart: always
network_mode: host
# env_file: .env
environment:
SSL_CERT_FILE: "/var/lib/marzban-node/ssl_cert.pem"
SSL_KEY_FILE: "/var/lib/marzban-node/ssl_key.pem"
SSL_CLIENT_CERT_FILE: "/var/lib/marzban-node/ssl_client_cert.pem"
SERVICE_PROTOCOL: "rest"
volumes:
- /var/lib/marzban-node:/var/lib/marzban-node
Certificates are generated using certbot, except ssl_client_cer.pem I got from marzban panel when adding the node.
At marzban panel I type the sub.domain.com and 62050 port by default. What I see at the container logs on the node:
marzban-node-marzban-node-1 | INFO: Node service running on :62050
marzban-node-marzban-node-1 | INFO: Started server process [1]
marzban-node-marzban-node-1 | INFO: Waiting for application startup.
marzban-node-marzban-node-1 | INFO: Application startup complete.
marzban-node-marzban-node-1 | INFO: Uvicorn running on https://0.0.0.0:62050 (Press CTRL+C to quit)
marzban-node-marzban-node-1 | INFO: 1.1.1.1 connected, Session ID = "55ec7b2a-3a64-40b6-b06c-70934c9860c5".
marzban-node-marzban-node-1 | INFO: 1.1.1.1:37770 - "POST /connect HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:37770 - "POST /start HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:37770 - "POST /ping HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:37770 - "POST / HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:37770 - "POST /ping HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:37770 - "POST / HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:37770 - "POST /ping HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:47290 - "POST /ping HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | INFO: 1.1.1.1:47290 - "POST /ping HTTP/1.1" 200 OK
marzban-node-marzban-node-1 | WARNING: Restarting Xray core...
marzban-node-marzban-node-1 | WARNING: Xray core stopped
xray is constantly restarting. I tried to save the config coming from marzban master (stdin) to file and then manually run xray from inside of container, it's working:
$ docker exec -it 5e xray -config /var/lib/marzban-node/xray_config.json
Xray 25.9.5 (Xray, Penetrates Everything.) 118131f (go1.25.1 linux/amd64)
A unified platform for anti-censorship.
2025/09/09 21:10:15.334792 [Info] infra/conf/serial: Reading config: &{Name:/var/lib/marzban-node/xray_config.json Format:json}
2025/09/09 21:10:15.622676 [Warning] core: Xray 25.9.5 started
2025/09/09 21:10:16.793563 from 1.1.1.1:43644 accepted tcp:127.0.0.1:62051 [API_INBOUND -> API]
2025/09/09 21:10:17.107959 from 1.1.1.1:43982 accepted tcp:127.0.0.1:62051 [API_INBOUND -> API]
2025/09/09 21:10:17.506622 from 1.1.1.1:44556 accepted tcp:127.0.0.1:62051 [API_INBOUND -> API]
2025/09/09 21:10:17.908682 from 1.1.1.1:44930 accepted tcp:127.0.0.1:62051 [API_INBOUND -> API]
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels