Split-Pro docker with Traefik reverse proxy - network interface configuration

[soeffi]

All,

I set up split-pro in a docker compose environment which works fine locally. I'm having trouble setting up Traefik, though.

My setup is based on the Docker example file, adding an additional network just for traefik. So one network for communication with the database, and another network for traefik (see below).

Judging from the output, it seems that split pro (server.js) is listening only on one interface, which happens not to be the one used for traefik, rendering split-pro inaccessible via the proxy.

Any hints how to make split-pro listen on all network interfaces? I don't see a way to change the order of interfaces within docker, unfortunately...

[krokosik]

You can set the env var HOSTNAME=0.0.0.0

[soeffi]

Works perfectly, thanks for the quick reply!

Did I miss that point somewhere in the docs? Or should this maybe even be added to the env.example file and docker compose?

[krokosik]

It's a typical Traefik issue, I never needed that with my nginx setup, but a PR with better docs is always welcome.

[soeffi]

Ok, found some more docs on this:

• By default, Next.js listens on localhost:3000 only
• Adding HOSTNAME=0.0.0.0 makes Next.js listen on all network interfaces

This is what I needed in my configuration.

I just saw that you added that to compose.yml already. Would it be more clear to replace the corresponding comment by something like follows?

# Uncomment this, to have the server listen on all network interfaces. Needed when you want to connect to split-pro via docker internal networks, e.g. for reverse proxy setups.

[krokosik]

Sure, can you send a PR?