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.

  • moonshine69@lemmy.nzEnglish
    2·
    3 days ago

    If you are doing a dns challenge then You need to give caddy access to your domain to perform the dns challenge. Depending on domain provider that is easy or hard. It will briefly change some records that tells let’s encrypt you own the domain and then issue the cert

    Or you can do http challenge, this requires you to manually configure your domain to point to a publicly accessible caddy endpoint which is probably not what you want, maybe there is a way to make it work through a cloud flare tunnel

    Who is your domain provider?

    • Spiffyman@slrpnk.netOPEnglish
      1·
      9 hours 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·
        3 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 …