Diagnostics / WebRTC
Connection check
Find out whether this browser and network can open a NulBridge session. Four quick checks run in this tab, with no camera or microphone prompt.
01Run the check
Verdict
4 checks
Untested
Run the check to see whether a session can start from this browser and network.
No camera or mic prompt · Nothing stored
- 01
Browser support
Status: Not runLooks for WebRTC, WebRTC data channels and the Web Crypto API on a secure (HTTPS) page. It also checks whether calls could use a camera and microphone, without asking for access.
RequiredNulBridge creates your keys and the connection inside the browser. Without these features, no session can start.
Not run yet
- 02
Network path
Status: Not runOpens a temporary WebRTC connection that goes nowhere and counts the routes your browser can offer: local, public (found through STUN) and relayed (TURN). Addresses are never shown or saved.
RequiredTwo browsers connect directly when a public route works. Without one, only devices on the same network can reach each other, unless a relay is available.
Not run yet
- STUN servers
- 3
- TURN relays
- None
- 03
Signaling server
Status: Not runRegisters a random, single-use ID with the signaling server, then disconnects straight away.
RequiredThe signaling server introduces the two browsers and passes the connection setup between them. It sees IP addresses and peer IDs, never your messages or keys. Without it, no session can start.
Not run yet
- Server
- 0.peerjs.com
- 04
6-digit code service
Status: Not runAsks the 6-digit code service whether it’s up. No code is created and nothing is stored.
OptionalOnly 6-digit codes need this service. Private links work without it.
Not run yet
- On this site
- Enabled
02Results
Three verdicts.
The check combines its four results into one answer about this browser and this network.
Ready.
Every required check passed. Create a private link or a 6-digit code, and connect.
Limited.
A session can start, but something won’t fully work: there’s no public network route, calls can’t use a camera or microphone, or 6-digit codes are down. The flagged check says what to do.
Blocked.
A required check failed: a browser feature is missing, WebRTC is blocked, or the signaling server is out of reach. Fix that check, then run it again.
03Troubleshooting
When a connection fails.
Most failures come from the network, not the browser. Work through these in order.
Check both devices
A connection needs a working route on both sides. If the other person gets LIMITED or BLOCKED, start with their network.
Switch networks
Office, school and hotel Wi-Fi often block peer-to-peer traffic. Mobile data usually works.
Pause VPNs and blockers
Some VPNs, privacy extensions and ad blockers stop WebRTC or the signaling server.
Update the browser
Use a current version of Chrome, Edge, Firefox or Safari, on an HTTPS page.
Keep both tabs in front
Phones pause background tabs, and a paused tab drops the connection.
Ask for a relay
The strictest networks only work through a TURN relay. The operator of this site can add one.
Still stuck? Read why a connection might not go through and how direct and relayed connections work.
04Privacy
What the check sends.
It contacts the same services a real session uses, and they see what they would see in a session. Nothing else leaves this tab.
| STUN servers | Your IP address, so they can tell your browser its public address. |
|---|---|
| Signaling server | Your IP address and a random, single-use ID (0.peerjs.com). The ID is dropped when the check disconnects. |
| TURN relay | Not contacted: this site has no relay. |
| 6-digit code service | Your IP address and a status request. No code is created. |
| Camera & microphone | Never accessed. The check only asks whether the browser supports them. |
| Your results | Stay in this tab. They’re never uploaded or stored. |
Checked and ready?
Open a bridge.
Create a private link or use a 6-digit code. Free, no account, nothing stored.