- 228
- 91
- NAS
- DS1621+, DS1522+, DS720+
- Router
- MR2200ac
- RT6600ax
- WRX560
- Operating system
- Linux
- macOS
- Windows
- other
- Mobile operating system
- iOS
Last edited:
I've setup VPN Plus on my RT2600ac using the Synology SSL VPN. This enables the URL https://<hostname>.synology.me:443/ for VPN Plus, which is viewable on the local subnet, but not remotely - it just refuses to display in the browser.
Firewall rules for VPN Plus are enabled in SRM, and a port scan on both the internal LAN IP and the external WAN IP shows that 443 is open. I can remotely connect to SRM on https://<hostname>.synology.me:8001 so I know DDNS resolution is good, and the LE certificates also appear fine. At this point, I'm out of ideas, or probably overlooking something obvious. I've gone through the Synology tutorial for the setup, so I'm at a loss to figure this one out.
Alternately, can anyone recommend a better option for a Mac to SRM VPN config? I'd prefer one that can use built-in VPN client (I guess that means L2TP), though if there's a better way, I'm open to alternatives (openVPN?). By 'better', I mean something that is more secure whilst still being fairly light on the client side.
The use case is a single user (me) having the ability to remote-in to fix other computers on the network, whilst travelling for work.
Firewall rules for VPN Plus are enabled in SRM, and a port scan on both the internal LAN IP and the external WAN IP shows that 443 is open. I can remotely connect to SRM on https://<hostname>.synology.me:8001 so I know DDNS resolution is good, and the LE certificates also appear fine. At this point, I'm out of ideas, or probably overlooking something obvious. I've gone through the Synology tutorial for the setup, so I'm at a loss to figure this one out.
Alternately, can anyone recommend a better option for a Mac to SRM VPN config? I'd prefer one that can use built-in VPN client (I guess that means L2TP), though if there's a better way, I'm open to alternatives (openVPN?). By 'better', I mean something that is more secure whilst still being fairly light on the client side.
The use case is a single user (me) having the ability to remote-in to fix other computers on the network, whilst travelling for work.