Messages

seems you have tons of plugins.
if you find in the logs where and why it hangs, there is still the exclusion approach: step by step disable temporary plugins till its solved.

the "drastic" approach

- backup the config and save it in a safe place
- reformat and build from scrath with a "standard installation"
- update with the most basic config to just have internnet connectivity
- import your config
- reinstall needed plugins

maybe faster than headaches understanding whats wrong

FYI: this behaviour is not just related to i226v. i had the same pciex disconnection error on a I210AT (H13SAE-MF supermicro) with proxmox on linux. a bios updated reduced the behaviour which was particularly happening in "idle" moments. restarting the nic driver on linux solved without rebooting or replugging .
i ended to put a broadcom nic in the server.
the i226v in the toptons never gave me this behaviour.

I performed several upgrades without problems, so the issue is plausible related to your unit.

could be a defect storage which on my experience can cause problems on upgrades, so i would check smart.
or you have configuration on a plugin which is not working fine with later package versions. for that case i would remove the plugins and add them back and reconfigure them step by step.

or without breaking your head:
- backup the config file
- make a clean 24.1 install
- upgrade the clean box configured just essential
- import the config file

the settings of the plugins are kept but you must install the plugins manually again.

Maybe the first approch would be to the firewall logs, in the Firewall Section -> Log files -> Life view  make a filter in those destination ports and access from out. and see what the logs says. That would be a step further for debugging your problem. also i noticed you used "your firewall" and not the wan address for this

I had this behaviour with older Zenarmor version time ago when SSL Error pages (in beta) was active. deactivating that feature in Zenarmos solved my problem.

So could be another service crashing. i would check the system logs for errors

The Error pkg-static: py311-sqlite3-3.11.9_7 failed checksum from repository means the mentioned file saved on your unit is corrupted.
Can mean you have a Storage Device issue (is the smart plugin enabled? did you check?=
can also be an issue on the network path of the download.

i connect on console or by ssh and look for that file and delete it for downloading it again. dont know by mind if by repeating the update he repeats/overwrites the download.

in my case it was the SSD failed. after i noticed : SMART failure (the code was overheating) but was unusuable sectors. by replacing the SSD the problem has been solved, running 24.1.8 now

Hello,
on proxmox i am used to openvswitch because i prefer the vlan handling of openvswitch, but should be the same also with linux bridges. There is several approches to handle opnsense virtualized on proxmox:

Environment 1:
lets suppose you have the vmbr0 bridge where you have the management ip for proxmox. on openvswitch i dont put the ip on the vmbr but on a port without tag. so i have that bridge a Trunk. or anyway make it vlanaware. hope this is clear what its meant.
you probably have a vmbr1 where you have another nic linked which acts a WAN.
in this context you will create a vm for opnsense with 2 nics - put first vmbr0 and second vmbr1 . the installation will automatically assign vmbr0 as lan and vmbr1 as  wan. the vmbr1 will be connected to the internet. on vmbr0 when installed the opensense will be in your lan. put on the console a proper ip address and you can configure even vlans. works like a charm.
to make the proxmox "routable" you can then add the ip address of the opnsense to the management bridge/port of proxmox. so this makes it reachable from other subnets/vpn etc
the other vms will have vmbr0 as lan eventually with the proper tag for the corresponding vlan on the opnsense. put the opnsense ip as gateway.
if you will have a vm for truenas dont forget a controller with pci passthrough for ZFS mandatory. or if its phisical will be on same net with vmbr1 with an ip of same class like the lan port of opnsense the mangement of proxmox etc.

2nd environment like in a colocation with just a public ip assigned:
in that context you are forced based on the number of ip to act different:
- if you are lucky to have multiple ips just put the mgmt which will be the public ip with the proxmox firewall filtered and the opennse will have that bridge of management as WAN port . the lan will be SDN or a phsical port with other colocated stuff.
- if you have a single public ip you must work with some linux nat by configuring the proxmox router, there is several tutorials on youtube and forums how to handle that.

hope this tips helps

updating from shell with opnsense-update -up for me still ends up with 23.7.12_5 :-(

Hello everyone i configured also the /64 slices and the the /56 static and i have the same behaviour from the wan i can ping from the lan not. also RADV didnt help. anyone has a clue?

i have a similar issue, but i got the /56 static and so i cant activate track interface,