Hi Guys,
first I want to say Hi to all, as I am new to this forum.
I stumbled across dietpi as I’m seraching for a lightweight raspi OS that suits for my purpose.
My plan is to run AdguardHome and Nextcloud in one place. I found that dietPi-software offers both but I’m not sure how this will function.
Both applications need port 80 for their webinterface. AdGuard let you change this port on the initial setup but will what about nextcloud?
There is my plan ^^
first install adguardhome and run the setup process to change the http port to idc… port 84
afterwards install nextcloud and let’S encrypt and run it on port 80.
Am I right? (can’t test it, as I only have one PI which I use with adguard atm)
Thank you in advance!
Hi,
you can check DietPi running on a VM to get a feeling on it 
On DietPi we aim to setup all software in a way to enable them working together. Therefore we configure AGH to use a different port on our standard setup. Both apps can be installed together in a single step. No need for any manual configuration needed.
I recommend to have a look to our online docs for further information https://dietpi.com/docs/software/dns_servers/#adguard-home
This is actually awesome! That might be the easiest way to get my setup running!!
I will test it as soon as possible.
I have to say Thank you! It works perfectly fine!
Just a short note, for noobs like me it would be nice if you implement DNSSEC activation into unbound installer. ( As it asks you if you want to install it - which is great!) and with the dashboard it is very easy to navigate to the config files!!
Usually DNSSEC is already activated on our default Unbound installation… This is how our configuration looks like
https://github.com/MichaIng/DietPi/blob/561f7a7724e51623742a016f12c03bef66c235f3/.conf/dps_182/unbound.conf#L70
Oh I see.
i checked the wrong .conf in /mnt/dietpi_userdata/adguardhome/dietpi-unbound.conf as you are referred there from within the adguard home interface.
/mnt/dietpi_userdata/adguardhome/dietpi-unbound.conf is just the configuration of AGH to use Unbound. It is not the configuration of Unbound itself as Unbound has it’s own config files.