Contact this documentation site

There is a single contact point for this site, and it handles everything: corrections, broken pages, and reports about mirrors pretending to be this documentation. A short message with a URL in it is more useful than a long one without.

The address

Email: security@solaraget.com — the only contact address for this site. Anything claiming to be official support on another domain, in a chat server or in a direct message is not connected to this documentation.

Replies are not instant and there is no ticket number to track. Reports that include a URL and a clear description of what you expected are answered fastest, because they can be reproduced without a follow-up exchange.

What to write about

Documentation errors are the most valuable thing you can send: a step that no longer matches what Windows or the Roblox client does, a stale version reference, a contradiction between two pages, or a link that leads nowhere. Reports about a site that copies this documentation and serves a different file are also worth sending, and are treated as security reports.

Genuine security issues with this site — anything that would let a visitor be redirected, served altered content or shown something that did not come from here — should go to the same address with as much technical detail as you can include.

What this site cannot help with

Some requests arrive regularly and there is no polite way to answer them other than plainly. This site cannot recover a Roblox account, reset a password, restore access or influence a moderation decision in any direction, because it has no relationship with Roblox Corporation and no access to any account. Appeals belong with Roblox support, and only there.

It also does not write, supply, review on request or troubleshoot individual Lua scripts, and it does not have a mobile build to send you — there is no APK and no iOS version in this line, as the FAQ explains. Messages asking for any of these will simply not have an answer.

What to include so a report is actionable

For anything that looks like a bug on the site or a problem with the documented steps, the details below turn a vague report into something reproducible. Without them, most messages end in a request for more information.

The full URL of the page you were on, or the URL of the suspicious mirror.
Your Windows version and build number, for example Windows 11 24H2.
Whether Roblox was fully loaded — able to move your character — at the moment of the problem.
Whether the application was started with administrator elevation.
The exact error text, copied rather than paraphrased.

Nobody here will ever ask for your Roblox password. Not for support, not to verify a report, not for any reason at all. Any message that asks you for a Roblox password, a login code, a session cookie or a two-step verification code is not from this site, regardless of the name or address it appears to come from.

Try the self-service pages first

There is no phone line and no live chat, so an answer by email will always be slower than the page that already covers your question. Setup failures are documented in troubleshooting, security prompts and download verification in safety, and the short answers to the recurring questions in the FAQ.