A Clean Workaround When Port 443 Is Blocked for Synology Access

2026-11-19 11:44≈ 1471Words≈ 7Minutes

Previously, to get around blocked 443, I had no choice but to use special ports to reach Synology services at home—photos, Docker apps, and the like. To keep domains pointing at the right IP I synced via DDNS, but there was a catch: when someone pinged the domain they could still see the real IP. Router and Synology firewalls were already tightened as much as I could.

Disable admin and administration, unmap ports 5001 and 5000, change those port numbers, stay on the latest system version, and set three firewall rules: first, LAN wide open; second, only the ports you need exposed externally; third, block everything else.

With that setup, the October ransomware wave didn’t touch me—I didn’t even see scans. Still, I felt I had too many ports open, so this time I planned to shrink down to two: 6690 for Drive sync (I’m not commuting to the office lately, so Drive is still on the NAS but not port-forwarded; I’ll deal with it when I need it again), and the other one was 443.

1. The Access Layout I Wanted

Target outcome:

  1. On LAN or WAN, each service is reached by its domain only—no port in the URL.
  2. Synology’s three apps—Photos, File, and Drive—only need the domain configured; no switching profiles to enjoy home and away.
  3. At home, traffic stays on the LAN for full speed without changing domains or IPs.

Worth noting: the ISP long ago blocked 443 and 80. So why keep 443 open at all? Mostly for the internal network. The goal either way is: type the domain, no extra port—LAN speed at home, same hostname and no port juggling when you’re out.

The plan: use Cloudflare’s supported HTTPS port 2096 on the outside, forward only that one port on the router to Synology, and let Synology’s reverse proxy split traffic by hostname.

The chain:

 1Browser on the internet
 2    │  HTTPS 443
 3    ▼
 4Cloudflare DNS (orange cloud / proxied)
 5    │  HTTPS 2096
 6    ▼
 7Home public IP (blocked 443; traffic enters on 2096)
 8    │
 9    ▼
10Router port forward
11    │  WAN TCP 2096
12    │  → 192.168.X.X:443     <---- LAN browser HTTPS 443
13    ▼
14Synology NAS (192.168.X.X)
15    │
16    ▼
17Synology reverse proxy
18    │
19    ├── By domain + 443 → Photos, e.g. 1201
20    ├── By domain + 443 → Drive, e.g. 1202
21    ├── By domain + 443 → File Station, e.g. 1203
22    └── By domain + 443 → other internal services

2. Why 2096

Orange-cloud proxying doesn’t accept arbitrary ports. Supported HTTPS ports include 443, 2053, 2083, 2087, 2096, 8443, and others. DDNS and orange cloud can coexist—pingers see a Cloudflare IP, while Cloudflare still reaches your real origin when someone visits. That’s the whole point of turning the cloud orange.

I didn’t trust 8443 either; the ISP might block it tomorrow. I picked 2096 because:

  • It’s on Cloudflare’s HTTPS proxy list;
  • It works as a single external HTTPS entry;
  • I didn’t have to renumber every internal port for Photos, Drive, and File Station.

Note: this is the port the client uses toward Cloudflare. You also need Cloudflare Origin Rules to rewrite the origin port, with match conditions and target ports aligned—DNS or the router alone isn’t enough.

3. Cloudflare: Orange Cloud and Port Rules

1. Enable the orange cloud on DNS

Turn on proxy (orange cloud) for the relevant records.

After that, lookups return Cloudflare anycast IPs, not your home WAN address.

Traffic hits Cloudflare first instead of dialing your household IP directly.

Tip: update DDNS for only one hostname and CNAME everything else to it—that way you aren’t hammering the API every time your public IP changes.

2. Origin Rules and ports

The easy place to get confused: the port users hit and the port Cloudflare uses on the origin are not the same thing.

If you design it so external HTTPS 443 hits Cloudflare and Origin Rules rewrite the origin port to 2096, the rule should match the right hostnames and set the destination port to 2096—match rule, hostname, rewrite target port to 2096. You don’t spell out 443 in the rule: with https:// in the browser, the default is 443, which is how you avoid typing a port.

image-20261119113139065

4. Router: One External Forward Only

On the router:

1Protocol: TCP
2External port: 2096
3Internal IP: 192.168.X.X
4Internal port: 443

In short:

1WAN TCP 2096  →  192.168.X.X TCP 443

1201, 1202, and 1203 for Photos, Drive, and File Station are no longer WAN entry points.

One hole from the internet; Synology’s reverse proxy does the rest.

The port you forward to on Synology must match what Synology actually listens on. Don’t tweak only Cloudflare and forget the router, and don’t forward to 443 if reverse proxy isn’t on 443. That’s how 2096 slips past the ISP-blocked 443 into the NAS.

5. Router: LAN Hosts for Every Device at Home

Skip this and “accessing your NAS at home” means hairpinning through orange cloud and back—you’ve wasted the whole setup. This step is mandatory: on the router, add static hosts entries pointing every service hostname at the NAS LAN IP.

You can do it on a PC, but phones, a Xiaomi box, random other gear—do it on the router.

6. Synology: Reverse Proxy by Hostname

Reverse proxy is the heart of this setup.

Everything arrives on 443, but different hostnames let Synology route by Host to the right backend.

For example:

1photo.example.com  ──┐
2drive.example.com  ──┼── HTTPS 443 → Synology reverse proxy
3file.example.com   ──┘                    │
4                                         ├── Photos internal port
5                                         ├── Drive internal port
6                                         └── File Station internal port

One external port doesn’t mean one service. The domain tells them apart, not the port.

Per rule, check:

  • Source protocol HTTPS;
  • Source port unified entry 443;
  • Source hostname matches the service;
  • Destination host/port correct;
  • Certificate matches the hostname.

If the ISP weren’t so awkward—well, it’s not entirely “their fault,” but… if 443 weren’t banned, none of this orange-cloud rule juggling would be necessary.

7. Real Pitfalls: Synology Firewall and “Local Network” on the Client

Pitfall 1: Synology firewall didn’t allow the new 2096 path

Outbound failed at first. The firewall still showed 5005, 1201, 1202, 1203—it didn’t mean 2096 (or the new path) was allowed.

Router forward succeeding ≠ Synology firewall allowing the connection.

After changing the entry port, check the router and:

Control Panel → Security → Firewall

Allow TCP 443 inbound on the right interface and source range.

Otherwise packets reach home and die on the NAS—timeouts or Cloudflare 522.

Control Panel → Security → Certificate

After changing reverse proxy targets, confirm the cert on each entry—not accidentally the Synology default.

Pitfall 2: LAN failures aren’t always DNS or reverse proxy

Weird symptom:

  • photo, drive, file all behaved the same;
  • WAN worked;
  • Browser on LAN OK, apps not;
  • Felt like everything was broken.

Easy to blame DNS, Cloudflare, reverse proxy, or port forwards.

It was Local Network permission: during an iPhone security pass I’d turned it off for those apps. Turn it back on and LAN worked.

On iPhone, check the app has Local Network access—not just router and NAS.

1Settings → Privacy & Security → Local Network

Find the app and enable it; paths vary slightly by iOS version.

WAN up, multiple LAN services down? Check client Local Network before ripping DNS or proxy config.

8. Where to Look When Something Breaks

The path is long—don’t change random knobs on “it doesn’t load.” Walk from edge to service.

Where to checkWhat to verify
Cloudflare DNSOrange cloud enabled
Cloudflare Origin RulesHostname match, origin port correct
Public entryUsing a Cloudflare-supported HTTPS port
RouterTCP 2096 → 192.168.X.X:443
Synology firewallTCP 443 inbound allowed
Synology reverse proxyListening on 443, Host rules correct
Internal servicesTarget host/port and service health
iPhone clientApp has Local Network permission

Testing tip: I had hosts overrides on the router; testing from a Mac is easily skewed by /etc/hosts or system proxy—don’t treat that as WAN truth.

Turn off Wi‑Fi on a phone and use cellular for a real external test.

9. Wrap-up

The core is straightforward:

  1. Orange cloud so visitors go through Cloudflare and don’t hit the home IP directly.
  2. HTTPS port 2096 (Cloudflare-supported) as the single external entry.
  3. OpenWrt: one forward, TCP 2096 → Synology 192.168.31.136:443.
  4. Reverse proxy splits by domain to internal ports.
  5. Origin Rules, router forward, and Synology listen port must line up.
  6. Synology firewall must allow the 443 entry.
  7. WAN fine, LAN weird—check iPhone Local Network on the apps.

I used to think one service, one port. With orange cloud, one external port, and reverse proxy, many services can share it.

Ports get traffic in; hostnames pick the service; reverse proxy delivers it.

The punchline this time: hours on DNS, ports, and firewalls—and the phone had Local Network switched off.