-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AdGuardHome installation failed #5
Comments
AdguardTeam/AdGuardHome#2536 (comment) I'm already working on it. Will release a new plugin when finished |
the panel with port 3000 does not open, any additional configuration? |
It doesnt even start .. I'll rework the while package |
in service status if active |
Ok, I have read that. So now I see AdGuardHome is installed in /usr/local/AdGuardHome. Why is the file /usr/local/etc/rc.d/AdGuardHome pointing to /usr/local/opnsense/service/AdGuardHome? Because I moved the binary "AdGuardHome" to this location it is working fine now! |
I finally got AdGuardHome working as an @opnsense plugin. Grab it from here: https://www.routerperformance.net/opnsense-repo/ It's still lacking status view, but after install and enabling it's available via port 3000 (if no other service listens to it). If you had a previous version better remove it via CLI (pkg and plugin), but then also config is wiped. |
Thank you. I copied my settings and data folder to the new location. All good! |
I installed your OPNsense repository and tried to install AdGuardHome.
The plugin is installed but the package apparently not. It is missing, although I can see it in the packages list on OPNsense.
I really don't know what went wrong, but I fetched the FreeBSD 64bit package from Adguard, extracted it and copied the binary to /usr/local/opnsense/service/ directory.
Then I was able to login on port 3000 and it is working fine now. I disabled Unbound/dnscrypt-proxy because AdGuardHome has the same/more functionality and a nice interface.
Thanks for your repository. I hope you can find the problem with installation.
The text was updated successfully, but these errors were encountered: