Two-factor authentication
A password alone can leak: it gets reused on another site, typed into a fake login page or exposed in someone else’s data breach. Your dashboard holds your balance, your proxy credentials, your API token and your billing details, so whoever has your password has all of that. Two-factor authentication (2FA) adds a second step to every sign-in to app.rayobyte.com, such as a code from your phone. With it on, a stolen password is not enough to get in.
It is off until you turn it on. Turn it on if you can.
The basics
Section titled “The basics”Turn it on
Section titled “Turn it on”- Open Security Settings from your profile menu in the dashboard, or go to app.rayobyte.com/security.
- On the Two-factor authentication card, select Turn on.
- Pick a method:
- Authenticator app (recommended): a free app on your phone, such as Google Authenticator or Microsoft Authenticator, shows a new 6-digit code every 30 seconds.
- Email code: we email you a 6-digit code at every sign-in.
- Passkey: you sign in with your fingerprint, face or phone screen lock instead of typing a code.
- Confirm it’s you with a code or a passkey. We ask before every change to two-factor authentication.
- Finish the method. For the app, scan the QR code and type the code the app shows.
- Save your recovery codes, then select Finish.
Save your recovery codes
Section titled “Save your recovery codes”When you turn it on, we show 10 recovery codes, once. Each one signs you in a single time if you lose your phone or can’t get a code. Download them or copy them somewhere safe that is not your email.
Signing in
Section titled “Signing in”After your password (or Google, Microsoft or GitHub), the dashboard asks for the second step. Type the code from your app or your email, or use your passkey.
Sign in with a passkey on the log-in page needs no code, whatever method you picked, because a passkey already counts as two steps: the device that holds it, and your fingerprint, face or screen lock.
If you lose your phone
Section titled “If you lose your phone”Sign in with one of your recovery codes and set up the app again. If you have no recovery codes and no passkey, ask [email protected] to reset two-factor authentication. A reset is not instant, and it replaces your API token, so scripts that use the token stop working until you update them. The steps are under Lost your phone, passkey or email.
In detail
Section titled “In detail”Which method to pick
Section titled “Which method to pick”| Method | What every sign-in asks for |
|---|---|
| Authenticator app (recommended) | The 6-digit code from an app on your phone |
| Email code | A 6-digit code we email to your sign-in address |
| Passkey | Your fingerprint, face or screen lock, with no code to type |
Email codes protect you if someone learns your password. They don’t protect you if someone gets into your email, because a password reset goes to the same inbox. Use the authenticator app or a passkey if you can.
Setting it up, in full
Section titled “Setting it up, in full”These are the same steps as above, with what each screen asks for.
- On the Two-factor authentication card, select Turn on.
- Pick a method and select Continue.
- Confirm it’s you, then finish the method:
- Authenticator app: confirm with a code or a passkey. Scan the QR code with the app, or enter the key shown under “Can’t scan it?”. Type the 6-digit code the app shows and select Turn on.
- Passkey: confirm with your passkey. If you have none yet, select Add a passkey first and follow your browser’s prompt.
- Email code: confirm with a code we email to you, so we know your inbox gets our mail.
- Select Copy codes or Download for your recovery codes, tick I saved my recovery codes and select Finish.
Turning it on signs you out on every other device and browser.
“That code didn’t match” while setting up the app usually means the phone’s clock is wrong. Check it and type the newest code. After 10 wrong codes in an hour, start the setup again an hour later.
Email codes cannot be turned on for an address we can’t deliver to. Use an authenticator app, or change your sign-in email first in the Sign-in email card on the same page.
Recovery codes
Section titled “Recovery codes”Each recovery code looks like k7m3n-9pqr4 and works once. On the code screen, select Can’t get a code?
then Use a recovery code. Keep the codes somewhere only you can reach: a recovery code is for the day you
can’t get into your phone or your email.
The card shows how many codes you have left. New recovery codes makes a new set of 10, and the old set stops working at once.
Which sign-ins ask for it
Section titled “Which sign-ins ask for it”With two-factor authentication on, every sign-in asks for the second step:
- your email address and password
- Google, Microsoft or GitHub
- the temporary password from Forgot password
- team members, each on their own sign-in
Signing in from a browser you have used before still asks for the second step. A code pasted with a space or a dash in the middle works.
To connect Google, Microsoft or GitHub to your account for the first time, sign in once with your password and the second step. After that, you can sign in with Google, Microsoft or GitHub.
When the emailed code doesn’t arrive
Section titled “When the emailed code doesn’t arrive”Check the inbox of your sign-in email, the address shown on the Sign-in email card. Then select Resend when its countdown ends, and use the newest code.
If the screen says we can’t deliver email to your address, or that you’ve asked for many codes today, no new code is coming. Use a recovery code or a passkey.
Too many wrong codes
Section titled “Too many wrong codes”Wrong codes slow sign-in down, to protect you from someone guessing:
- One sign-in attempt accepts up to 5 codes. After that, sign in again.
- After 10 wrong codes in 15 minutes, the screen asks you to wait and says for how long.
- After many wrong codes in a row, sign-in codes pause for 24 hours and we email you, because someone else may know your password. After the pause, codes come back slowly, one try an hour, until you type a correct one.
- If wrong codes go on after that, codes stop until you sign in with a recovery code or a passkey.
A passkey works through all of these. A recovery code works through the pause and the stop, but counts toward the first two limits. Signing in with either turns codes back on. Change your password once you’re in. If you can’t sign in at all, contact [email protected].
Change the method or turn it off
Section titled “Change the method or turn it off”Every change below asks you to confirm it’s you first, with your current method, a passkey or a recovery code.
- Set up on a new phone moves the authenticator app. Scan the new QR code, type a code from the new phone and select Use this phone. Codes from the old phone stop working, and your recovery codes stay the same.
- Use email codes instead, Use an authenticator app instead and Use a passkey instead switch the method and keep your recovery codes. Switching to email codes also asks for a code we email you.
- Turn off removes two-factor authentication, and your recovery codes stop working.
You can make 6 changes in 24 hours: turning it on, switching methods, a new phone and new recovery codes each count. Turning it off is never limited.
While two-factor authentication uses a passkey, your last passkey cannot be removed. Add another one first, switch methods, or turn two-factor authentication off.
Lost your phone, passkey or email
Section titled “Lost your phone, passkey or email”Sign in with a recovery code, then use Set up on a new phone, add a new passkey or make New recovery codes. A passkey on another device works too.
With no recovery code and no passkey, contact [email protected]. When our support team is asked to reset two-factor authentication, we email your sign-in address with the date the reset happens and a link to cancel it. If you are still signed in anywhere, the Security settings page shows the request with Cancel this request. If you didn’t ask for it, cancel it.
A reset turns two-factor authentication off and removes your authenticator app and recovery codes. It also signs you out on every device and browser and replaces your API token: copy the new one from the API tab of the Statistics page and update your scripts. If you used a passkey as your method, your passkeys are removed too. We email you a list of what was removed.
Emails we send
Section titled “Emails we send”We email you about every change to two-factor authentication:
| When | Subject |
|---|---|
| A sign-in needs your emailed code | Your Rayobyte sign-in code |
| You turn it on, switch methods or set up a new phone | Two-factor authentication is on for your Rayobyte account |
| You turn it off | Two-factor authentication is off for your Rayobyte account |
| A recovery code is used (with how many are left) | A recovery code was used on your Rayobyte account |
| You make new recovery codes | New recovery codes for your Rayobyte account |
| Codes are paused, or stopped, after wrong codes | Sign-in codes are paused (or stopped) on your Rayobyte account |
| Support is asked to reset it | A request to reset two-factor authentication on your Rayobyte account |
| Support reset it | Two-factor authentication was reset on your Rayobyte account |
If you get one of these for a change you didn’t make, contact [email protected].
Team members
Section titled “Team members”Two-factor authentication protects one person’s sign-in. Each person on an account turns it on for themselves, and the owner cannot turn it on for a member. See Team members.
Your API token
Section titled “Your API token”The API token is not covered by two-factor authentication: anyone who has the token can use the API. Keep it secret, and replace it on the API tab of the Statistics page if it leaks. With two-factor authentication on, we ask you to confirm it’s you before we show the token.
For developers: an API token cannot change two-factor authentication. Those calls answer
409 SESSION_REQUIRED. Sign in to the dashboard to make the change.
Was this page helpful?
Thanks. That helps us fix it.