I usually pay dyn.com for dynamic dns in order to access my home servers (webserver on ubuntu, home assistant, synology, etc...). I now register for my own domain name, say example.com, from namecheap, and want to stop using dyndns.biz. I don't know how I could achieve the same functionality after stopping the dyndns.
My use cases before having my own domain.
- http://xxx.dyndns.biz/weewx - to access my weather website hosted on my home server ip 192.x.x.14. The web content is in var/www/html/weewx folder
- http://xxx.dyndns.biz:4002 - to access my Calibre ebook hosted on my Synology NAS, local ip 192.x.x.4. I use port forwarding on my pfSense to point it to the right server/port
With my own domain name https://example.com (using let's encrypt ssl): a) I can access my weewx without problem by https://example.com/weewx. The website content is on my same home server, and in var/www/example.com/weewx folder. Apart from weewx folder, I also create other folders for other websites b) To access my Calibre server on my Synology, I don't know how to achieve it; because when I type https://example.com:4002, it won't connect to my Synology server. I understand that because https has to stick to port 443. Before I implement let's encrypt ssl, no problem with port forwarding.
FYI, my web server, 192.x.x.14, is running Ubuntu 18.04/Apache.
Thank you for any suggestion.