@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.

Replies (1)

It's running in a Debian LXC on my proxmox host. It sure doesn't seem to be paying attention to changes in the env file, but... I'm suspecting that there's another env file that I'm not aware of that is actually being read. The frustrating thing is that one not heard a peep of install issues from anyone else, even poking around for days. Being ahead of curve sucks sometimes. I'm not knowledgeable enough to be doing any of this as a pioneer. 🤣