Embedded Jitsi Meet returns 429 Too Many Requests

Hello, we have recently started to receive HTTP status code from meet.jit.si server when embedding Jitsi via iFrame API. Is there a new limitation per source domain or something like that? This affects our customers.

When opening the same link as the iframe src in the new tab, Jitsi work as expected. Seems the problem is linked to our source domain.

https://meet.jit.si/ isn’t designed for use as a white label backend for commercial products at scale; you may indeed be hitting limits. Jitsi as a Service (JaaS) is a paid offering run by the same team as meet.jit.si and is intended to meet this need: https://jaas.8x8.vc/

1 Like