Octoprint not accessible with local network IP

[nikil511]

works with balena public IP but not with local one.
I guess it has to do with traefik settings

[MatthewCroughan]

Yes, this is how it is currently configured. It only allows traffic in if the host: header is *.balena-devices.com OR *.local OR *.localdomain OR *.lan.

As can be seen in the traefik.http.routers.<entrypoint/frontend>.rule definitions

octobalena/docker-compose.yml

Line 20 in 0814bec

traefik.http.routers.octoprint-balena.rule: 'HostRegexp(`{subdomain:[a-zA-Z0-9\-]+}.balena-devices.com`)'

octobalena/docker-compose.yml

Line 24 in 0814bec

traefik.http.routers.octoprint.rule: 'HostRegexp(`{subdomain:[a-zA-Z0-9\-]+}.local`) || HostRegexp(`{subdomain:[a-zA-Z0-9\-]+}.localdomain`) || HostRegexp(`{subdomain:[a-zA-Z0-9\-]+}.lan`)'

octobalena/docker-compose.yml

Line 28 in 0814bec

traefik.http.routers.octoprint-insecure.rule: 'HostRegexp(`{subdomain:[a-zA-Z0-9\-]+}.local`) || HostRegexp(`{subdomain:[a-zA-Z0-9\-]+}.localdomain`) || HostRegexp(`{subdomain:[a-zA-Z0-9\-]+}.lan`)'

So, port 80/443 is owned by traefik. Traefik says you only get forwarded/proxied into the octoprint container on port 5000 IF those names match, if not then 404.

TL;DR

If you go to the IP address on port 5000 you will bypass Traefik and get directly through to Octoprint.

octobalena/docker-compose.yml

Lines 12 to 13 in 66436c1

	ports:
	- '5000:5000'