This project has moved. For the latest updates, please go here.
1

Closed

Unable to select google calendar

description

I was able to access my google calendar however all of a sudden that stopped and the syncing as well . I now get the error

Unable to get the list of Google calendars. The following error occurred:
Web request to 'https://accounts.google.com/o/oauth2/token' failed.
Unable to connect to the remote server

Log file is attached.

file attachments

Closed Apr 1 at 9:34 PM by phw198

comments

phw198 wrote Jul 27, 2016 at 4:44 PM

Looks like you haven't set the app to use a proxy - try selecting the option to inherit from IE.

phw198 wrote Jul 27, 2016 at 4:52 PM

Actually, scratch that - I see you've tried using a custom proxy and that doesn't authenticate successfully either. However, your username is "mog/kam064" - is the "mog" meant to be the domain name? If so, it should be a backslash, not forward slash.

If that still doesn't work, does setting it to IE inherit from IE help?

kevin123456 wrote Jul 28, 2016 at 7:39 AM

If I try "inherit settings from IE" I get the error "The remote server returned an error: (401) Unauthorized.unauthorized."

I was just trying to guess the proxy settings required based on my companies information and what I could find in IE. Not sure if what I entered is right.

The sync use to work so I don't know what happen. Maybe my company chagned some security protocals.

phw198 wrote Dec 3, 2016 at 9:15 PM

Could you confirm if this is still a problem in v2.3?

kevin123456 wrote Dec 5, 2016 at 10:11 AM

Hi phw198,

It is still an issue in V2.3. If I "inherit from internet explorer" proxy settings I get "the remote server returned an errror: (4101) Unauthorized".

If I use "no proxy" I get "web request to https://acounts.google.com/o/oauth2/token' failed. Unable to connect to the remote server".

Kevin

phw198 wrote Feb 25 at 8:08 PM

Hi Kevin,

I've just closed a different proxy error ticket, where the user said it was fixed in v2.3.3 - worth trying?

Cheers

kevin123456 wrote Mar 9 at 11:31 AM

Hi,

Thanks for the reply. The new version definitely fixed the problem. Thanks for the fix!

Kevin