Messages

1

Documentation and Translation / Re: AdGuard Home setup guide

« on: March 25, 2024, 10:39:36 pm »

I didn't want to do it per client. I just want the service available to all clients during a specified time. However, I don't want to unblock all the other services.

Looks like that is not possible at the moment with AdGuard Home

2

Development and Code Review / Re: [v1.5.1_1] Caddy Reverse Proxy plugin with GUI

« on: March 24, 2024, 05:02:33 am »

I am happy to see this integrated into OpnSense as a plugin. I am currently using HAProxy plugin, but would like to move to this plugin and I have some questions.

• This seems to include DynDNS and Acme Certs. -- Does this mean that by using this plugin, I can get rid of the os-ddclient and the on-acme-client plugins altogether and simply set them up under this plugin?
• Currently for a few services like Omada, Nextcloud, I had to set up certain headers rules (http-request redirect, http-request header set, http-response replace-value etc etc) in HaProxy in order for it to work. How would the same headers be setup in this plugin?

3

Documentation and Translation / Re: AdGuard Home setup guide

« on: March 24, 2024, 04:55:42 am »

I have a question regarding the Blocked services.

I see that there is an option to pause the blocking. Can someone confirm if there's a way to pause blocking only for certain services instead of pausing the block for all services?

For eg. I just want to unblock YouTube from 6PM to 7AM on Weekdays and all day on Sat, Sun. I don't want to pause the blocking of any other services. Can this be achieved with the current Pause Blocking feature?

4

Development and Code Review / Re: Redundant domain override pages in Unbound?

« on: January 21, 2024, 08:08:16 pm »

I'll just add here that  -- as a user who doesn't fully grasp the DNS nitty gritties without reading 5-7 articles before fixing the DNS related issues that I have AND then promptly forgetting within a day or so -- it is definitely confusing to have 3 different places that can do similar things. Sometimes, users like me read something on the web, and put those settings in which might turn out to be in conflict with previous settings we might have done on the different pages and it's hard to relate those unless you know what's going on.

I would definitely recommend reducing the footprint of doing stuff to a single page and would also like to ask if there is further progress on this issue since it was last discussed?

5

General Discussion / Re: mimugmail repo Caddy plugin

« on: January 19, 2024, 11:41:58 pm »

Awesome, thanks.

6

General Discussion / mimugmail repo Caddy plugin

« on: January 19, 2024, 07:07:40 pm »

Hello,

I was wondering if the os-caddy-maxit plugin supports Cloudflare DNS challenges or would I have to re-compile caddy with the cloudflare dns myself?

I was planning on switching from the os-haproxy over to caddy.

7

23.7 Legacy Series / Re: AdGuardHome Web Interface on multiple addresses?

« on: August 21, 2023, 12:33:19 am »

I need to be able to access AdGuard Home from my main LAN but also from my VLAN when I connect via Wireguard in case there's something I need to do when on the road.

Is there a way to enable the web-interface from more than 1 interfaces without enabling it on all interfaces?

8

23.7 Legacy Series / Re: AdGuardHome Web Interface on multiple addresses?

« on: August 19, 2023, 05:31:57 pm »

Weirdly, when I remove 0.0.0.0 from the bind_hosts my OpnSense firmware updates start timing out. I can still access the internet just fine, but the Opnsense updates keep failing.

So should AdGuardHome be listening on ALL interfaces by default for dns: bind_hosts? Seems strange that only the OpnSense updates should fail while the internet is still accessible !!

9

23.7 Legacy Series / AdGuardHome Web Interface on multiple addresses?

« on: August 19, 2023, 05:09:37 pm »

Is there a way to allow the web interface for AdGuardHome to be available on multiple interfaces but not all ?

Initially, I set it up on ALL interfaces and the yaml file used 0.0.0.0.

Code: [Select]

http:
      address:0.0.0.0:8080

I have 5 separate VLANs and I have since changed the bind_hosts to stop listening on all interfaces and only enabled it on 4 of my VLANs. I would like to do the same to the web interface but I was looking to see what format I can use to do that

The following allows access on VLAN 1, but I would also like access on VLAN 7 and VLAN 10

Code: [Select]

http:
      address:192.168.1.1:8080

I tried the following three formats, but then AdguardHome failed to start up.

Code: [Select]

http:
      address:192.168.1.1:8080
      address:192.168.7.1:8080
      address:192.168.10.1:8080


Code: [Select]

http:
      address:192.168.1.1:8080, 192.168.7.1:8080, 192.168.10.1:8080


Code: [Select]

http:
      address:
            - 192.168.1.1:8080
            - 192.168.7.1:8080
            - 192.168.10.1:8080

None of the above format worked for me and googling doesn't provide relevant results and I was hoping if someone could tell me what format to use

10

Documentation and Translation / Re: AdGuard Home setup guide

« on: August 19, 2023, 05:05:07 pm »

Is there a way to allow the web interface for AdGuardHome to be available on multiple interfaces but not all ?

Initially, I set it up on ALL interfaces and the yaml file used 0.0.0.0.

Code: [Select]

http:
      address:0.0.0.0:8080

I have 5 separate VLANs and I have since changed the bind_hosts to stop listening on all interfaces and only enabled it on 4 of my VLANs. I would like to do the same to the web interface but I was looking to see what format I can use to do that

The following allows access on VLAN 1, but I would also like access on VLAN 7 and VLAN 10

Code: [Select]

http:
      address:192.168.1.1:8080

I tried the following three formats, but then AdguardHome failed to start up.

Code: [Select]

http:
      address:192.168.1.1:8080
      address:192.168.7.1:8080
      address:192.168.10.1:8080


Code: [Select]

http:
      address:192.168.1.1:8080, 192.168.7.1:8080, 192.168.10.1:8080


Code: [Select]

http:
      address:
            - 192.168.1.1:8080
            - 192.168.7.1:8080
            - 192.168.10.1:8080

None of the above format worked for me and googling doesn't provide relevant results and I was hoping if someone could tell me what format to use

EDIT: Weirdly, when I remove 0.0.0.0 from the bind_hosts, my OpnSense firmware updates start timing out. I can still access the internet just fine, but the Opnsense updates keep failing.

So should AdGuardHome be listening on ALL interfaces by default for dns: bind_hosts? Seems strange that only the OpnSense updates should fail while the internet is still accessible!!

11

General Discussion / Re: [SOLVED]Nextcloud config for HAProxy as reverse proxy

« on: August 17, 2023, 03:42:53 am »

Hello,

sorry for bringing this post back to life, but I have the same issue. I have followed this suggestion, but I still have the same issue.

Are there any known alternatives, or maybe could you describe if you had to change any config files in the nextcloud server itself? (shouldn't be needed, since it's going over reverse proxy, same as mine)

Thank you.
Kosta

You should list out your config so we can see. It's been working fine for me.

I can also suggest looking into using the Caddy plugin from the mimugmail repository. Finding config examples for Caddy is much easier than finding something for HAProxy on OpnSense. I plan to migrate to the Caddy plugin too... but currently everything works, so I am afraid to mess around with it now.

12

23.7 Legacy Series / Re: No hostname resolution after changing hostname on server

« on: August 17, 2023, 03:35:17 am »

Did the problem happen before or after you upgraded OPNsense?  Had you updated your static lease to the MAC of the new NIC?

I'm a bit unclear as to the order of events.

I updated first and during the reboots, I also changed the port from em1 to em0.

I changed the hostname much later in the process when I had no DNS resolution working.

13

23.7 Legacy Series / Re: No hostname resolution after changing hostname on server

« on: August 07, 2023, 04:55:37 am »

Yeah, this upgrade certainly changed a few of my settings in the Unbound configuration.

It disabled itself, then it also changed the outgoing interface and the active interface during the upgrade which I had already fixed however. But now I noticed that it had even removed my settings for Registering the DHCP static mappings and DHCP Leases which led to this problem of hostname resolution.

I enabled them both and now I have DNS hostname resolution on my network. I might have to keep an eye out for what else might have changed with Unbound during this upgrade.

14

23.7 Legacy Series / No hostname resolution after changing hostname on server

« on: August 07, 2023, 02:07:51 am »

I changed the network port from em1 to em0 on my NAS and I could no longer ping the server using the hostname leading to breakage in my NFS mounts etc. I thought I would just change the hostname to something new which I did, but I still cannot access it via the hostname. I can use the IP and everything works as expected.
I have tried flushing the unbound cache upon restart (using adguard with unbound as the upstream) but that hasn't helped. My resolv.conf points to my Opnsense router as the nameserver.

Any ideas how to get the new hostname to be recognized across the network?

15

23.7 Legacy Series / Re: Unbound failed to start after upgrading to 23.7, Domain Overrides Issue

« on: August 05, 2023, 07:20:50 pm »

I had a similar issue where Unbound failed to start after upgrade to 23.7.

I logged in using the IP address and found that Enable Unbound was unchecked. I checked that but it still failed to start. I found this thread and checked the active_interface in /conf/config.xml and noticed that there was an entry for ovpns1 but I had already deleted that interface as I switched from OpenVPN to Wireguard.

I was still logged into the UI via the IP address so I went to Unbound --> General and manually selected all the interfaces except Loopback under Network Interfaces. I no longer see an "All (recommended) option in that list for some reason. Saved the settings and then restarted Unbound and now I have DNS resolution again.

However, when I run_migrations via SSH, I still get the failure for Unbound Migration

Code: [Select]

*** OPNsense\Unbound\Unbound Migration failed, check log for detailsNot sure how I can upgrade again, because running upgrade indicates that there are no updates available. I also ran an update from console which also indicated that all packages are up to date.

I will reboot once more and see if Unbound restarts automatically on boot without any issues.

EDIT : Subsequent reboots have kept everything working, however the run_migrations.php script still indicates that Unbound Migration failed, but updates don't bring in any new packages.