2.12.3 node not start

chrome login 502 gateway error:

fallback_error.log have error:
2025/12/25 02:10:45 [error] 188#188: *8433 connect() failed (111: Connection refused) while connecting to upstream, client: 172.16.9.100, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "10.0.1.248:8181", referrer: "http://10.0.1.248:8181/login"

docker exec -it nginx-proxy-manager-app-1 netstat -ntpl

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 160/nginx: master p
tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 160/nginx: master p
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 160/nginx: master p
tcp 0 0 127.0.0.11:41727 0.0.0.0:* LISTEN -
tcp6 0 0 :::443 :::* LISTEN 160/nginx: master p
tcp6 0 0 :::81 :::* LISTEN 160/nginx: master p
tcp6 0 0 :::80 :::* LISTEN 160/nginx: master p

have not 3000 port listen about node service

Start with fallback_error.log and the docker exec netstat output, then inspect how the 2.12.3 container starts its node service and exposes port 3000. Confirm the cause of the refused upstream connection and verify that the service listens on port 3000 and Chrome login no longer returns a 502.