examples: ADMIN_BIND collides with SERVER_PORT=8081

public-free and paid-relay both set SERVER_PORT=8081, which is the ADMIN_BIND
default (config.rs). An operator following either example with the admin plane
enabled gets 'Address already in use' at startup and no obvious cause. Moves
ADMIN_BIND rather than SERVER_PORT so the nginx config in the example still
matches.
This commit is contained in:
jwinterm
2026-08-03 15:46:07 -04:00
parent c64cd9be8e
commit bdc76bd3a8
2 changed files with 10 additions and 0 deletions
+5
View File
@@ -13,6 +13,11 @@
SERVER_HOST=127.0.0.1
SERVER_PORT=8081
# ADMIN_BIND defaults to 127.0.0.1:8081, which is the SAME port as SERVER_PORT
# above. With the admin plane enabled the process fails to start with
# "Address already in use". Move it rather than moving SERVER_PORT, so the
# nginx config in this example keeps working.
ADMIN_BIND=127.0.0.1:8091
# REQUIRED: replace with YOUR real https domain. The your-domain.example placeholder
# is rejected at boot in production (Nostr identity is on by default).
PUBLIC_API_URL=https://api.your-domain.example/api/v1
+5
View File
@@ -9,6 +9,11 @@
SERVER_HOST=127.0.0.1
SERVER_PORT=8081
# ADMIN_BIND defaults to 127.0.0.1:8081, which is the SAME port as SERVER_PORT
# above. With the admin plane enabled the process fails to start with
# "Address already in use". Move it rather than moving SERVER_PORT, so the
# nginx config in this example keeps working.
ADMIN_BIND=127.0.0.1:8091
# REQUIRED: replace with YOUR real https domain. The your-domain.example placeholder
# is rejected at boot in production (Nostr identity is on by default).
PUBLIC_API_URL=https://api.your-domain.example/api/v1