Trying to get https working

Synology
1

Hello everyone, I am stuck and been stuck for a very long time.

Trying to get audio server working where I can access it remotely and through some apps. I managed to get it to work where I can access it through unsecured connection only, which makes me think I have issues with letsencrypt certificate.

Here is address to the audio server i am working on

http://pzserver.synology.me:4533

I used google to check that my ports 80, 443, and 4533 are open.

Can you guide me and tell me what else I can do? Thank you!

2

If this subdomain is specifically for your audio server, you should use the reverse proxy feature.

First forward 443 (external) to 443 (NAS IP)

Create a reverse proxy entry:

1193Ă—1120 58.9 KB

Presuming that your certs are properly set, you would enter “https://pzserver.synology.me” to access the server externally.

Be sure to try that on a cell phone, and not from your LAN.

3

Thanks so much for all that information! I’ll give it a try. One question, “First forward 443 (external) to 443 (NAS IP)” - you mean port forwarding or that is something else? Am I doing it at router?

4

Yes. If your connecting remotely by your domain name, your router must pass that traffic to the NAS.

5

I googled and confirmed my port 443 is open, so I guess that part should be good.

I played too much with certificates yesterday and I am unable to create new certificates on lets encrypt for 7 days. I’ll have to wait to know if it will work.

But now when I go pzserver.synology.me, it goes straight to the music server, just unsecured. I’ll let you know if it will work in a week. Thanks so much for your help!

7

Hello, finally I was allowed to create lets encrypt certificate. Now, when I type pzserver. synology. me, it goes to port 5000, but does not get to destination. When I type same address with port 4533, it says connection not secured. I took couple screenshots of my settings, please let me know if I did something wrong.

Screenshot 2026-02-06 at 10.37.43 PM
Screenshot 2026-02-06 at 10.37.43 PM1182Ă—848 51.6 KB

8

Screenshot 2026-02-06 at 10.37.03 PM
Screenshot 2026-02-06 at 10.37.03 PM1070Ă—576 25.8 KB

9

Screenshot 2026-02-06 at 10.36.33 PM
Screenshot 2026-02-06 at 10.36.33 PM1170Ă—1108 52.3 KB

11

Test it from a true data connection (not LAN)… for example a cell phone. Looks fine here:

554Ă—133 10.7 KB

1 Like
12

Staying on LAN definitely had me super confused. I also confirmed everything works. I really appreciate your help, thank you very much!

13

Hello all. Everything worked great all the time, but yesterday I noticed that connection stopped working. I did not change anything on synology. I noticed that lets encrypt certificate was to expire next month, so I renewed it, but still. I can not connect to my music server using pzserver synology me. I can connect to it however just by opening it from package center inside synology.

14

I might be onto something here, is it possible that with new ISP, my ports were closed? I am checking on google and it says 80, 443, and 4533 are closed

Just checked my router and all is good in settings. I wonder if Fiber modem has some settings inside and has ports closed, but its just a modem.

15

Did router change? If so, you’ll need to set up port-forwarding again.

Also check your WAN IP to ensure it is not “CGNAT” (If your IP begins with “100.”, it’s likely CGNAT). If so, contact you ISP and ask if you can be given a non-CGNAT IP (dynamic IP or fixed IP).

16

Just checked, checking whats my ip on google starts with 140 or something, but in router settings, IP first digits are 100. I guess it is CGNAT. I have fiber service provided stop by tomorrow, not sure why they decided to send a tech, but now I know more as to what to tell them. Thank you!