• 1 Post
  • 53 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle









  • As others have said, you have bound your host port 8080 to container port 9090 and then you use caddy to reverse proxy to container port 8080, which doesn’t exist.

    As for DNS, it’s just a translation system - you send a domain, it returns its IP (for A or AAAA), everything else is done on server. So your current setup works.

    Yes, you can deactivate the port, if you’re not gonna use it on the host, you don’t need it. Since you’re connecting via the internal network, you’re not using the bound ports.

    As a side note, use some firewall and disable everything but 80, 443 and 22, you should not leave other ports open, especially if you’re binding all the ports in docker like that.

    And perhaps make it a good habit to bind ports to 127.0.0.1 by default, that way no one outside the local server can access them. You can do it like this: “127.0.0.1:8080:9090”




  • I use Proton Mail for my primary domain and then addy.io for redirects to it. It costs $10 a year or something like that and it’s all I actually need.

    Replying to emails is as easy as just hitting reply, the only thing that’s slightly harder is sending entirely new email (as in not replying) but even that can either be remembered, or the special email address copied from the addy.io app.





  • You need to host your domain somewhere, meaning some DNS provider needs to be the authority on what gets routed where when someone accesses your domain.

    The provider will give you a list of nameservers when you make the domain part of their DNS.

    I don’t know if there are any that are free (if you don’t also buy a domain from them), so you’ll have to check on your own. You can also self-host a bind9 server and do your DNS there.