Skip to main content
All CollectionsError Messages & How To Fix Them
Google Connection Error Codes Explained
Google Connection Error Codes Explained

If you receive an error while connecting an inbox, here are a few troubleshooting steps to perform in order to get your inbox connected.

Lucia Matúšková avatar
Written by Lucia Matúšková
Updated over a week ago

If you receive an error while connecting an inbox, here are a few troubleshooting steps to perform to get your inbox connected.

If you are attempting to connect a Google Workspace account to the platform, you may come across a few errors preventing you from getting your inbox connected. Let's go over all the specific types of errors that can get thrown and how you can resolve them.

To learn how to get your account set up for Warmup Inbox before performing these troubleshooting steps, please follow our guide on how to do this here.

Note: When performing these troubleshooting steps, we strongly suggest users open up an incognito browser window and sign into the Google account you are attempting to connect to the platform, then perform these troubleshooting steps. The direct links we provide to these Google settings pages can sometimes auto-redirect to other Google accounts you are signed into so this prevents you from accidentally enabling these settings under a different account.

SMTP error Error: Invalid login: 535-5.7.8 Username and Password not accepted. Typically, a 535-5.7.8 error indicates that you did not enable Less Secure Apps on the inbox side of your email address. If you see this error, navigate to this link below and double-check that this setting is enabled, and try connecting again.

If this setting is enabled under the inbox and you are still experiencing this same issue, double-check you are utilizing the correct login information for this Google inbox.

You might also need to add the inbox using the SMTP/IMAP option instead of the Google Workspace integration.

Error: Your account is not enabled for IMAP use. Please visit your Gmail settings page and enable your account for IMAP access. (Failure)

If you receive this error while connecting an inbox, it indicates that you did not enable IMAP access under this inbox, and we cannot connect to your account. To resolve this, all you need to do is enable IMAP access under the settings of this inbox. To do this, please refer to our official Google setup guide found here.

534-5.7.14 Please log in via your web browser and then try again.

If you receive this error when attempting to connect your inbox to the platform, learn how you can resolve it.

This error will occasionally get thrown by Google accounts for a variety of reasons. In most cases, this error simply will get thrown when Google wants to verify that the owner of this inbox is the one attempting to connect this inbox to the platform.

To resolve this issue, you will need to:

1. Log into your Google account and navigate to the app password section: Go to your Google Account and Select Security Under "Signing in to Google," select 2-Step Verification At the bottom of the page, select App passwords

2. Delete the old app password for the Warmup Inbox, create a new one, and name it Warmup Inbox

3. Copy-paste this new app password to your inbox settings in your Warmup Inbox account.

Click on the affected inbox - settings - connection.

Paste the new app password into the SMTP password field and hit save.

Then paste the new app password into the IMAP password field and hit save.

4. Once done, you can unpause your inbox.

SMTP error Error: Invalid login: 534-5.7.9 Application-specific password required. If you receive this error when attempting to connect your inbox to the platform, learn how you can resolve it.

If you are receiving this error, it indicates that you might not have the 2-factor authentication enabled under the inbox you are attempting to connect to and that you are not using the App password to get it connected to the platform.

Instructions on how to turn on 2FA under your Google account can be found in this article.

To create an app password, please follow our guide on how to do this here.

Did this answer your question?