Comment on A/MX records tutorial

runaway@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

• TheOldRepublic@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Lots of servers running. Main System is proxmox. I have an Ubuntu server running on that with docker installed which runs about everything (pi-hole, nginx, jellyfin, radarr, sonarr, (even) Firefox, and more). So end goal would be to go to www.mydomain.com/pihole to access pihole, to www.mydomain.com/jellyfin to go to jellyfin and so on.

  source

  • Amcro@lemm.ee ⁨1⁩ ⁨year⁩ ago

    I’d recommend running pihole.yourdomain.com or jellyfin.yourdomain.com instead. I think using yourdomain.com/service might cause you some problems, that’s why i heard other recommend use subdomains instead.

    source
  • runaway@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

    What I’d personally recommend is Cloudflare Tunnels, it allows you to lock down access to your services with an emailed code or other authentication method, as well as avoiding having ports forwarded to your services. It’s an easy way to avoid port forwarding and not have to worry about whether all the services you’re hosting are 100% secure, since you’ll be exposing them to the internet.

    The downside is you’re routing all your traffic through Cloudflare.

    source

    • TheOldRepublic@lemmy.world ⁨1⁩ ⁨year⁩ ago

      I discovered this one too. Don’t care about the downside as long as it works and is easy a ough to do…And it is, worked right out of the box. The only problem I have now is that my website (hosted on the servers of a domain provider) is not accessible anymore. Tried to redirect to the correct ip, but it’s not working. I have an nginx server too but for some reason that ip is also unavailable, while the one from my jellyfin (which is on the same proxmox) is 🤔

      source