There’s always money in the banana stand
I’m running an old Igel M340C thin client to run a lot of stuff, from Jellyfin to AdguardHome. Perfectly enough.
I’m trying to get Dawarich up on my server via Docker. It runs via local IP, but when I access via domain.com:6001 (port I’ve set in docker-compose.yml), I get error stating this is not allowed host and I should add it via config.hosts << “domain.com:6001”
When I do add domain.com:6001 to APPLICATION_HOSTS in environment in docker-compose and create new containers with compose up -d, I still get error.
I’ve also tried this, but the port seems to throw it off and not including the port does the same.
I’m on supervised install on Ubuntu server. All worked fine for many years, except Supervisor being bitchy about me having Portainer installed for no reason. Last week or so, my machine started acting weird. After reboot I couldn’t access it via local ip, only via external hostname. What keeps happening is after reboot Supervisor creates new network config for my ethernet, that causes this. It uses the network-manager to do this. I have netplan doing the config. Nyone else?