ok I just did that and my problem is that I wanted to access my services with a custom domain like .homes
Now I need to access them for x.y.duckdns.org
Comment on Finally got my server to work properly. (Routing with custom local domain instead of ports)
Lifebandit666@feddit.uk 2 months agoYou can get pretty cheap domain names if you google around. I managed to get mine for £35 for a number of years (3 I think, I was high when I set it up) and got a .com name out of that.
You could look into DuckDNS. I know I used them many moons ago for Home Assistant but can’t quite remember what the capabilities were, I just remember it was free and a bit rubbish. But as a stopgap it works.
Try that for a bit until you have a few quid spare, then get yourself a domain name paid for a while.
Mir@programming.dev 2 months ago
toffi@feddit.de 2 months ago
I used dynv6.com to get a free subdomain e. g. [name].dynv6.net and then a swag docker to do the reverse proxy subfolder->dockerport matching. Trafic in my home network is http and the swag ports are the only one exposed to the public. When I find the time I’ll do in depth setup guide including the ipv6 setup problems.
Mir@programming.dev 2 months ago
ok I just did that and my problem is that I wanted to access my services with a custom domain like .homes
Now I need to access them for x.y.duckdns.org
Lifebandit666@feddit.uk 2 months ago
Have a look into Heimdall or Homarr. Much easier, don’t need to worry about addresses at all. Single set up and add Tailscale exit node for external access.
Mir@programming.dev 2 months ago
Yea I’m using Homarr, I’ve just finished setting everything up. The only problem I have right now is that I can’t access Syncthing GUI through the domain.