AdGuard Home Wildcard aliases

[girish]

@lukas If you go to Location view and click Save (without making any changes), does that help the situation ? That should maybe (re)trigger getting the cert.

[lukas]

@girish did not help. This looks also not fine:

Certificate chain is invalid

[girish]

@lukas can you check the output of openssl x509 -text -in /etc/certs/_.adguard.domain.cert in the web terminal of adguard ? Does it seem like a valid Let's Encrypt certificate?

[lukas]

@girish I see an output. Which part do you need from this ouput?

[girish]

@lukas The first few lines should give us the issuer and expiry like this:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            04:1d:71:e7:48:c7:d3:80:02:ac:c1:ac:5b:79:e5:3f:3e:4e
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C = US, O = Let's Encrypt, CN = R3
        Validity
            Not Before: Apr 15 02:11:00 2023 GMT
            Not After : Jul 14 02:10:59 2023 GMT

Then later down, you should also see the SAN section:

            X509v3 Subject Alternative Name: 
                DNS:*.girish.in

Ideally, there should the wildcard and non-wildcard DNS listed above in your case.

[lukas]

@girish

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            36:5d:97:51:3d:9f:45:89:58:45:67:c2:82:a6:83:3f:6d:50:69:0b
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN = *.mydomain.cloud
        Validity
            Not Before: Apr  2 14:06:15 2023 GMT
            Not After : Jun 10 14:06:15 2025 GMT

and

			        X509v3 extensions:
            X509v3 Subject Alternative Name: 
                DNS:mydomain.cloud, DNS:*.mydomain.cloud

[girish]

@lukas It's not getting the new certs for some reason - it's using the self-signed cert. If you go to Domains -> Renew all certs. Can you check the logs when it's renewing? Do you see any errors?

[lukas]

@girish I sent you the log-file via E-Mail

[girish]

@lukas From the logs, it seems the domain is not using Wildcard certs at all. If you go to Domains -> Edit -> Advanced. What is the certificate provider ? I suspect it's not wildcard . Can you change it and try to renew certs again?

I guess the reason is because you went from maybe Wildcard DNS to Programmatic DNS. In wildcard DNS, wildcard cert is not possible. But this is indeed a workflow/ui thing, that we have to consider in the future.

[girish]

The certificate provider should be Let's Encrypt Prod - Wildcard

[lukas]

@girish this is set and I haven't change it. Just today changed the DNS Provider from Wildcard to Bunny

[lukas]

@girish so which steps do I need to go, to get this resolved?

Btw. I see there some "non-used" SSL certificates, is there any kind of "housekeeping" ?

[girish]

@lukas I am a bit lost at this point. Are you able contact me at support@cloudron.io , so I can debug your instance?

[lukas]

@girish sure, I give you access. I open a Ticket via Cloudron

[girish]

@lukas thanks! As a heads up, I will only be able to debug a bit later today.

[lukas]

@girish said in AdGuard Home Wildcard aliases:

@lukas thanks! As a heads up, I will only be able to debug a bit later today.

all right, thank you very much for your amazing support!

[girish]

@lukas Thanks for the access. I found the root cause. I (re)learnt about Let's Encrypts validation cache.

<tech stuff>

It's a very corner case but, unfortunately, it's hit in your situation.

• You used to have wildcard DNS before. This results in Let's Encrypt HTTP validation (http-01)
• You switched to Bunny DNS. The code now expects to do Let's Encrypt DNS validation (dns-01)
• Turns out , Let's Encrypt will "remember" authorization for 60 days (in some places, it says 30 days). So, it will continue to ask for HTTP validation . The code gets confused because is really wants DNS validation.

If you want to read more:

• https://community.letsencrypt.org/t/flush-of-authorization-cache/188043
• https://community.letsencrypt.org/t/let-s-encrypt-s-vulnerability-as-a-feature-authz-reuse-and-eternal-account-key/21687
• https://community.letsencrypt.org/t/http-01-validation-cache/22529

</tech stuff>

I fixed our code to handle this - https://git.cloudron.io/cloudron/box/-/commit/15e0f11bb9815f5e4e7637cf29cf4fd17ccd2da2 . I applied the fix on your server and it seems to work. Atleast, the certs are correct now and we can now go back to checking if AdGuard is working for you. Can you check?

[lukas]

@girish it works great now, can't thank you enough for your constant and professional support! Very happy to use Cloudron guys

[ByMynix]

Hey @girish,

I have the same problem now. I was a bit too stupid and first created a manual record in Porkbun which is logically not necessary and does not work. I have subsequently deleted this entry again. I tried via Cloudron (with Lets Encrypt Prod/ Wildcard and Porkbun DNS) to set an alias entry for AdGuard (*.adguard.mydomain.com). However, I get this error message:

GET /api/v1/domains/my.domain/dns_check?subdomain=*.adguard 424 Failed Dependency Porkbun DNS error 400 {} 770.306 ms - 76

I ran the DNS sync function in Cloudron, as well as renewed the certificates. However, nothing has helped

[girish]

@ByMynix Porkbun support never got back to us and we gave up trying after reminding them 2-3 times. Their API is broken wrt wildcards (well, atleast it's undocumented). I recommend using some other DNS provider if you want this feature.