Hello,
I am unable to get a fresh EasyPanel installation to work behind the Traefik proxy. The service consistently binds to 127.0.0.1 instead of 0.0.0.0, resulting in a "502 Bad Gateway" error.
Environment:
- Provider: LWS
- OS Tested: Ubuntu 24.04 LTS and Ubuntu 22.04 LTS (fresh installs on both)
- Docker: Installed via the official Docker repository.
Problem:
The easypanel service log always shows: Server listening at http://127.0.0.1:3000
Troubleshooting steps taken:
- Configuring
/etc/easypanel/variables.env with EASYPANEL_URL=https://mydomain.com before running the install.sh script. The variable is ignored.
- Manually creating the service with
docker service create and injecting environment variables (EASYPANEL_URL and HOST=0.0.0.0). The service still binds to 127.0.0.1.
- Manually adding Traefik labels to the service.
It seems the application is hardcoded or has a behavior that forces it to listen on localhost, ignoring all standard configuration methods in my VPS environment. This makes it impossible for the Traefik container to reach it.
Could you please advise on what might be causing this behavior?
Thank you.
Hello,
I am unable to get a fresh EasyPanel installation to work behind the Traefik proxy. The service consistently binds to 127.0.0.1 instead of 0.0.0.0, resulting in a "502 Bad Gateway" error.
Environment:
Problem:
The
easypanelservice log always shows:Server listening at http://127.0.0.1:3000Troubleshooting steps taken:
/etc/easypanel/variables.envwithEASYPANEL_URL=https://mydomain.combefore running theinstall.shscript. The variable is ignored.docker service createand injecting environment variables (EASYPANEL_URLandHOST=0.0.0.0). The service still binds to 127.0.0.1.It seems the application is hardcoded or has a behavior that forces it to listen on localhost, ignoring all standard configuration methods in my VPS environment. This makes it impossible for the Traefik container to reach it.
Could you please advise on what might be causing this behavior?
Thank you.