How to Fix Roblox Error 773 (Teleport Failed: Restricted Place)
What error 773 means
Roblox worlds are constantly shuffling players around: from a lobby into a match, from a tutorial into the main world, from one experience into another through a portal or "play" button. Each of those moves is a teleport — your client drops one server and picks up a fresh connection to another. Error 773 fires when that move is blocked at the door. The full message reads "Teleport Failed: Attempted to teleport to a place that is restricted (Error Code: 773)," and unlike the generic error 769 ("unknown exception"), it tells you exactly what happened: Roblox refused to send you to the destination because it couldn't grant you access.
"Restricted" covers more than you'd think. The destination place might be set to private, it might be under review by Roblox's moderators, it might carry an age rating your account can't enter, the private server link you clicked might have expired, or the server itself might be full or shutting down. There's also a sneakier cause on your own side: being logged into Roblox on two devices at once can confuse the teleport system, which can't decide which session should receive you — and blocks the request. Understanding which bucket your case falls into is the whole fix, because 773 is rarely a broken installation; it's almost always an access or session problem.
The good news is that this error is specific, which makes it faster to fix than the mystery teleport codes. If the error shows up in only one game, the restriction lives with that game — its settings, its servers, or its links — and you can often route around it by joining a different server. If it shows up everywhere, the cause is your sessions or your connection, and the logout-everywhere fix below usually clears it in minutes.
Common causes
- Private or under-review destination: the place you're teleporting to is set to private, is under Roblox moderation review, or has third-party teleports disabled — access is denied outright.
- Double-login session: you're signed into Roblox on two devices or locations at once, so the teleport system can't identify your session and restricts the request.
- Age-restricted destination: under-13 accounts can't teleport into experiences rated 13+, and Roblox blocks the move with error 773.
- Expired private-server link: the private server invite you used has expired or the owner revoked your access, so the destination no longer accepts you.
- Full, broken, or overloaded destination server: the target server filled up, crashed, or went offline before the handoff completed.
How to fix error 773 — step by step
Work through these fixes in order. Test with the same teleport after each step.
- Log out of all Roblox sessions except this one. Open roblox.com in a browser, sign in, and go to Settings (the gear icon) > Security > Active Sessions. Sign out of every other device and location so only your current device stays logged in. A double-login session is a classic trigger for error 773, because Roblox can't tell which session should receive the teleport and blocks it. After signing out everywhere else, restart Roblox and try the teleport again.
- Check whether the destination place is restricted. Error 773 literally means "attempted to teleport to a place that is restricted." Open the game's page on roblox.com and check whether it's public, private, under review, or has an age rating your account can't enter. If it's a private server, the link may have expired or the owner may have revoked your access — ask them for a fresh link. If you're under 13, you can't teleport into 13+ rated experiences; switch to a destination rated All Ages instead.
- Join a different, working server. Go to the experience's page on the Roblox website or app, scroll down to the server list, and pick a different populated server manually. If the teleport came from inside a game (for example moving from a lobby into a match), leave the experience entirely and rejoin it from its main page so Roblox assigns you a fresh server. Retrying on a different server bypasses full, broken, or restricted destinations.
- Update Roblox and restart your device. An outdated client can fail teleports that newer servers reject. On PC, launching Roblox from roblox.com checks for updates automatically; on mobile, update from the App Store or Google Play. Then restart your device completely — not sleep, a full restart. This clears stuck sessions and gives the client a clean slate for the next teleport attempt.
- Clear the Roblox cache and check your connection. Close Roblox fully. On Windows, press Win + R, type
%temp%\Roblox, and press Enter, then delete everything inside. On mobile, open Settings, find Roblox in your app list, and clear its cache (cache only, so you stay signed in). Then stabilize your connection: reboot your router and play on a wired or strong Wi-Fi signal, since an unstable connection can make a teleport request time out and surface as error 773. - Try again later or ask the game creator to allow teleports. If the error appears only in one experience, the restriction is developer-side: the destination place may be private, under review, or have third-party teleports disabled in Game Settings > Security — only the game's creator can change that. Message the creator or check the experience's group or Discord for announcements. If it happens everywhere, wait 30–60 minutes and retry, then contact Roblox support if it persists for hours.
Did this fix it? Quick checklist
- You can teleport between games or servers without the 773 message
- Only your current device is signed into Roblox (check Settings > Security > Active Sessions)
- The destination experience is public, available, and rated for your account's age
- Roblox is updated to the latest version and your connection is stable
If error 773 keeps appearing in only one experience after all six steps, the restriction is with that game — a private place, an expired server link, a place under review, or third-party teleports disabled in the creator's settings. Only that game's developer can change those; look for announcements on the experience's group or Discord, and ask the owner for a fresh private-server link if you were using one. If teleports fail in every experience, give it an hour in case it's a platform issue, then contact Roblox support with the exact times and games — a persistent, account-wide block points to something on their end.
Frequently asked questions
What does Roblox error 773 mean?
Error 773 means a teleport failed because the destination place is restricted. The full message reads "Teleport Failed: Attempted to teleport to a place that is restricted (Error Code: 773)." Roblox blocked the teleport because you can't access the destination — it's private, under review, age-restricted, full, or temporarily unavailable.
What is the difference between Roblox error 769 and 773?
Error 769 is the generic "teleport failed for an unknown reason" code — the transfer broke and Roblox couldn't say why. Error 773 is specific: it tells you the destination place was restricted. If you see 773, the problem is access or permissions on the destination, not a mystery client failure.
Can my Roblox account age cause error 773?
Yes. Roblox blocks under-13 accounts from teleporting into experiences with 13+ age ratings, and that block shows as error 773. If you're on a U13 account, either use a destination rated All Ages or play from a 13+ account.
Why does error 773 happen when I'm logged in on two devices?
A double-login session confuses the teleport system — Roblox can't tell which session should receive the teleport and restricts the request, triggering error 773. Sign out of all sessions under Settings > Security > Active Sessions, keep only your current device logged in, and try again.
What should I do if error 773 happens in only one game?
Then the restriction is developer-side and you can't fix it yourself. The destination place may be private, under review, have expired private-server links, or have third-party teleports disabled in Game Settings > Security. Only the game's creator can fix that — check the experience's group or Discord for announcements.