I found a really good video on YouTube, but, of course, they aren’t running on Synology and one of the first things they did was add the add-on DuckDNS.
So anyway, here is what I’ve accomplished (if I remember what I did since it is mostly all new):
- Set up ports 80 and 443 on the router letting them through to the Synology box
- Create a domain under DuckDNS.
- Created DDNS entry for DuckDNS using key token using Install instructions in DuckDNS.
- Tested that I could start HA on the port 8123 using the DuckDNS domain name that was created.
- Went to the Security|Certificate in Control Panel and managed to get an entry for my DuckDNS domain.
That entry looked a little odd, because unlike the Synology one that list
For: FTPS, Synology Storage Console Server, Synology Drive Server, Log Receiving, System, default
My entry just said For: -
Maybe that is all right, I don’t know. It DID say registered R3 which is the same thing the other Synology entries said for theirs. And mine said (RSA/ECC)
- Tried to create Reverse Proxy in Login Portal|Reverse Advanced, but got various errors when trying various things. Never able to access HA with https://domainname:8123 or 443.
If I tried 443 in the source port, it said port number had to between 1 and 65535. Odd message
When I tried 8123 in source port, it said domain name is already in use.
I tried putting an http section in configuration.yaml and it didn’t like that.
I feel like I’m close. Anybody got a clue?
Oh, I also exported all the pem files out of Synology, but don’t know how to tell HA to use them. (nor do I know which ones are for use with HA, if any)