Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - axsdenied

#1
26.7 Series / Re: 26.7.1_1 -> 26.7.2 Boot loop
August 12, 2026, 07:54:29 PM
It appears removing the realtek drivers worked for me as well.  While my motherboard's nic is realtek, I don't use it, I use an intel pci-e 4 port card so I was ok disabling it.

Below are my logs from the boot with the realtek drivers installed showing the panic:
P.S. the new services widget, is much improved, thanks for that :)

---<<BOOT>>---
Copyright (c) 1992-2025 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 15.1-RELEASE-p2 stable/26.7-n283714-dd064f22c895 SMP amd64
FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
[1] VT(efifb): resolution 1024x768
[1] CPU: Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz (3500.00-MHz K8-class CPU)
[1]   Origin="GenuineIntel"  Id=0x906e9  Family=0x6  Model=0x9e  Stepping=9
[1]   Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
[1]   Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
[1]   AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
[1]   AMD Features2=0x121<LAHF,ABM,Prefetch>
[1]   Structured Extended Features=0x29c6fbf<FSGSBASE,TSCADJ,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
[1]   Structured Extended Features3=0xbc002e00<MCUOPT,MD_CLEAR,TSXFA,IBPB,STIBP,L1DFL,ARCH_CAP,SSBD>
[1]   XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
[1]   IA32_ARCH_CAPS=0xc04<RSBA>
[1]   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
[1]   TSC: P-state invariant, performance statistics
[1] real memory  = 8589934592 (8192 MB)
[1] avail memory = 8186134528 (7806 MB)
[1] Event timer "LAPIC" quality 600
[1] ACPI APIC Table: <DELL   CBX3   >
[1] FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
[1] FreeBSD/SMP: 1 package(s) x 4 core(s)
[1] random: registering fast source Intel Secure Key Seed
[1] random: fast provider: "Intel Secure Key Seed"
[1] random: unblocking device.
[1] ioapic0 <Version 2.0> irqs 0-119
[1] Launching APs: 3 2 1
[1] random: entropy device external interface
[1] wlan: mac acl policy registered
[1] kbd1 at kbdmux0
[1] WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 16.0.
[1] efirtc0: <EFI Realtime Clock>
[1] efirtc0: registered as a time-of-day clock, resolution 1.000000s
[1] smbios0: <System Management BIOS> at iomem 0xf0600-0xf0617
[1] smbios0: Entry point: v3 (64-bit), Version: 3.0
[1] aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS>
[1] acpi0: <DELL CBX3   >
[1] acpi0: Power Button (fixed)
[1] cpu0: <ACPI CPU> on acpi0
[1] hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
[1] Timecounter "HPET" frequency 24000000 Hz quality 950
[1] Event timer "HPET" frequency 24000000 Hz quality 550
[1] Event timer "HPET1" frequency 24000000 Hz quality 440
[1] Event timer "HPET2" frequency 24000000 Hz quality 440
[1] Event timer "HPET3" frequency 24000000 Hz quality 440
[1] Event timer "HPET4" frequency 24000000 Hz quality 440
[1] atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
[1] atrtc0: Warning: Couldn't map I/O.
[1] atrtc0: registered as a time-of-day clock, resolution 1.000000s
[1] Event timer "RTC" frequency 32768 Hz quality 0
[1] attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
[1] Timecounter "i8254" frequency 1193182 Hz quality 0
[1] Event timer "i8254" frequency 1193182 Hz quality 100
[1] Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
[1] acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
[1] pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
[1] pci0: <ACPI PCI bus> on pcib0
[1] pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
[1] pci1: <ACPI PCI bus> on pcib1
[1] pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
[1] pci2: <ACPI PCI bus> on pcib2
[1] pcib3: <PCI-PCI bridge> irq 17 at device 1.0 on pci2
[1] pci3: <PCI bus> on pcib3
[1] igc0: <Intel(R) Ethernet Controller I226-V> mem 0xf7a00000-0xf7afffff,0xf7b00000-0xf7b03fff irq 17 at device 0.0 on pci3
[1] igc0: EEPROM V2.17-0 eTrack 0x80000303
[1] igc0: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc0: Using 4 RX queues 4 TX queues
[1] igc0: Using MSI-X interrupts with 5 vectors
[1] igc0: Ethernet address: b0:b1:a1:b6:72:37
[1] igc0: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib4: <PCI-PCI bridge> irq 18 at device 2.0 on pci2
[1] pci4: <PCI bus> on pcib4
[1] igc1: <Intel(R) Ethernet Controller I226-V> mem 0xf7700000-0xf77fffff,0xf7800000-0xf7803fff irq 18 at device 0.0 on pci4
[1] igc1: EEPROM V2.17-0 eTrack 0x80000303
[1] igc1: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc1: Using 4 RX queues 4 TX queues
[1] igc1: Using MSI-X interrupts with 5 vectors
[1] igc1: Ethernet address: b0:b1:a1:b6:72:34
[1] igc1: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib5: <PCI-PCI bridge> irq 19 at device 3.0 on pci2
[1] pci5: <PCI bus> on pcib5
[1] igc2: <Intel(R) Ethernet Controller I226-V> mem 0xf7400000-0xf74fffff,0xf7500000-0xf7503fff irq 19 at device 0.0 on pci5
[1] igc2: EEPROM V2.17-0 eTrack 0x80000303
[1] igc2: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc2: Using 4 RX queues 4 TX queues
[1] igc2: Using MSI-X interrupts with 5 vectors
[1] igc2: Ethernet address: b0:b1:a1:b6:72:35
[1] igc2: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib6: <PCI-PCI bridge> irq 16 at device 4.0 on pci2
[1] pci6: <PCI bus> on pcib6
[1] igc3: <Intel(R) Ethernet Controller I226-V> mem 0xf7100000-0xf71fffff,0xf7200000-0xf7203fff irq 16 at device 0.0 on pci6
[1] igc3: EEPROM V2.17-0 eTrack 0x80000303
[1] igc3: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc3: Using 4 RX queues 4 TX queues
[1] igc3: Using MSI-X interrupts with 5 vectors
[1] igc3: Ethernet address: b0:b1:a1:b6:72:36
[1] igc3: netmap queues/slots: TX 4/1024, RX 4/1024
[1] vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem 0xf6000000-0xf6ffffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
[1] vgapci0: Boot video device
[1] xhci0: <Intel Union Point USB 3.0 controller> mem 0xf7d10000-0xf7d1ffff irq 17 at device 20.0 on pci0
[1] xhci0: 32 bytes context size, 64-bit DMA
[1] xhci0: xECP capabilities <PROTO,PROTO,VEND(c0),LEGACY,VEND(c6),VEND(c7),VEND(c2),DEBUG,VEND(c3),VEND(c4),VEND(c5)>
[1] usbus0: waiting for BIOS to give up control
[1] xhci_interrupt: host controller halted
[1] usbus0 on xhci0
[1] usbus0: 5.0Gbps Super Speed USB v3.0
[1] pci0: <simple comms> at device 22.0 (no driver attached)
[1] ahci0: <Intel Union Point AHCI SATA controller> port 0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7d28000-0xf7d29fff,0xf7d2c000-0xf7d2c0ff,0xf7d2b000-0xf7d2b7ff irq 22 at device 23.0 on pci0
[1] ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported
[1] ahcich0: <AHCI channel> at channel 0 on ahci0
[1] ahcich1: <AHCI channel> at channel 1 on ahci0
[1] ahciem0: <AHCI enclosure management bridge> on ahci0
[1] pcib7: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
[1] pci7: <ACPI PCI bus> on pcib7
[1] re0: <Realtek PCIe GbE Family Controller> port 0xe000-0xe0ff mem 0xf7c04000-0xf7c04fff,0xf7c00000-0xf7c03fff irq 16 at device 0.0 on pci7
[1] re0: Using Memory Mapping!
[1] re0: Using 1 MSI-X message
[1] re0: ASPM disabled
[1] re0: version:1.102.01
[1] re0: Ethernet address: d8:9e:f3:37:ec:a0
[1]
[1] This product is covered by one or more of the following patents:           
[1] US6,570,884, US6,115,776, and US6,327,625.
[1] re0: Ethernet address: d8:9e:f3:37:ec:a0
[1] isab0: <PCI-ISA bridge> at device 31.0 on pci0
[1] isa0: <ISA bus> on isab0
[1] pci0: <memory> at device 31.2 (no driver attached)
[1] hdac0: <Intel Kaby Lake-H HDA Controller> mem 0xf7d20000-0xf7d23fff,0xf7d00000-0xf7d0ffff irq 21 at device 31.3 on pci0
[1] acpi_button0: <Sleep Button> on acpi0
[1] acpi_button1: <Power Button> on acpi0
[1] acpi_tz0: <Thermal Zone> on acpi0
[1] acpi_tz1: <Thermal Zone> on acpi0
[1] uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
[1] atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
[1] atkbd0: <AT Keyboard> irq 1 on atkbdc0
[1] kbd0 at atkbd0
[1] atkbd0: [GIANT-LOCKED]
[1] driver bug: Unable to set devclass (class: atkbdc devname: (unknown))
[1] orm0: <ISA Option ROMs> at iomem 0xc0000-0xcffff,0xd0000-0xd0fff pnpid ORM0000 on isa0
[1] hwpstate_intel0: <Intel Speed Shift> on cpu0
[1] cpufreq0: <CPU frequency control> on cpu0
[1] hwpstate_intel1: <Intel Speed Shift> on cpu1
[1] cpufreq1: <CPU frequency control> on cpu1
[1] hwpstate_intel2: <Intel Speed Shift> on cpu2
[1] cpufreq2: <CPU frequency control> on cpu2
[1] hwpstate_intel3: <Intel Speed Shift> on cpu3
[1] cpufreq3: <CPU frequency control> on cpu3
[1] Timecounter "TSC-low" frequency 1751996437 Hz quality 1000
[1] Timecounters tick every 1.000 msec
[1] ZFS filesystem version: 5
[1] ZFS storage pool version: features support (5000)
[1] hdacc0: <Realtek ALC255 HDA CODEC> at cad 0 on hdac0
[1] hdaa0: <Realtek ALC255 Audio Function Group> at nid 1 on hdacc0
[1] pcm0: <Realtek ALC255 (Rear Analog Line-out)> at nid 27 on hdaa0
[1] hdacc1: <Intel Kaby Lake HDA CODEC> at cad 2 on hdac0
[1] hdaa1: <Intel Kaby Lake Audio Function Group> at nid 1 on hdacc1
[1] pcm1: <Intel Kaby Lake (HDMI/DP 8ch)> at nid 5 on hdaa1
[1] pcm2: <Intel Kaby Lake (HDMI/DP 8ch)> at nid 6 on hdaa1
[1] pcm3: <Intel Kaby Lake (HDMI/DP 8ch)> at nid 7 on hdaa1
[1] ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WD Blue SA510 2.5 500GB 52046100> ACS-4 ATA SATA 3.x device
ada0: Serial Number 22303Q802015
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 476940MB (976773168 512 byte sectors)
[1] cd0 at ahcich1 bus 0 scbus1 target 0 lun 0
cd0: <HL-DT-ST DVD+-RW GU90N A1C1> Removable CD-ROM SCSI device
cd0: Serial Number M1IG6CK1400
cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
[1] ses0 at ahciem0 bus 0 scbus2 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 2.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
[1] ses0: ada0,pass0 in 'Slot 00', SATA Slot: scbus0 target 0
[1] ses0: cd0,pass1 in 'Slot 01', SATA Slot: scbus1 target 0
[1] Trying to mount root from zfs:zroot/ROOT/default []...
[1] ugen0.1: <Intel XHCI root HUB> at usbus0
[1] uhub0 on usbus0
[1] uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
[2] Root mount waiting for: usbus0
[2] uhub0: 22 ports with 22 removable, self powered
[2] ugen0.2: <American Power Conversion Back-UPS XS 1500M FW:947.d11 .D USB FW:d11> at usbus0
[3] ugen0.3: <PiKVM PiKVM Composite Device> at usbus0
[3] usbhid0 on uhub0
[3] usbhid0: <PiKVM PiKVM Composite Device, class 0/0, rev 2.00/1.00, addr 2> on usbus0
[3] hidbus0: <HID bus> on usbhid0
[3] hkbd0: <PiKVM PiKVM Composite Device Keyboard> on hidbus0
[3] kbd2 at hkbd0
[3] usbhid1 on uhub0
[3] usbhid1: <PiKVM PiKVM Composite Device, class 0/0, rev 2.00/1.00, addr 2> on usbus0
[3] hidbus1: <HID bus> on usbhid1
[3] usbhid2 on uhub0
[3] usbhid2: <PiKVM PiKVM Composite Device, class 0/0, rev 2.00/1.00, addr 2> on usbus0
[3] hidbus2: <HID bus> on usbhid2
[3] umass0 on uhub0
[3] umass0: <PiKVM PiKVM Composite Device, class 0/0, rev 2.00/1.00, addr 2> on usbus0
[3] umass0:  SCSI over Bulk-Only; quirks = 0x0
[3] umass0:3:0: Attached to scbus3
[3] cd1 at umass-sim0 bus 0 scbus3 target 0 lun 0
cd1: <PiKVM Optical Drive 1.00> Removable CD-ROM SCSI-2 device
cd1: 40.000MB/s transfers
cd1: Attempt to query device size failed: NOT READY, Medium not present
cd1: quirks=0x10<10_BYTE_ONLY>
[7] igc0: link state changed to UP
[7] igc1: link state changed to UP
[7] igc2: link state changed to UP
[7] kernel trap 12 with interrupts disabled
[7]
[7]
[7] Fatal trap 12: page fault while in kernel mode
[7] cpuid = 3; apic id = 06
[7] fault virtual address = 0x22710068
[7] fault code = supervisor write data, page not present
[7] instruction pointer = 0x20:0xffffffff80c71200
[7] stack pointer         = 0x28:0xfffffe008a3679c0
[7] frame pointer         = 0x28:0xfffffe008a367a00
[7] code segment = base 0x0, limit 0xfffff, type 0x1b
[7] = DPL 0, pres 1, long 1, def32 0, gran 1
[7] processor eflags = resume, IOPL = 0
[7] current process = 0 (netlink_socket (PID)
[7] rdi: fffff800120593c0 rsi: fffff800663bf2b8 rdx: fffff800120593e0
[7] rcx: fffff80012059420  r8: 0000000000000000  r9: 0000000000000010
[7] rax: 0000000022710000 rbx: fffff8001207a780 rbp: fffffe008a367a00
[7] r10: 0000000000000000 r11: 0000000000000570 r12: ffffffff82213e28
[7] r13: 0000000000000000 r14: fffff800663bf420 r15: fffff800120593c0
[7] trap number = 12
[7] panic: page fault
[7] cpuid = 3
[7] time = 1786544944
[7] KDB: stack backtrace:
[7] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe008a367710
[7] vpanic() at vpanic+0x136/frame 0xfffffe008a367840
[7] panic() at panic+0x43/frame 0xfffffe008a3678a0
[7] trap_pfault() at trap_pfault+0x37d/frame 0xfffffe008a3678f0
[7] calltrap() at calltrap+0x8/frame 0xfffffe008a3678f0
[7] --- trap 0xc, rip = 0xffffffff80c71200, rsp = 0xfffffe008a3679c0, rbp = 0xfffffe008a367a00 ---
[7] turnstile_wait() at turnstile_wait+0x120/frame 0xfffffe008a367a00
[7] __mtx_lock_sleep() at __mtx_lock_sleep+0x175/frame 0xfffffe008a367a90
[7] re_init() at re_init+0x27/frame 0xfffffe008a367ab0
[7] dump_iface() at dump_iface+0x11a/frame 0xfffffe008a367b50
[7] dump_cb() at dump_cb+0x1c/frame 0xfffffe008a367b70
[7] if_foreach_sleep() at if_foreach_sleep+0x227/frame 0xfffffe008a367bf0
[7] rtnl_handle_getlink() at rtnl_handle_getlink+0x257/frame 0xfffffe008a367cd0
[7] rtnl_handle_message() at rtnl_handle_message+0x195/frame 0xfffffe008a367d30
[7] nl_taskqueue_handler() at nl_taskqueue_handler+0x469/frame 0xfffffe008a367e40
[7] taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xfffffe008a367ec0
[7] taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe008a367ef0
[7] fork_exit() at fork_exit+0x7b/frame 0xfffffe008a367f30
[7] fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe008a367f30
[7] --- trap 0xc, rip = 0x3deae40b0c8a, rsp = 0x3deae6647f48, rbp = 0x3deae6647f60 ---
[7] KDB: enter: panic
#2
26.7 Series / 26.7.1_1 -> 26.7.2 Boot loop
August 12, 2026, 05:01:38 PM
Apologies in advanced as this post won't have a lot of useful info yet. Unfortunately, I don't have time this morning to figure out what happened but when upgrading to 26.7.2 I ended up in a boot loop.  I changed my BE back to 26.7.1_1 and was back up.

I have time later today to see what was going on and provide logs, but I wanted to post in case someone else was running into the same thing and might have more to share.

Quick addition, I do not have cpu microcode installed.
#3
Quote from: patient0 on July 20, 2026, 05:40:51 PM
Quote from: miketubby on July 20, 2026, 05:37:48 PMI added 77.**.**.49 as a Gatewa
You set that gateway in the WAN interface settings, in the field "IPv4 gateway rules"? If yes, then I don't know, works for me.

This.  When  you say you added the gateway, was that to the interface or to System->Gateways? You must set the upstream gateway on the WAN interface or that NAT rules won't be generated as it doesn't treat it as a path.
#4
Do you have an ICMP LAN allow firewall rule? Source LAN Network -> Anywhere
#5
I did all the audit checks and everything checked out ok so I'm assuming, at least my issue, was just related to that incorrect service test.
#6
Found the issue, unrelated to upgrade. The error just happened to show during service restart.  It was one of my custom service test checks.  Removed it, rebooted and we're back in business.


---------------
During the update a pop up showed an unknown error message and suggested looking at the logs.  I went to the logs and got a 404 error message.  The upgrade continued and it rebooted and the webui was back.  I checked the logs and didn't see any errors logged however I noticed monit was stopped.  I tried starting and it won't start.  Checked the logs and got the following:

2026-03-04T08:21:27-07:00Noticekernel<118>[40] /usr/local/etc/rc.d/monit: WARNING: failed to start monit
2026-03-04T08:21:27-07:00Noticekernel<118>[40] monit exiting due to parsing errors in the configuration file.
2026-03-04T08:21:27-07:00Noticekernel<118>[40] /usr/local/etc/monitrc:43: syntax error 'if'
2026-03-04T08:21:27-07:00Noticekernel<118>[40] Starting monit.

I checked line 43 of monitrc and it shows "if if failed host 127.0.0.1 port 2198 type tcp then restart then restart"

Show I just edit it even though it says not to?
#7
25.7, 25.10 Legacy Series / Re: Update to 25.7.6...
October 23, 2025, 03:41:58 PM
After reading this thread, I got prepped and braced to deal with whatever.  Snapshotted, backed up, already ssh'd in, etc.  But when I went to update...it just updated, no errors, no need to recheck for updates and was on 25.7.6 with no issue?  I also use the mimugmail repo.
#8
I believe it's the traffic graph.  Thats what I see crash out most and first.
#9
Quote from: JDabbs on July 24, 2025, 11:45:01 AMUninstalled the os-cpu-microcode-intel microcode & rebooted to make sure it took effect.

Ran the upgrade to 25.7 device hung, power cycled it and it came up OK so removing the microcode did improve the situation. Unfortunately I'm running this router headless so could not see any errors on screen - I have to take it out of the rack to attach a monitor to it.

I'm going to continue running it without the microcode installed and see how it goes. Following on from Franco said earlier I will look it there is a BIOS update available, it's a small fan less PC so may need to do some research to find it.

PS big thank you to Franco for you extremely rapid and helpful suggestion, I love this community.

I highly recommend using a PIKVM for this type of situation.  I also run my servers headless but still need console from time to time.  Works flawlessly.
#10
Yup this has been happening to me after they did the UI overhaul.  I can only refresh the page, assuming it doesn't hang, to get everything back.
#11
Quote from: Isabella Borgward on June 23, 2025, 06:53:51 PMI was under the impression that this functionality was deprecated by Google, so have changed my backup method to Oxidized.

It's going to be and I believe a plugin is what will be suggested.

https://github.com/opnsense/core/issues/8343
#12
Just keying off your use of "instance"...Are you virtualizing it?
#13
Quote from: craig_ on June 20, 2025, 06:02:41 AMYou shouldn't need to bridge the interfaces. If the VLANs are all setup correctly, traffic should be routable so a few firewall policies should be all you need. Check the users Windows firewall is configured, too.

Have a read of the Steam FAQ regarding the requirements:
The network transfer happens on TCP port 27040 and it needs to be allowed by local firewall software. You also need to open UDP ports 27031-27036 for client discovery.


Are you able to add in a network diagram?

This!
#14
A few things you can check:

- Encryption Password Mismatch
If you've set a password for encrypting the backups in OPNsense, but it's missing or incorrect during the backup process, the system may still create the file but fail to write the actual config data. Double-check that the password is set and confirmed correctly in System → Configuration → Backups.
- Service Account Permissions
Make sure the Google Drive folder is shared with the service account email (not just your personal Google account). The service account must have Editor access to the folder, or it won't be able to write the file contents—even if it can create the file shell.
- P12 Key or Client ID Issues
If the P12 key is invalid, expired, or mismatched with the service account, authentication may partially succeed (enough to create a file) but fail silently when uploading the actual data. Try re-generating the key and re-uploading it to OPNsense.

Someone else filed a bug in git hub but not sure if it's due to the above or an actual bug.  Mine are backing up fine, I just had one go last night and I'm on the latest version.
https://github.com/opnsense/plugins/issues/4731
#15
Sure thing:

First Create a new Monit Service Test. Image 1.
Then create a Service and point to the Service Test. Image 2


https://imgur.com/a/3klgQ7M