Why do I get an error message on start up?

Just installed eM Client and am so happy to have found an Outlook alternative that works with gmail! It seems to be functioning fine, but whenever I open the application, I get an error message saying “Connecting to failed.” Email is coming in and going out. What’s up?

Hello Julia, sorry to see this, can you please make a screenshot of the error you’re experiencing? Also when it occurs, please switch to the “Log” tab, copy the content of the Log and submit it to us here for more information.

What version of eM Client are you currently using on your computer, can you please check the exact release number in Help > About?

Screen shot and Log copied below. Running release 6.0.22344.

9:33:15 AM Online state: changed to online due to NetworkAvailability

9:33:15 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/

9:33:15 AM [email protected] [GData]  Synchronizing folder list

9:33:15 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/

9:33:37 AM [email protected] [XMPP]  MailExceptions.ConnectionException:

9:33:37 AM (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [2607:f8b0:4002:c07::7d]:5223)

9:33:37 AM [email protected] [GData]  Synchronizing folder list

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/Inbox

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/[Gmail]

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/Inbox

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/Junk E-mail

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/[Gmail]/Trash

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: For folder [email protected]/[Gmail]

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing messages: For folder [email protected]/Inbox

9:33:37 AM [email protected] [IMAP]  Synchronizing subfolders: Done

9:33:37 AM [email protected] [IMAP]  Synchronizing messages: For folder [email protected]/Inbox

9:33:38 AM [email protected] [IMAP]  Synchronizing messages: For folder [email protected]/Inbox

9:33:38 AM [email protected] [IMAP]  Synchronizing messages: For folder [email protected]/Inbox

9:33:38 AM [email protected] [IMAP]  Synchronizing messages: Done

9:33:38 AM [email protected] [IMAP]  Synchronizing messages: For folder [email protected]/Inbox

9:33:38 AM [email protected] [IMAP]  Synchronizing messages: For folder [email protected]/Inbox

9:33:38 AM [email protected] [IMAP]  Synchronizing messages: Done

9:33:58 AM [email protected] [GData]  Synchronizing folder list

9:33:58 AM [email protected] [GData]  Synchronizing folder list

9:33:58 AM [email protected] [GData]  Synchronizing folder list

9:33:58 AM [email protected] [GData]  Synchronizing folder list

9:33:59 AM [email protected] [GData]  Synchronizing folder ‘[email protected]/Contacts/’

9:33:59 AM [email protected] [GData]  Synchronizing folder ‘[email protected]/[email protected]/’

 

Hello, this unfortunately seems like either some security software on your computer may have disabled the application’s ability to connect to the server, or the server is unable to respond on time during the first request, this may be due to a number of request sent to the mail server on application startup that it may not be able to handle on time - before the request times out.
If you’re only experiencing this problem on startup and you’re able to use the chat feature while the application is running this should be nothing to worry about as the application should automatically try to reconnect after the request times out.