Good day, So I have a Synology NAS hosting a Homer container on port 3030.
Using pfSense DNS resolver, I am accessing homer as http://homer.domian.local
I want to access homer (and other local applications) with an SSL certificate.
In psSense I created root and intermediate CA, imported those to my test VMs, and added server certs as custom in NPM hosted on a PI. It works for all apps hosted in PI or other Linux servers, except for Synology's hosted containers or plex app.
For some reason, Synology is conflicting with ports 80 and 443.
I tried to use embedded Synology reverse proxy but it ends up erroring: "Synology, Sorry, the page you are looking for is not found."
Is there a way to redirect Synology's ports 80 and 443 to 3030 internally, without causing conflict with other services that Synology runs by default on those ports?
Using pfSense DNS resolver, I am accessing homer as http://homer.domian.local
I want to access homer (and other local applications) with an SSL certificate.
In psSense I created root and intermediate CA, imported those to my test VMs, and added server certs as custom in NPM hosted on a PI. It works for all apps hosted in PI or other Linux servers, except for Synology's hosted containers or plex app.
For some reason, Synology is conflicting with ports 80 and 443.
I tried to use embedded Synology reverse proxy but it ends up erroring: "Synology, Sorry, the page you are looking for is not found."
Is there a way to redirect Synology's ports 80 and 443 to 3030 internally, without causing conflict with other services that Synology runs by default on those ports?