It looks like the issue was fixed with this release: https://forum.cloudron.io/post/70524
@nebulon You can mark this thread as solved. Thank you!

@girish

I got the same unsigned message, but I'm not sure if this is because I initiate this via my own adguard site by changing the hostname 🙂

I do however got some other info via https://github.com/paulmillr/encrypted-dns#signed-profiles

I think it is working now. Thread can be closed (I tried myself but didn't find the option)

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

@imc67 Thanks, I hadn't even thought of that. It was set to 90 days (which I don't need anyway...)

@lukas you may have a look at the guide from Cloudron here: https://docs.cloudron.io/apps/adguard-home/#security

However the setup is pretty simple, go to the DNS Settings in Adguard Home and give some names for your client IDs IMG_0209.jpeg

When you entered ClientIDs the DNS will not be available anymore for anyone who is NOT in your Client IDs list. If you want to update your non static IP from your internet service provider, you could do that and put in your public IP. In that case your local clients can use the DNS even without having a named Client ID

Then you can use the Tab "Setup Guide" in Adguard Home to get guidance how to get your devices configured.

If you want to configure Chrome, Brave or Firefox for DoH you can then use the URL to your Adguard Home DNS Name with appending your ClientId like this for example:
https://DNS-NAME-TO-YOUR-ADGUARDHOME/dns-query/CLIENTID

Please be aware that you should understand what you do and in case of concerns just don't do it. You will be responsible yourself for anything you do.

@imc67 Thanks. I just ran the update. Hopefully, this will fix it 🙂

@girish thanks. Yes, it was actually easier than my mind made it out to be! I just opened the ports I needed and set 53 only for the networks I wanted.

@khadanja Indeed, OpenVPN uses a custom port and does not run over http(s)

@ClaudiuCitar Once you have adguard installed, just use the public IP of your VPS as the DNS server on your devices.

@lcd_official thanks for the kind words 🙂

@ApplegateR sorry for late update. After reinstall it fixed and dns are back working again

This was sorted out in support.

@necrevistonnezr Yes, that should be enough. You can verify if this is the case by trying out host www.cloudron.io <public-ip-of-your-cloudron-server>. It should timeout.

As for IPv6, from a quick look at the code, it looks like we only bind port 53 to the server's IPv4 addresses. Let me check and get back tomorrow.

@atridad Awesome! Thanks...

@girish I know I seen it somewhere about the quotes and I did try it but it also did not work.
Maybe I missed something but will keep that in mind.