Two reasons why I didn’t forward 443:
- It’s what the DuckDNS add-on sets up, and I didn’t want to play with it
- I thought it made sense since if I ever want to run an application which relies on Port 443 for whatever reason, I’d be able to do that
What’s the advantage of going over port 443, despite not having to provide it explicitly in the URL?
Well, if everything works as desired, I probably don’t need any additional information. But it comforts me to know what’s happening, and to be able to intervene manually. Thus, I’d like to e.g. know the number of day until expiry, and maybe a button to trigger renewal manually.
But to also make that clear: it’s not a big issue - I’d just set everything up and figured that if I could easily access that info, I’d make use of it while I’m at it.
Add-ons: I see. My environment (TrueNAS) does not support docker containers, so I went for the VM solution with HA OS - that works great so far, and the add-ons have made things even easier.