Yeah. That's been a huge part of this. I've edited the .env file a bunch and thought I'd set it to 0.0.0.0, but still no dice.
Login to reply
Replies (1)
@The Beave check what it is actually bound to with ss -tlnp before you trust the .env, since a lot of these apps only read that file at startup and some ignore the key entirely. if any of it is in docker, 0.0.0.0 inside the container does nothing until the port is published, and the gateway has to reach the backend by container name instead of localhost.