Easy Pin Over Wireguard Does Not Work With Tunnel Address

[storyofathen]

Info:
I have a firewall running Wireguard. Then my phone is connected to Wireguard.
For simplicity sake, Wireguard tunnel address (local) is 192.168.1.1/32, and the phone (endpoint) is 192.168.1.2/32

Issue:
In Jellyfin, the option to use local pin exists (quick pin to login on LAN without full password).
In Jellyfin under > Admin Dashboard > Networking > LAN Networks
I have my LAN networks specified.  Easy pin does not work unless I also specify the Wireguard address there. So I did.
192.168.1.1/32

Then, I go on my phone, try to login via easy pin.  Failed.

If I change in LAN Networks, (remove) 192.168.1.1/32 to (add) 192.168.1.2/32, all suddenly works no issues.
Now this makes sense to an extent, because my phone endpoint is 192.168.1.2/32

However, why does it not apply to the Wireguard tunnel address ip? Which would mean it'd allow ALL my devices connected to wireguard to login via easy pin.
Instead, I have to specify every single endpoint IP in Jellyfin?

[TheDreadPirate]

Because you are using /32, that means your subnet size is that specific address only. If you want the entire 192.168.1.X address space to be considered local, you would need to use /24. 192.168.1.0/24