WeChat Stickers: Strange problem; Cannot load stickers when connected to network

[Scintillation]

Pixel 6a and Pixel 4a running Wechat cannot load stickers properly when app is open on Android 13. When Wifi is off and mobile data is on, the stickers load properly.
This is only for some stickers, not all stickers. Other functionality seems to work fine.

While on wifi, the stickers do not load, just get the spinning icon as show in this screenshot.
Setup is Opnsense > Unifi AC Lite access point > Phone, with Pihole set as DNS server.

At first I thought it was a DNS issue, but even when disabling blocking on Pihole and also setting DNS to 1.1.1.1 manually, the problem persists. It doesn't appear to be a DNS issue because the entries in Pihole when whitelisted, doesn't seem to make a difference.

We went to Grandma's for Thanksgiving, when connected to her wifi network, the stickers load properly.
She is using a ddwrt Archer A7 that I setup, all using 1.1.1.2 and 1.0.0.2. I don't recall any setting that would allow the stickers to load, vs my setup in OPNsense.

Is there some kind of default rule in the firewall that would prevent these particular stickers from loading? I did not add any rules of my own. Maybe geolocation blocking?

[Scintillation]

After playing around with no root android firewall on mobile data(block all and then allow one by one), it seems that either of these two IP's allow the stickers to load:

101.33.110.41
101.33.110.204

Why would these be blocked by OPNsense firewall?
Also, since I am a bit unfamiliar with mobile apps.
Are these IPs hardcoded into the app, or it is sending a DNS request for it?

Edit:
I examined the first IP address in OPNsense logs, indeed it looks like it is being blocked.
I would like some assistance on how to read these logs and also how to allow the traffic.

• 8,,,02f4bab031b57d1e30553ce08e0ec131,igb1,match,block,in,4,0x0,,64,9847,0,DF,6,tcp,40,192.168.1.156,101.33.110.41,48014,80,0,FA,2841549261,4019845570,716,,
• 8,,,02f4bab031b57d1e30553ce08e0ec131,igb1,match,block,in,4,0x0,,64,9842,0,DF,6,tcp,40,192.168.1.156,101.33.110.41,48014,80,0,FA,2841549261,4019845570,716,,
• 85,,,ef794793b2e3764b938bd04cba88e8a3,igb0,match,pass,out,4,0x0,,63,9821,0,DF,6,tcp,60,173.56.90.21,101.33.110.41,2377,80,0,S,2841548820,,65535,,mss;sackOK;TS;nop;wscale
• 85,,,ef794793b2e3764b938bd04cba88e8a3,igb0,match,pass,out,4,0x0,,63,35929,0,DF,6,tcp,60,173.56.90.21,101.33.110.41,24522,80,0,S,1182758240,,65535,,mss;sackOK;TS;nop;wscale

[Taunt9930]

Looks like it is matching one of your firewall rules.

[Scintillation]

Thanks, I figured that was the case.
igb0 is wan and igb1 is Lan.

What rule would cause it to be blocked on Lan?
I don't have any custom rules, only the auto generated ones.

[Scintillation]

Hello, I would like any assistance if possible to identify which firewall rules are causing the IP to be blocked.
I feel like I am doing my due diligence in investigating the problem, I just don't know what to do with the information I am finding.

Here are screenshots of LAN, WAN, Loopback, and Floating rules. Hopefully this is helpful.