What should I troubleshoot? ProxMox? OPNsense? AdGuard?

[CancunManny]

I am baffled and frustrated. I am going to share much info which probably most of it will be useless for you guys to help me, but maybe there is something I am missing that you guys are able to catch. Not sure if my issue is with proxmox, OPNsenes or something else.

So I have a beelink mini computer with two ethernet ports. I am running proxmox on that computer. Proxmox is running HomeAssistant, Frigate, OPNsense and AdGuard. I have 4 wifi access points, and about 8 Alexas.

In the living room I have the main "modem/router" from my ISP (only use it as a modem). I also have a wifi access point in the living room, and an Alexa. Those 3 devices don't run on AC anymore. I have an AC to DC power supply that provides the power. I am using step down/step up buck converters to get the correct volts to each of the devices. All running smooth for almost a year now.

4 days ago the circuit breakers popped. After some troubleshooting I found that the two hot wires that feed the mini splits (Air conditioners) got hot, melted the electrical tape and were basically short circuiting. Went ahead and fixed that issue, and now as far as electricity to the house it seems to be fine. All tv's, air conditioners, fridge, etc work well.

Well once I had the electricity sorted out I noticed I had no internet. I started to troubleshoot. The ISP modem shows a red light on LOS. I am able to access the modems control panel, and the error it gives is that it has no fiber-optic connected. Reported to my ISP 4 days ago, and still waiting for them to come fix it. As expected I was able to access my home assistant, my frigate, and I am able to get onto my OPNsense dashboard as well. Just didn't have internet access.

Yesterday my neighbor was kind enough to let me run a cat6 cable from his house to mine so that I can have internet while I wait for my ISP to come and fix it. Like I mentioned before I only use my ISP modem/router as a modem. Fiber optic connects to that modem, and I then run a cat6 from that modem to one of the beelink servers Ethernet ports. The 2nd ethernet port of the server is connected to a small switch which connects to the 4 access points via cat6 and there is a straight cat6 going to my main PC.

The temporary solution should have been as easy as connecting my neighbors cat6 to my server where I had the cat6 from my modem connected. However that just ended up sending me down another spiral. I am able to get an IP from OPNsense. I am able to log in to my OPNsense dashboard and see it does have a WAN ip assigned to it, however I can't connect to the internet via the computer (tried both with wired and wireless connection) and if I connect a cell phone to any of my wifis I am not able to get internet either. HOWEVER the Alexa Echo's and my Wyze cams connected to the SAME wifi's are able to connect to the internet. That has me TOTALLY confused.  If I bypass my server by connecting my neighbors cat6 directly to the swtich I am able to get internet in all of my devices, and as expected I can't access my frigate, HomeAssistant, etc., (In fact that is how I am connected to the internet at the moment).    This leads me to believe the issue might be with OPNsense.

When my network is connected to my server I am able to connect to HomeAssistant, Frigate and OPNsense. I am not able to connect to AdGuard via the dashboard, and in OPNsense the AdGuard shows red with a button to "start" however when I click on start it doesn't start. I then went ahead and "disabled" Adguard via OPNsense, but that didn't solve anything. I tired to access proxmox dashboard but I can't seem to get in. The IP that OPNsense shows for proxmox is 10.69.69.70 but it always shows it offline (even before my issues started). To access proxmox I should visit https://10.69.69.70:8006 and get the login screen, but nothing loads up. I don't login to proxmox dashboard often, so maybe I changed the IP and don't remember?

To make it more interesting, I also discovered that the Alexa in the living room (the one with dc power supply) stopped working. I can configure it, says that it is connected to my wifi but literally seconds after it connects it disconnects again. Figured it might be a power issue, so I swapped with the Alexa in the kitchen. I was able to confirm the Alexa from the living room is the one with the issue, as the kitchen one works fine with the regular power brick provided and with my DC supply, and the living room Alexa fails with either of the two power supplies.

I understand that when you have a short on your electrical system it can fry electronics, but the way my electronics are failing doesn't seem to make much sense. For example the modem, could a power issue kill the fiberoptic connection but leave everything else running fine? Also don't understand how the power issue would get to the devices without breaking something before. AC connects to the 12v power supply, which is working just fine. Then the 12v power supply connects to 3 different step down buck converters, each providing DC to a different device. So if power spiked it should have killed the 12v power supply, and if the 12v power supply glitched and sent higher volts, the buck converters should have taken care of that.

At this point I don't even know where to start trouble shooting. I brought the beelink server down to my office so I can connect a monitor and keyboard directly to it (haven't done it yet). However going by memory when I do bootup the server connected to a monitor I won't be able to see the actual dashboard. I will be able to access the console, but have no idea where I would go from there.

Any suggestions on what to try, or any info on what you guys think might be going on would be greatly appreciated!

[CancunManny]

I was finally able to log in to proxmox dashboard (I had the wrong IP address). Everything seems to be working fine there.  I did confirm that I don't have AdGuard running by itself, if I remember correctly I set up AdGuard directly inside of OPNsense. 

I am leaning towards my issue being OPNsense and/or AdGuard related.  Any suggestions on how I can trouble shoot?

[newsense]

Set DNS manually on a device and see if you can get out, either 1.1.1.2 or 9.9.9.11 would suffice

[CancunManny]

Set DNS manually on a device and see if you can get out, either 1.1.1.2 or 9.9.9.11 would suffice

Ok, I tried 1.1.1.2 on my main computer, and it worked!

I assume the issue is with AdGuard then?  I usually don't mind when I "break" things by playing with the configuration, but when stuff breaks on its own it drives me nuts!

Would you mind giving me suggestions on how to fix my issue?  And once I have everything back to normal, what could i do so it doesn't break on its own again?

[CancunManny]

I tried to go to OPNsense>System>Settings>General>DNS server section, and I put 1.1.1.2 and select the IPv4 WAN 
I had also previously disabled AdGuard

With those settings if I take off the DNS on my main computer it doesn't work. 

[newsense]

What is the outut when you start AGH manually ?

Code: [Select]

. /usr/local/AdGuardHome/AdGuardHome

[CancunManny]

What is the outut when you start AGH manually ?

Code: [Select]

. /usr/local/AdGuardHome/AdGuardHome

At the moment I am updating to the new version of OPNsense, but once that is done, how would I start AGH manually?  Log in to the OPNsense console and put in the code you shared?

[CancunManny]

Also, I am pretty sure I didn't make any changes to the default configuration of my ISP modem/router.  My neighbor has the same ISP provider but his actual modem/router hardware is different than mine.  Is there a possibility that once my ISP fixes my issue everything will start working properly again?

[CancunManny]

Ok, so took me a bit to figure out I had to run the command without the . before the /

the output of /usr/local/AdGuardHome/AdGuardHome is

Code: [Select]

root@OPNsense:~ # /usr/local/AdGuardHome/AdGuardHome
2024/09/15 22:30:25.412219 [info] AdGuard Home, version v0.107.45
2024/09/15 22:30:25.413605 [info] tls: using default ciphers
2024/09/15 22:30:25.415467 [info] safesearch default: disabled
2024/09/15 22:30:25.417278 [info] Initializing auth module: /usr/local/AdGuardHome/data/sessions.db
2024/09/15 22:30:25.417368 [info] auth: initialized.  users:0  sessions:1
2024/09/15 22:30:25.417381 [info] web: initializing
2024/09/15 22:30:25.427320 [info] dnsproxy: cache: enabled, size 4096 b
2024/09/15 22:30:25.427345 [info] dnsproxy: max goroutines is set to 300
2024/09/15 22:30:25.427469 [info] dnsproxy: cache: disabled
2024/09/15 22:30:25.427563 [info] AdGuard Home is available at the following addresses:
2024/09/15 22:30:25.427582 [info] clients: processing addresses
2024/09/15 22:30:25.427743 [info] go to http://[fe80::be24:11ff:fe47:7902%em0]:3000
2024/09/15 22:30:25.427759 [info] go to http://192.168.1.216:3000
2024/09/15 22:30:25.427767 [info] go to http://[2806:10be:a:767e:be24:11ff:fe47:7902]:3000
2024/09/15 22:30:25.427785 [info] go to http://10.69.69.1:3000
2024/09/15 22:30:25.427795 [info] go to http://[fe80::be24:11ff:fe11:4761%em1]:3000
2024/09/15 22:30:25.427802 [info] go to http://[2806:10be:a:8fbc:be24:11ff:feed:9287]:3000
2024/09/15 22:30:25.427809 [info] go to http://[::1]:3000
2024/09/15 22:30:25.427895 [info] go to http://[fe80::1%lo0]:3000
2024/09/15 22:30:25.427903 [info] go to http://127.0.0.1:3000
2024/09/15 22:30:25.592074 [info] dnsproxy: starting dns proxy server
2024/09/15 22:30:25.592107 [info] Ratelimit is enabled and set to 20 rps, IPv4 subnet mask len 24, IPv6 s                                                                                                                         ubnet mask len 56
2024/09/15 22:30:25.592115 [info] The server is configured to refuse ANY requests
2024/09/15 22:30:25.592122 [info] dnsproxy: cache: enabled, size 4194304 b
2024/09/15 22:30:25.592136 [info] dnsproxy: max goroutines is set to 300
2024/09/15 22:30:25.592150 [info] dnsproxy: creating udp server socket 0.0.0.0:53
2024/09/15 22:30:25.594068 [error] querylog: closing: flushing log buffer: nothing to write to a file
2024/09/15 22:30:25.594098 [fatal] couldn't start forwarding DNS server: starting listeners: listening on                                                                                                                          udp addr 0.0.0.0:53: listening to udp socket: listen udp 0.0.0.0:53: bind: address already in use
root@OPNsense:~ #

[CancunManny]

Well seems I figured it out, sortha.  I went ahead and removed AdGuardHome from OPNsense plugins, then I re installed again.  I had to disable Unbound DNS to solve the port 53 conflict.  In retrospect I think I had disabled Unbound DNS when I first installed AdGuard, seems somehow it got "enabled" and that is why AdGuard stopped working.    However not sure how settings changed since I hadn't done any updates at all. 

The whole situation is so weird and crazy!  So many things went wrong at the same time which makes it hard to believe they weren't all related. 

If anyone has any info or suggestions of what might have caused all my issues I would be glad to read