You can log in to the DigitalOcean Control Panel in one of three ways:
Your username is the email you used to sign up for your DigitalOcean account.
If you cannot sign in to open a ticket, you can send a support request through the Can’t sign in form.
If you have lost access to the email account you use with your DigitalOcean account, first try restoring access to your email account by contacting your email administrator, renewing your domain’s registration, or setting up another email server.
If you have gone through these steps and cannot regain access to the email account, contact our support team for help.
Email generally arrives quickly. If you haven’t received email within a few minutes:
support.digitalocean.comto your email whitelist.
If you still don’t have a reset email, contact our support team.
If you lost the SSH key you use for your Droplet, follow the lost SSH key instructions to regain access. If you lost or don’t know the root password for the Droplet, you can reset the Droplet’s root password via the control panel. For more SSH troubleshooting tips, see our SSH troubleshooting guide.
To access your account settings, click the profile icon in the top right of the control panel. In the menu that opens, click Manage Account to go to your My Account page. In the Sign-in method section, click Change. This opens a pull-down menu with three options: Change email, Use Google, and Use GitHub.
To log in with an email and password, click Change email. This opens two text fields for a new email address and a password confirmation. Fill in both fields and then click Submit Change. A confirmation is sent to your new email address to confirm the change. The change does not take effect until you click the link in the confirmation email.
You can alternatively change to Google or GitHub SSO by clicking Use Google or Use GitHub respectively.
When you create a DigitalOcean account using your email and password, we protect it with device verification by default. This only applies to email and password sign ins without 2FA and does not apply to GitHub or Google SSO.
Each time you sign in from a new location using a new device or a different web browser, we email an authorization code to the email address you use to sign in or send an SMS to the phone number you provided.
This process means that a bad actor would need to have compromised your device or email account as well as your DigitalOcean account to log in. This increases the difficulty for would-be attackers and provides you with notification if someone is trying to access your account.
If you were expecting an email with the code, check your spam folder. To be sure you receive these and other DigitalOcean emails directly in the future, add
*.digitalocean.com to your email whitelist.
If you were expecting an SMS message with the code, ensure that you aren’t blocking communications from us and that you have entered the correct phone number in your profile’s Security page.
If you still aren’t receiving your verification codes, open a support ticket with your device details in the description. To get your device details, visit whatsmybrowser.org and click Copy, then paste the URL in the ticket description.
You may be required to enter a verification code each time you sign in if you use an ad blocker.
To allow your browser to be recognized, you can whitelist the verification domain,
siftscience.com or pause ad blocking on
You may be asked to verify your browser from a trusted location and device if you have deleted cookies for digitalocean.com or you have disabled cookies entirely.
You can disable device verification by enabling two-factor authentication (2FA) or by authenticating with Google or GitHub.
If you receive a verification code email from DigitalOcean, somebody has successfully entered your email address and DigitalOcean account password.
We strongly recommend that you reset your DigitalOcean account password to prevent unauthorized access and update any other accounts which use the same email address and password combination.
If you receive an error on the DigitalOcean login screen that prevents you from signing into your account, open a support ticket with your device details in the description. To get your device details, visit whatsmybrowser.org and click Copy, then paste the URL in the ticket description.
If you’ve successfully entered your username and password and are experiencing an issue with two-factor authentication, you can disable 2FA using your backup method (backup codes or SMS).
Search your computer for the backup recovery codes text file, which by default would be called
digitalocean_backupcodes.txt. If you find that file, use one of the codes by logging in to the control panel and clicking Enter a recovery code at the bottom of the Two-factor authentication screen. Remember that if you successfully use the code, you cannot use it again, so you may want to mark it as used or delete it from the file.
Log in to the control panel and enter your account credentials. click Send an SMS instead at the bottom of the Two-factor authentication screen.
You are prompted to enter a verification code, which you receive via SMS at the phone number you entered when you configured SMS as your backup method.
See How to Manage Two-Factor Authentication more information on 2FA, including how to update your device.
If you can’t use your backup method to access your account, our support team can help. Open a ticket from the email associated with your DigitalOcean account and let them know you need to reset your backup method.
They will need additional information to verify that you are the account owner, so be prepared with a photo of your government-issued ID (e.g. passport, driver’s license, military ID). The name on ID in the photos must match the name for the account information that we have on file.
If you are an existing customer and would like to use a GitHub or Google account to authenticate, navigate to your Account profile. In the Sign-in method, open the Change menu and select Use Google or Use GitHub. You can only enable one sign-in method at a time.
Follow the prompts to authorize your account. Next time you sign in, use the new sign-in method.
If you can’t regain access to your GitHub account, submit a support ticket. Our support team will guide you through verifying your identity and setting a new authentication method for your account.
If you have lost access to your Google account, first try to restore your access to that account using Google’s account recovery procedures.
If you can’t regain access to your Google account, submit a support ticket. Our support team will guide you through verifying your identity and setting a new authentication method for your account.
If you want to switch from SSO to a username and password for your DigitalOcean account, navigate to the Profile page of your account. In the Sign-in method section, open the Change dropdown menu and select Use email and password, then confirm the change. The next time you log in, use your email address and password.
If you originally signed up using Google SSO, reset your password after disabling Google SSO to set a password for your account.
You cannot switch directly between accounts from the same provider. Instead, you’ll need to switch to a different method, then switch back. For example, if you want to use a different Google account for SSO, change to either email and password or GitHub. Then, change back to Google and select the account you want.