Emergency access
A backup way to connect when a network uses allow-lists and the main connection is blocked — create a video call, hand us its link from your cabinet or by email, and get a ready-to-use connection.
Emergency access is a backup way to connect for networks with allow-lists — where only a short list of approved services works and everything else, including your normal VPN, is blocked. It is not a replacement for your regular connection: it's slower, meant for short sessions, and only for the moments when nothing else gets through.
This feature is experimental. It may not work in every country or on every network, it depends on an external video service being reachable, and it does not guarantee the speed of your normal connection. Treat it as a lifeline, not a daily driver.
How it works, in short
You create a fresh video call in a service that the restricted network still allows, and hand us its link. A server joins that call as a guest, and your traffic travels inside the call — the network sees an ordinary video conference.
- You create a fresh call in a supported service.
- You hand us its link — either paste it into the Emergency access block in your cabinet, or email it to your personal request address. Both paths are equal and give the same result.
- In about a minute you get a ready-to-use connection that works for up to 12 hours.
- You import it into the emergency client and connect.
No permanent room, no always-on call, no separate subscription. Each session uses a fresh call you create right before connecting, and stops on its own when the time runs out.
Supported services
Paste the full room link from one of these:
| Service | What the link looks like |
|---|---|
| Yandex Telemost — telemost.yandex.ru | https://telemost.yandex.ru/j/… |
| WB Stream — stream.wb.ru | https://stream.wb.ru/room/… |
| Jitsi Meet — meet.jit.si or any other instance | https://meet.jit.si/YourRoomName |
The list in your cabinet is authoritative — it is generated from what the service currently supports. Links from other video services (Zoom, Google Meet, Sber Jazz and so on) are rejected with a clear message: there is no adapter for them.
Two practical notes: the room must be open to guests (in Telemost use a personal @yandex.ru account — it has no waiting room; in WB Stream create a free, non-private room), and for Jitsi you should first check in a browser that the instance opens on the restricted network at all.
Prepare in advance
Do this now, while your connection still works normally — during restrictions you may not be able to download apps or open pages.
Install the emergency client. Open your account cabinet, find the Emergency access block, and download the client (olcbox). Install it and keep it — you won't need it until an emergency.
Save your request address. In the same block, the By email panel shows your personal address — it looks like connect+service-name@…. Save it to your contacts together with the offline instructions (there's a button for that). Email is the one path that still works when the cabinet page itself is blocked, and by then you won't be able to look the address up.
Make sure your account is active. Emergency access requires an active account: if the subscription is paused or expired, the traffic limit is used up, or you have never paid for access, the request is rejected.
Try it once. While everything is normal, run the whole flow a single time and confirm you get a connection. Knowing it works beforehand is worth the two minutes.
During restrictions
Create a fresh call in one of the supported services and copy its link.
Send us the link — whichever way is open to you.
- In your cabinet: paste the link into the On this page panel of the Emergency access block and press Get connection.
- By email: send the link from your account email to your saved request address. Nothing else in the message — just the link.
Both do exactly the same thing. Use the cabinet while it opens; use email when it doesn't.
Wait about a minute. The server joins your call — this takes up to 90 seconds. Keep the call open while it happens.
Connect. You'll see a connection link (starting with olcrtc://) and a QR code. Copy the link into the emergency client on the same device, or scan the QR code with your phone to open it there.
More about the email path
The reply brings the same ready connection — as a link and a QR code you can scan with your phone. Two rules decide whether the request is recognised: send it from your account email (that's how we identify you), and put only the call link in the message (with several links we cannot tell which one is the room).
If the link or your account status is the problem, you get a reply explaining it. Complete silence means we could not recognise the request as yours at all — the mail failed its authentication checks, was sent from an address we don't know, or you exceeded the limit (five requests per hour). In that case check that you're sending from your account email, and try again later.
Sessions, time limits and stopping
- Each session lasts up to 12 hours, then stops automatically. To continue, create a new call and request a new connection.
- You can have one emergency session at a time. If one is already running, a new request changes nothing — wait for the current one to end, or stop it.
- You can stop the current session early from the Emergency access block, or just let it expire.
- The connection link is a secret: anyone who has it can use your connection. Don't forward it.
Good to know
- We never ask for your password, cookies, or account of the video service — you create the call yourself and give us only the link.
- The operator of the video service can see meeting metadata (participants, duration, traffic volume), the same as any call. Emergency access adds this external touchpoint that your normal connection does not have — another reason it's for emergencies only.
- It requires the client to be installed ahead of time and a video service that is actually reachable on your restricted network. If none of the supported services opens there, emergency access can't help — which is why testing in advance matters.