Synology Reverse Proxy to homer container port 443

Currently reading
Synology Reverse Proxy to homer container port 443

2
0
NAS
DS920+
Operating system
  1. Linux
  2. macOS
  3. Windows
Mobile operating system
  1. Android
  2. iOS
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?

Reserve proxy rules example.jpg


certs example.jpg
 

Attachments

  • reverse proxy example.jpg
    reverse proxy example.jpg
    88.7 KB · Views: 30
I gave up trying, and ended up moving all my containers away from Synology to a Pi. When it comes to dealing with ports 80 and 443, Synology sucks. And using this
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
to free those ports, is not an option as it will break other cool features in DSM such as Synology Drive Server and Active Backup for Business
 
For some reason, Synology is conflicting with ports 80 and 443.
Officially synology's nginx (reverse proxy) uses port 80/443 and those are reserved.

Trying to free them is not recommended and the update will reset that and you are at the mercy of Synology that can change any element at any point.

Using any other reverse proxy would be recommended and you can in facet host it on the NAS on custom ports, while pushing 443 traffic from your router to that custom reverse proxy (on custom, non-443/80 ports).

Basically what you did by moving that task on a separate device.

This is how I have it configured on the NAS, bypassing the built-in default ports and still getting 443 access for all services.

 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Old thread notice: There have been no replies in this thread for quite some time. The last reply was on .
The content in this thread may no longer be relevant. It might be better to open a new thread instead.

Similar threads

  • Question
That is correct. I can continue to connect to devices on my LAN. But opening a website for example just...
Replies
2
Views
1,463
Replies
11
Views
3,373
  • Question
I'm having the same issue. I can't add the public IP in the FW access list because for the NAS I'm...
Replies
18
Views
6,002
right , so I would assume even though there is no certificate applied on the certificate option, it...
Replies
3
Views
8,808
The difference is that the surface pro X uses an ARM processor. It uses a 32bit emulator for x32 apps
Replies
3
Views
3,146

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top