LAGG not getting IP after storm

[swILeZBa]

Hello, I have a bit of a weird problem which seems to be related to LAGG.

Context:
My homelab looks a bit like this:
Modem -> External Router -> Unifi switch -> Internal Router (OPNsense running on Topton) -> Internal devices
Apart from Modem and External Router the other devices are on a UPS with surge protection.

The other day there was a thunderstorm and I thought to disconnect the UPS for a while but not the Modem and the External Router. When the storm passed and I turned the devices on, almost nothing was working.

After some debugging, I figured out that the PoE ports of the Unifi switch (4/8) had had some issue (possibly fried) and I could only plug a cable to 0 or 1 ports at a time (I could plug in a cable if I used a USB to Ethernet adapter. Plugging a cable straight into it caused the Unifi switch to shut down until I removed it which it started its reboot sequence. Luckily, Unifi have agreed to RMA this)

I ordered a cheaper D-Link switch until they replace my Unifi switch, set up the VLAN's as before and again some stuff did not work as it should. Cue more debugging and I now figure out that WAN in OPNsense does not acquire an IP (It is DHCP statically allocated according to the guide here). I should say here that my WAN port was a LAGG of igc0 and igc1 with VLAN tag 10 and that it was working without a hitch for a long time. .

Now my first thought was that this port got fried too but I start trying a few things and figure out that if I remove the LAGG (LACP) and create a VLAN for each port separately (igc0.10, igc1.10) it works without a problem and the WAN does get an IP.
After tinkering for a while I restored to the config before my tinkering and again the same issue arose.

I think I was on at least 24.7 and I don't think I had updated for a few weeks so I am thinking 2 things:
1) Did anything change with regards to LAGG during the past few releases which would cause it to not be able to acquire an IP and I only realized because I turned off the router which usually runs 24/7?
2) Has any hardware been fried and now the 2 ports can't aggregate together?

For 1, I checked the changelogs and didn't see anything related
For 2, it's okay I did not really need the link aggregation, it was more as a proof of concept.

Any help is welcome and thank you for your time.