FAQ & Troubleshooting
We've compiled some of the most common questions and tips we receive about Whereby Embedded.
You can check for service outages and issues on our status page:
To use Whereby behind a firewall, a network administrator will need to adjust the settings. Port 443 will need to be open to all TCP and UDP traffic. Some enterprise firewalls require more in depth technical information for proper allowance, please contact your Customer Success Manager or [email protected]
We're aware of restrictions that have been put in place for peer to peer applications like Whereby. In these areas we've had reports from users that they have spotty access to Whereby, or that the service doesn't work for them at all.
Unfortunately, because these are government-level restrictions that have been put in place on the internet, there isn't anything we can do to address issues like this at this time.
- 1.The most common error we see relating to URL parameters is incorrectly using "?" twice in the meeting room URL. Combining parameters can be achieved by using the ampersand symbol (&) for example:
- 2.If the person using/testing the room is also logged into their Embedded account, it will override any parameters added to the room URL. Try accessing the room via a private or incognito window to verify your links are working as expected.
- 1.Host or Viewer privileges will only be available while the room is active and until 1 hour after the meeting's
Integrations are disabled for Whereby Embedded by default while using the
?minimalparameter. We set this by default because Content Security Policy restrictions can sometimes cause integrations to fail in unexpected ways. Currently only our YouTube and Miro integrations will work in an embedded setting.
If you would like to test an integration in your embedded meeting, you can do so by adding the
Please note, we offer limited support for integrations in an embedded meeting, even when enabled. It's highly recommended that you test before using it in a production context.
In some cases you may experience an error in your browsers developer console that looks something like this:
Access to fetch at "https://api.whereby.dev/v1/meetings' from origin S° nas WithOutLoginMult:1 been blocked by CORS policy...
You need to access the Whereby API from a server environment or computer. You aren't allowed access to the API via the browser console because it would expose your secret API key.