This document provides an overview of common authentication issues that users might encounter when connecting their Microsoft accounts to Nylas.
You may encounter these errors on the auth logs page of your developer dashboard from time to time.
Sometimes a user will receive an invalid password error even if they type the correct password in. If you’re sure your password is correct, there could be a couple other things that cause you to receive an Invalid Credentials error:
Note about VPNs
If a user's mail server is behind a VPN, firewall or has other strict MDM policies in place we might not be able to support connecting their account.
- If you have two-factor authentication enabled for your email account you might need to generate an app specific password
- It could be that Autodiscovery could be trying to login to the wrong server
- Ask your email administrator what server and port information should be used to connect. Then, try logging in again by adding these settings under advanced settings.
- Make sure you aren’t logging in with an email alias (exchange). You must login to the actual account
- Make sure mobile device provisioning is enabled and that ActiveSync connections are allowed
- Check that Nylas devices aren’t quarantined or blocked
- See Suggested Office 365 Settings
- See Checking for quarantined EAS devices
This indicates that a temporary error occurred on the mail server when we tried to authenticate the user's account. In most cases, retrying the request should resolve the issue.
Nylas was unable to automatically determine the correct connection settings using Autodiscovery. The user should reach out to their mail administrator and ask for the correct connection settings they can use to manually connect.
Nylas was unable to connect to the server settings that were provided. The user should reach out to their mail administrator and ask for the correct connection settings they can use to manually connect.
Updated 3 years ago