Tools

WordPlus Cloud connection test

See whether this browser, on this network, reaches our realtime servers, relays and media servers, and how far away each region is. Send this page to anyone whose calls or live updates fail, or to whoever runs their network.

Your browser connects to our servers as an app on WordPlus Cloud would, with no account and no site named. We keep none of the results.

Step by step: WebRTC ports: which ones a video call needs and what a firewall must allow

For whoever runs the network

What a firewall has to allow

Allow these by name, as the addresses behind them change when we add servers and regions.

NamePortsWhat it is for
ws.wordplus.cloud
rest.wordplus.cloud
TCP 443Messages, presence and live updates.
turn.rtc.wordplus.cloudUDP 3478, UDP 443, TCP 443, TCP 80Relays, which carry a call when a firewall blocks the direct path. One of these ports is enough.
*.rtc.wordplus.cloudTCP 443Media servers, to join a group call or a live stream.
*.rtc.wordplus.cloudUDP, TCP 7900-7999The sound and picture of group calls and live streams. When these are closed, they go through the relays instead.

WordPlus Cloud

Realtime, calls and streams from one cloud

Your site or app runs no websocket server, relay or media server of its own. Each device reaches the region nearest to it, with nothing for you to set up.

Questions

Frequently asked

What does this connection test check?

That this browser, on this network, reaches each WordPlus Cloud service: the realtime servers that carry messages and live updates, the relays that carry calls when a firewall blocks the direct path, and the media servers behind group calls and live streams. It also measures the time to each region.

Why does a relay count as working when it refused the test?

The test has no account, so it logs in with details that are not valid and the relay refuses them. Only the relay itself can answer that way, which shows the path to it is open on that port. No call starts, and no relay is taken.

Why do some rows say Not tested in Firefox or Safari?

These browsers, and any browser on an iPhone, do not tell a page what a relay answered. So over UDP the test asks our relays a question that needs no login, and for TLS on port 443 it checks that our media servers answer on that port, which shows the port is open but not the relay behind it. Over TCP on port 80 there is nothing else to ask, so that row says Not tested, and calls still use that way in. Chrome or Edge on a computer tests every way in.

Do all the rows have to pass?

No. A call tries each way in and uses the one that works, so one relay row passing is enough. The realtime server and the media servers need port 443.

What does this test not check?

The ports that carry the sound and picture of group calls, 7900 to 7999, which a browser can only reach in a real call. When a network closes them, those calls go through the relays instead, so the relay rows show whether they can connect.

What should I do when something cannot be reached?

Try another network, such as a phone hotspot, and turn off any VPN, to see whether it is this network. If it is, ask whoever runs it to allow the addresses listed on this page, and to let WebSocket traffic through any proxy.

Why does the nearest region matter?

Each device reaches the region with the shortest time by itself, with nothing to set. The shorter that time, the shorter the delay people hear in a call.

Is anything sent to WordPlus?

Your browser connects to our servers as an app on WordPlus Cloud would, with no account and no site named. The results stay on this page, and we keep none of them.