Nevermind, I did a new install, set up everything from scratch and all is good. Maybe it was some weird setting I had done, who knows…

@Jenova Oh, you mean the "Allowed clients" inside AdGuard Home ? If you use port 853 , then you are connecting directly to AdGuard and IP should be client IP.

@girish okay, will do. thank you.

Was someone able to resolve this?
The profiles are unsigned for me, too, which would require manual re-deploying (and remembering to do so!) a profile after 90 days…

@necrevistonnezr Could be something changed in your ISP regarding IPv6 rotation. But @nebulon and I see this pretty consistently in our home servers (in Berlin, where they seem to rotate IPv6 for some reason).

@ByMynix if you want to stick with Porkbun please email them and link https://forum.cloudron.io/post/64902 as the post reproducing the issue. You can also cc support@cloudron.io and we are happy to respond.

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!

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

@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.