System > Settings > Administration.The UI has the ability to change the port the GUI is listening on. Many of us change it from the default for a variety of reasons. No need to worry about changing it here, is not a hack, and it survives updates and upgrades.That said, in general, the advice is sound.
"Still cannot load into either of 192.168.1.1:80 or 192.168.1.1:3000 for AdGuardHome setup."
So now OPN GUI is listening on port 82 and AdGH on 80 it seems.Quote"Still cannot load into either of 192.168.1.1:80 or 192.168.1.1:3000 for AdGuardHome setup."What happens? Whether you can not reach it or you can but errors, different solutions.The AdGH config can be modified manually but it is no good if you can't reach it.Please tell where you are trying to reach it from, the same network, or a different one?I can't assume because of your previous setup with machines on different ports on the firewall.
p.s from your screenshot (re-added here for reference), the interface is called vtnet1. Is this a virtualised setup? If so, can you please provide the complete setup with all interfaces, assignments, etc. all is relevant.
$ sudo service adguardhome statusPassword:adguardhome is running as pid 31785.$ sudo ps -vvv 31785 PID STAT TIME SL RE PAGEIN VSZ RSS LIM TSIZ %CPU %MEM COMMAND31785 Is 0:00.09 75 127 0 12728 2260 - 12 0.0 0.0 daemon: /usr/local/AdGuardHome/AdGuardHome[31884] (daemon)$ sudo service adguardhome onerestartStopping adguardhome.Waiting for PIDS: 31785 done.Starting adguardhome.$ sudo service adguardhome onestatusadguardhome is running as pid 44395.
congratulations on building your next time sink For configuration - the site documentation https://github.com/AdguardTeam/AdguardHome/wiki/Getting-Started For which blocklists to use - there are many. I suggest to start with the Steven Black list https://github.com/StevenBlack/hostsBe ready to start allow-listing to fine tune to your requirements.