Errors while connecting an account
Every error you can see while connecting Google, Microsoft, a mailbox, iCloud, Zendesk, WooCommerce, Magento or Mailchimp, and how to fix it.
Plugsight checks every new connection before saving it: it signs in, or tests the password or keys with the service. If that fails, nothing is saved and you see an error. Find it below.
Failed attempts also appear in Activity, starting "Connecting … failed:", with the full message.
Signing in with Google, Microsoft or Zendesk
These messages appear after the provider's sign-in page sends you back to Plugsight. "Google", "Microsoft" or "Zendesk" is filled in.
You didn't allow access in Google. Click Connect again and allow it, ticking every permission box.
What it means: you clicked Cancel or Deny on the provider's page, or closed it.
How to fix it: start again from the connector and, on the provider's page, allow access. On Google's page, tick every permission box: unticked boxes mean the connection can't work.
Your organisation needs an administrator to approve Plugsight in Microsoft. Ask your IT admin, or if you are the admin, sign in and consent on behalf of the organisation.
What it means: your company restricts which apps staff can connect, and Plugsight hasn't been approved yet.
How to fix it: ask your IT admin to approve Plugsight. If you are the admin, connect again and tick Consent on behalf of your organisation when Microsoft asks.
The Google sign-in expired before it finished. Click Connect and sign in again.
Also: The sign-in didn't finish. Click Connect and sign in again.
What it means: the sign-in wasn't completed in time.
How to fix it: start again from the connector, and finish the provider's pages in one go.
Google sign-in didn't finish. Click Connect to try again. (Google said: …)
What it means: the provider ended the sign-in with an error of its own, shown in brackets.
How to fix it: try again. If it repeats, the provider's message in brackets usually says why; send it to info@plugsight.app if it doesn't make sense.
Your session changed during sign-in. Please try again.
What it means: while you were on the provider's page, you signed out of Plugsight or signed in as someone else in another tab.
How to fix it: make sure you're signed in to the right Plugsight account, then connect again.
We couldn't read this account's email address. Sign in again, choosing an account that has an email address.
What it means: the Google or Microsoft account you picked didn't give an email address.
How to fix it: connect again and choose a different account, one with an email address.
"Google hasn't verified this app"
What it means: Google shows this warning while it reviews new apps. It doesn't mean anything is wrong.
How to fix it: on Google's page, click Advanced, then Go to Plugsight (unsafe), and carry on.
Google returned no refresh token. Remove the app's access in your Google account and try again.
What it means: Google didn't give Plugsight lasting access to the account.
How to fix it: remove Plugsight's access in your Google account, then connect again.
Gmail access wasn't granted. Tick the Gmail permission and try again.
Also, for other Google services: … access wasn't granted. Tick the permission and try again., with the service's name (Google Analytics, Search Console, Google Ads, Calendar, Contacts and so on).
What it means: on Google's permission page, the box for this service was left unticked.
How to fix it: connect again and tick the permission box Google shows. The Plugsight page before Google's names the exact permission to tick.
… is a Google account without a Gmail inbox. If your email is in Outlook or Microsoft 365, connect it with Outlook instead; for other providers, use "Connect a mailbox".
What it means: this Google account has no Gmail. Your email lives somewhere else.
How to fix it: connect the mailbox with the right connector: Outlook for Microsoft 365. For other providers, open the Connector catalog, type your email address in the box "Or type an email address to detect its provider" and click Detect.
That Google service isn't recognised. Pick one from the list of connectors.
What it means: the page was opened from an old or edited link.
How to fix it: go back to the Connector catalog and pick the Google service again.
Problems: Google Ads: the Google Ads developer token only has test access, so real ad accounts are blocked. …
What it means: the connection was saved, but Google Ads refused to list real ad accounts. The message after "Problems:" names each service that failed and why.
How to fix it: the Google Ads developer token belongs to the Plugsight service, not to your account, so contact info@plugsight.app about this one. For other services named after "Problems:", open Connections, click Show sites & accounts on the account and then Refresh list.
Google Ads isn't set up on this server (no developer token). Search Console and Analytics still work.
Also: Microsoft Advertising isn't set up on this server (no developer token).
What it means: this Plugsight service can't reach that ad platform yet.
How to fix it: nothing you can change. Contact info@plugsight.app.
… didn't answer: … Try Refresh list below; if it keeps failing, reconnect this account.
What it means: on Connections, when you open a marketing account's sites and accounts, one Google or Microsoft service didn't answer.
How to fix it: click Refresh list. If it keeps failing, click Reconnect on the account.
This login doesn't reach anything yet.
What it means: the Google or Microsoft login you used has no sites, properties or ad accounts in that service.
How to fix it: connect again with the login that has access, or give this login access at the provider. Then click Refresh list.
Microsoft (Outlook and Microsoft Advertising)
Microsoft didn't grant lasting access. Remove Plugsight at myapps.microsoft.com, then connect again.
What it means: Microsoft didn't give Plugsight access that lasts beyond the sign-in.
How to fix it: open myapps.microsoft.com, remove Plugsight, then connect again.
Outlook isn't set up on this server yet.
Also: Choose Outlook Calendar or Outlook Contacts. (from an old or edited link).
What it means: this Plugsight service can't connect Outlook right now, or the link was wrong.
How to fix it: pick the connector again from the Connector catalog. If Outlook still isn't available, contact info@plugsight.app.
Mailboxes with a password (IMAP)
For Gmail with an app password, iCloud Mail, Yahoo, AOL, Zoho and other mailboxes. For problems making the app password itself, see App password problems.
Could not connect: … Check the password; most providers need an app password, not your normal one.
What it means: the mail server refused the login. The part after "Could not connect:" is the mail server's own message.
How to fix it:
- Make sure you pasted an app password, not your normal password. Most providers require one.
- Make sure the email address is exactly the mailbox the app password belongs to.
- If you made the app password a while ago, make a new one: it may have been deleted.
- Some providers need IMAP access switched on in their settings first, for example Zoho, GMX, WEB.DE, Yandex, Seznam and many others. The connect page for your provider says what to switch on.
Could not connect: …
Without the password hint, the mail server refused for another reason, given in its message.
How to fix it: read the mail server's message. For "Other IMAP" mailboxes, check the server names and ports with your provider.
Couldn't find imap.example.com. Check the server name for typos.
What it means: the server name doesn't exist.
How to fix it: check the spelling of the IMAP (and SMTP) server name.
imap.example.com refused the connection. Check the port number, or whether the server allows this kind of access.
What it means: the server exists but refused on that port.
How to fix it: check the port. IMAP is usually 993, and SMTP 465 or 587. Also check the provider allows IMAP access.
Couldn't reach imap.example.com in time. Check the server name and port, then try again.
What it means: the server didn't answer.
How to fix it: check the server name and port, then try again.
The secure connection to imap.example.com failed. Check the port and whether it expects SSL/TLS.
What it means: the server's secure connection didn't work on that port.
How to fix it: use the port that matches SSL/TLS (usually 993 for IMAP).
We couldn't detect this provider's settings. Enter its IMAP (and SMTP) details below.
What it means: Plugsight couldn't work out your provider from the email address.
How to fix it: enter the incoming (IMAP) and outgoing (SMTP) server details from your provider's help pages.
IMAP server is required.
What it means: the Other IMAP form was sent without an IMAP server name.
How to fix it: fill in the IMAP server.
Proton Mail only works through Proton Mail Bridge running on your own computer, so it can't be connected to a cloud service like this one.
What it means: Proton Mail can't be connected to Plugsight.
How to fix it: there's no workaround.
Enter the password.
Also: Enter a valid email address., Enter a full email address. and Unknown provider.
What it means: a field is empty or isn't valid.
How to fix it: fill it in and try again.
iCloud Calendar and Contacts
Apple didn't accept that Apple ID and password. Use an app-specific password (account.apple.com → Sign-In and Security → App-Specific Passwords), not your normal password.
What it means: Apple refused the login. Apple only allows app-specific passwords here.
How to fix it: create an app-specific password at account.apple.com → Sign-In and Security → App-Specific Passwords, paste it, and use your Apple ID email address.
Enter the app-specific password.
What it means: the password box is empty.
How to fix it: paste the app-specific password.
Pick iCloud Calendar or iCloud Contacts from the catalog.
What it means: the page was opened from an old or edited link.
How to fix it: go back to the Connector catalog and pick iCloud Calendar or iCloud Contacts.
Zendesk
Enter your Zendesk address, like yourcompany.zendesk.com.
What it means: the address box is empty or isn't a Zendesk address.
How to fix it: type the part of your Zendesk address before .zendesk.com, as in your browser's address bar when you use Zendesk.
Zendesk sign-in failed: …
What it means: connecting with Sign in with Zendesk didn't finish. The rest of the message says why, using the sign-in messages above.
How to fix it: click Continue with Zendesk again, sign in as an agent or admin, and click Allow.
That Zendesk user isn't an agent. Use an agent or admin account.
What it means: you signed in with a Zendesk customer (end-user) account. Plugsight needs an agent.
How to fix it: sign in to Zendesk as an agent or admin, then connect again.
Could not connect: Zendesk rejected the credentials. Check the agent email and API token. Zendesk no longer issues new tokens, so use Sign in with Zendesk if this one was removed.
What it means: the API token or the agent email is wrong, or the token was switched off.
How to fix it: use Sign in with Zendesk instead. Zendesk stopped creating new API tokens on 27 October 2026 and switches existing ones off on 30 April 2027. Tokens unused for 30 days already stop working, and Zendesk accounts created since 28 July 2026 can't use tokens.
Sign in with Zendesk isn't set up on this server yet. If you already have a Zendesk API token, use that.
What it means: this Plugsight service can't use Zendesk sign-in right now.
How to fix it: connect with an API token that's still active, or contact info@plugsight.app.
Enter the API token.
What it means: the token box is empty.
How to fix it: paste the token, with the email of the agent the AI should act as.
WooCommerce
Enter your store's web address, like shop.example.com.
What it means: the address box is empty or isn't a web address.
How to fix it: type the address customers visit, like shop.example.com. Your store must use https.
That address isn't a public website. Enter your store's web address, like shop.example.com.
What it means: the address points to a private network, not a public website.
How to fix it: use your store's public address.
shop.example.com didn't answer like a WooCommerce store (HTTP …). Check the address, and that WooCommerce is installed and its REST API isn't blocked by a security plugin.
What it means: the site answered, but not as a WooCommerce store would.
How to fix it: check the address, check WooCommerce is installed and active, and check no security plugin or firewall blocks the WooCommerce REST API.
The store wasn't connected: the approval was cancelled. Click Connect and choose Approve.
What it means: you didn't click Approve on your store's "Plugsight would like to connect" page.
How to fix it: click Continue to my store again and click Approve.
shop.example.com approved Plugsight but couldn't send us the keys (some hosts block this). Use "Connect with REST API keys" below instead.
What it means: your web host blocked the store from sending the keys to Plugsight.
How to fix it:
- Open Connect with REST API keys instead on the WooCommerce connect page.
- In WordPress, go to WooCommerce → Settings → Advanced → REST API and click Add key.
- Describe it as "Plugsight", pick your user, set Permissions to Read and click Generate API key.
- Copy both keys (WooCommerce shows the secret once) and paste them into Plugsight.
The store didn't accept these keys. Copy both again in full from WooCommerce → Settings → Advanced → REST API, with Read access.
What it means: the consumer key or secret is wrong, incomplete or deleted.
How to fix it: create a new read-only key and paste both parts in full.
The store's keys don't allow this. Reconnect and approve read access, or check a security plugin isn't blocking the WooCommerce API.
What it means: the store accepted the keys but refused to share orders with them.
How to fix it: make sure the key has Read permission, and that no security plugin blocks the WooCommerce REST API.
The consumer key starts with ck_.
Also: The consumer secret starts with cs_., Enter the consumer key., Enter the consumer secret. and Enter your store's web address.
What it means: a key was pasted into the wrong box, cut short, or left empty.
How to fix it: paste the consumer key (starts with ck_) and the consumer secret (starts with cs_) into their own boxes.
Couldn't reach the store: …
Or one of the network messages: "Couldn't find …", "… refused the connection", "Couldn't reach … in time", "The secure connection to … failed".
What it means: Plugsight couldn't reach your store's website.
How to fix it: check the address, and that your site is online and uses https.
Magento / Adobe Commerce
shop.example.com didn't answer like a Magento store (HTTP …). Check the address, and that the REST API isn't blocked by a firewall or security module.
What it means: the site answered, but not as a Magento store would.
How to fix it: check the address, and check no firewall or security module blocks Magento's REST API.
The store didn't accept these keys. Copy all four again from the integration's details in Magento admin, and check the integration says Active.
What it means: one of the four keys is wrong, or the integration isn't active.
How to fix it: in Magento admin, go to System → Extensions → Integrations. Check the Plugsight integration is active (click Activate, then Allow, if not). Copy all four keys again with Edit → Integration Details.
The integration isn't allowed to read this. In Magento admin, edit the integration's API resources to include …, save, then reauthorize it.
What it means: the integration can't read orders, products or customers.
How to fix it: edit the integration, open the API tab, set Resource Access to Custom and tick Sales → Operations → Orders, Catalog → Inventory → Products and Customers → All Customers. Save, reauthorize it, then copy the new keys into Plugsight.
The consumer key is 32 letters and numbers. Copy it from the integration's details.
The same message appears for the consumer secret, access token and access token secret, along with Enter the consumer key. and so on when a box is empty.
What it means: a key is incomplete or in the wrong box.
How to fix it: copy each of the four keys into its matching box.
Mailchimp
That isn't a Mailchimp API key. It ends with a dash and letters and numbers, like -us21.
Also: Enter your Mailchimp API key.
What it means: what you pasted isn't a complete Mailchimp API key.
How to fix it: copy the whole key, including the ending like -us21.
Mailchimp didn't accept that API key. Check you copied all of it, including the ending like -us21, and that it hasn't been deleted.
What it means: Mailchimp refused the key.
How to fix it: create a new key in Mailchimp (API keys → Create A Key → Generate Key) and paste it. Mailchimp shows the key once.
Couldn't reach Mailchimp: …
What it means: Mailchimp didn't answer.
How to fix it: try again in a few minutes.
Any connector
That didn't work. Refresh the page and try again; if it keeps happening, contact us.
Also: The server didn't answer properly (error …). Wait a moment and try again.
What it means: something unexpected went wrong.
How to fix it: refresh the page and try again. If it keeps happening, email info@plugsight.app.
Your Free plan includes 2 connections. Upgrade to Pro for 10.
Or another plan limit message. See Plans and limits.
Marketing and analytics connectors (Google Ads, Microsoft Ads, Search Console, GA4, Tag Manager, YouTube, Merchant Center) are on the Pro plan. Upgrade under Billing to connect them.
See Plans and limits.