Port Forwarding for Valheim only not working

[senectus]

OPNSense 24.1.8
on Proxmox 8.2.2

All my other port forward rules work just fine. It seems like there is some issue with Valheim PFing.
I am beginning to think I might be running into the same issue as this guy with unraid
https://forum.opnsense.org/index.php?topic=38026.0

My Valheim server works internally by IP and pinging the address by name works fine internally and externally.
Trying to connect to the server by IP or Name gets the same result.

Valheim Server (Ubuntu 24.04 LTS, with a LinuxGSM install of Valheim) is a VM on a separate Proxmox Server

 I've been using "Is My Valheim Server Up?" https://geekstrom.de/valheim/check/ to check external connectivity.

If it is the same issue, I think I'm more inclined to backup my config and build the OPNSense as a physical, but I'd really like to keep the flexibility of Proxmox .
unfortunately that link (https://forum.opnsense.org/index.php?topic=38026.0) give precious little information about what the mysterious problem was that causes the port forwarding issue. Does anyone have any advice on how to troubleshoot/resolve this?
Screenshots of PF rules attached.

[heaven73]

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

[senectus]

Ok I'm not sure i can fully read what this is saying...

Something is blocking it, is "rulenr" the Firewall "Rule Number"?

If thats correct then Rule number 7 is"block all targeting port 0" which doesn't seem to jive?

[senectus]

so as I understand it, when I click on RID it should take me to the specific rule that blocked it.

When I do I the page "blinks" to a new tab then immediately closes that tab and I never get to see what rule was blocking it.

is there some way I can manually search for the rid "02f4bab031b57d1e30553ce08e0ec131" and see what rule was the blocker?