UFW blocking frigate in limit rate. Bug or Feature?

I don't know if its by design or a bug but i needed to access my frigate from outside and exposed my 8971 port to the open world.

I already have other services exposed so I added the frigate in my ufw configuration. Like other services I put it under the "limit" rule to avoid suprises. Inside my network my rule is to allow all connections. After some testing i noticed when i'm home the frigate runs as expected, but when i'm outside my LAN I frigate don't respond correctly and won't stream the cameras at all.

Checking ufw logs I found it block the connections with the limit rule. A section of the limit is down below. I noticed in ufw logs that my phone creates A LOT of new connections and try to open a lot of ports in client side causing the ufw to flag and drop the connection.

Anyone had this problems? I don't know if is normal to a client open a lot of new connections on a server to trigger the ufw. It's like the frontend is calling a lot of APIs from the server by creating new connections.

I'm on ubuntu server 24.04, using ipv4 and ipv6. Frigate is installed under docker compose.