ottobonn / dsm-containers Goto Github PK

Hello!

First of all, thank you very much for this really instructive overview and sample configuration.

Especially with Synology NAS I see the following problem:

What if I not only want to use NPM to reach other Docker containers in the same macvlan, but also Synology DSM apps outside the macvlan network?

NPM is located in the macvlan (because NPM listens on Port 80/443 and would be otherwise in conflict with Synology DSM at this point), which means that destinations outside the macvlan cannot be reached by NPM by default. This is not a problem for Docker containers, as these can also be created to run in the same macvlan network. So we can use NPM for all Docker containers.

The problem starts when the NPM is supposed to point also to synology services such as the DSM web interface or the MailPlus-GUI. Because DSM runs outside the macvlan and have his own reverse proxy ...

Example:
NPM IP: 192.168.0.201 (macvlan)
NAS (DSM) IP: 192.168.0.100 (non virtual network)

So the setup for a proxy host in NPM-GUI:
dsm-gui.domain.com --> Destination: 192.168.0.100:[DSM-Port]
ends in a 502-Error (Bad Request).

Is it possible to set a custom nginx configuration with your example network configuration or are modifications to your network configuration necessary in this case?

Thank you and best regards!

Chris