Why a Video Chat Won't Connect
"It just doesn't work" is the least useful thing a live video chat can tell you. In practice it fails in exactly four places, and the one you hit is usually obvious once you know what to look at. This is the version written by the people who run the thing — including the parts that are our fault, not yours.
- 1Permission
- 2Camera
- 3Video engine
- 4Room
In this guide
Three places a video chat can fail
Starting a live chat looks like one action, but it is really a short chain: your browser has to let the page use your camera, the page has to get hold of the camera hardware, the software that actually moves video across the internet has to be loaded, and a room has to exist for two people to meet in. Break any link and you get the same unhelpful result — nothing happens.
The useful part is that these four links fail in visibly different ways. A permission problem never looks like a network problem. A blocked video engine never looks like a camera problem. Once you can tell them apart, most of these are a ten-second fix.
Match the symptom to the cause
| What you see | What it actually is |
|---|---|
| A prompt asking for camera and microphone | Normal first step — permission has not been granted yet |
| A "camera blocked" screen, no connection attempt | Permission is set to denied for this site |
| Black preview, camera light off, nothing happens | The camera is still held by a previous session |
| The page works fine, but starting a chat does nothing | The video engine was blocked before it could load |
| It tries, then drops you back to the queue | The room never came up in time |
| Connected, but the picture is frozen or blocky | Not a failure — quality is scaling down to keep the call alive |
One distinction worth holding on to: a permission failure and a connection failure are different screens on purpose. If you are being told the connection failed, the camera is not the thing to go looking at.
1 · Camera and microphone permission
This is the most common reason a first chat never starts, and it is the least interesting one — which is exactly why it is worth ruling out first. Browsers grant camera access per site. Permission you gave a video-call app last week does nothing here.
There are three states, and the page behaves differently in each. If access is already granted, your camera starts immediately with no prompt. If it has been explicitly denied, the page does not even try to open the camera — it shows you how to undo that in your browser settings instead, because attempting it again would just fail silently. If nothing has been decided yet, you get a short note explaining why a video chat needs a camera, and then the browser's own permission prompt.
iPhone Safari is genuinely different. iOS Safari does not expose the browser API that lets a page read whether permission was already granted. Every other browser tells us; Safari does not. So on iPhone the page cannot skip ahead — it shows the explainer and lets the browser ask. If it feels like the site keeps forgetting your answer, that is why, and it is a platform limitation rather than something we can switch off.
The fix, if you did deny it once: open your browser's site settings for this page, set camera and microphone back to "ask" or "allow", and reload. On iOS that lives under Settings for the browser rather than in the page itself.
2 · The camera is still held by the last session
This one produces the most confusing symptom of the lot: permission is fine, you get no error worth reading, and the preview stays black with the camera indicator light off. Nothing appears broken. Nothing works either.
What has happened is that a previous chat did not release the camera. On iOS Safari in particular, a video element does not give the camera hardware back on its own when the page moves on — the tracks have to be stopped explicitly. We do that at the end of every normal call, and it is one of those steps that stays in the code with a warning attached to it, because removing it means the next call cannot get a camera. But if a session ended abnormally — the tab was killed, the browser was force-closed, the phone rebooted mid-call — that cleanup never ran.
The fix is a full reload, not a retry. Close the tab completely and reopen the page — a reload is what releases the stale camera handle. Also check that another app or another browser tab is not currently holding the camera, since only one thing can use it at a time.
A related version of the same idea: only one live session is allowed at a time. If a previous call is still believed to be running, a new one gets blocked. There is a check that looks at whether a real session actually exists rather than trusting the flag, and releases it when it does not — but a reload gets you there faster than waiting for anything to notice.
3 · The video engine never loaded
This is the failure that sends people looking in entirely the wrong place, because the website itself is working perfectly. Pages load. Buttons respond. You tap start, and nothing happens.
The reason is a deliberate design choice: the software that actually carries live video is not downloaded when you open the page. It is fetched the moment you start a chat. That keeps the landing page fast for the large majority of visitors who are reading rather than calling — but it also means the download can fail long after the site has appeared to work fine.
Things that block it: strict ad blockers and privacy extensions, some VPNs, and school, office, or hotel networks that filter which domains are reachable. Live video is a common thing for a network policy to block on purpose.
The test takes thirty seconds. Switch from the restricted network to mobile data, or pause your blocker for this site, and try again. If it works on one network and not the other, the network was the answer — no amount of fiddling with camera settings would have found it.
4 · The room itself never came up
The last rung is the one we own. A live chat is two people joining the same room, and that room has to be created and issued credentials before either of you can enter it. If any of that is missing or has expired, joining is impossible — and your connection being excellent makes no difference at all.
When it happens, the attempt is dropped and you go back to the queue. We would rather tell you that quickly than leave you watching a spinner, and there is a second reason for the speed: there is a real person on the other end of a match, holding a room that is not going to work. Releasing it fast puts them back in the queue too.
The connect window is a few seconds, not a minute. A room that has not come together in single-digit seconds is essentially never about to. If it drops you back, the correct move is just to start another match — that requests a brand-new room rather than retrying a dead one.
One thing in this area that is not a failure: a frozen or blocky picture on a weak connection. Live video scales its quality down to keep a conversation going rather than dropping the call, so a rough-looking chat is the system working as intended. Moving closer to the router, or switching between Wi-Fi and mobile data, normally clears it. There is more on that in our guide to video chat on a phone.
The 60-second checklist
In the order that actually resolves the most cases:
- Reload the page fully. Close the tab and reopen it rather than hitting retry. This alone clears the stale-camera case, which is the most common non-obvious failure.
- Check nothing else is using the camera. Another tab, a video call app in the background, or a camera app left open will hold it.
- Check the site permission. Camera and microphone should be "allow" or "ask" for this site — not "block".
- Pause blockers, or change network. If you are on a school, office, or hotel network, or running a VPN or strict blocker, test once on mobile data.
- Start a new match rather than retrying. If it dropped you back to the queue, the room was the problem — a new match gets a new room.
- Try a normal browser. If you opened the site from inside another app's built-in browser, open it in Safari or Chrome directly; embedded webviews are the usual source of "not supported".
If you have been through all six and it still will not start, that is worth telling us — the failure is genuinely ours at that point, and a note about your device and browser is what makes it findable. You can reach us from the contact page.
FAQ
Camera access is granted per site, not once for the whole browser, so a permission you gave another site does not carry over. The other common version of this is that the camera is still held by a previous session that did not close cleanly — most often on an iPhone, where a video element does not release the camera hardware on its own. Fully closing the tab and reopening the page clears it.