I have a minipc with proxmox on it. I have tried caddy in a lxc to set up DNS challenges to my owned domain and I set the url in my router to point to the IP (for example, proxmox.DOMAIN.com could be 192.168.10.22). The hope was to have everything local within my house and nothing needs the internet to be accessed. Some services I can host in proxmox NEED https to use, which I could not get working with my own certs or ones proxmox could make, thus Caddy. However, I get proxmox with a proper cert, but i cannot get any of the other services from proxmox working. If I were doing it all manually, I would expect DNS issues with the domain, but from what I understand, Caddy by default does wildcard domains which should mean that my services should work. but they do not. Networking is new to me so perhaps I am missing something obvious. Any guidance would be appreciated.

EDIT: You guys helped me find my issue! Turns out that I did everything right except for 1 simple step. Once I have everything set up, I have my router point the urls to the CADDY address, not the services address. For example, I had bookmarks.DOMAIN.com set in my router to point at the readeck lxc ip and it didn’t work. Changing that to the Caddy ip fixed it. So all my services would point to the same ip (caddy). I do not know how I never saw this in any of the tutorials/videos/guides I checked, but THANK YOU for pointing it out to me.
Now the only odd thing is why does the proxmox ip work fine without pointing to caddy? I will leave it as is, but its the odd one out :/

  • Spiffyman@slrpnk.netOPEnglish
    1·
    1 day ago

    I use porkbun and I do the DNS challenge. I know it succeeds because proxmox gets https perfectly fine. But none of my lxc containers get https after doing DNS challenges for them. Not sure what I am doing wrong since I clearly did it right at least once :/

    • moonshine69@lemmy.nzEnglish
      1·
      22 hours ago

      Nice, ok hmm… sounds like you are using the router for internal DNS, did you set all the services to point at caddy?

      Eg you could try a quick hack in hosts (assuming the caddy ip is 192.168.10.10)

      192.168.10.10 grafana.domain.example
192.168.10.10 prometheus.domain.example
192.168.10.10 jellyfin.domain.example

      And then navigate to one of the services over https

      Main thing is all your internal DNS records need to point at caddy, and then it forwards to the real container IP

      Not strictly required but could be worthwhile to get a dedicated internal dns server up… I use technitium, or there’s pi hole or a few other options …

      • Spiffyman@slrpnk.netOPEnglish
        1·
        18 hours ago

        like you are using the router for internal DNS, did you set all the services to point at caddy? That was the answer! I had it pointed to the services, but once I set them to point at Caddy, it all worked. I cannot believe it was such a simple fix and also that I never picked up on that in all the guides/tutorials/videos I watched about this. Thank you!