Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ERROR: Unable to connect to the Google calender
See original GitHub issueChecklist:-
OGCS Version: v2.8.3.0 Edition: Installed Sync Direction: O<->G
Bug Description
The sync immediately fails with the above message: ERROR: Unable to connect to the Google calender
Steps to Reproduce the Issue
- Start Outlook Google Calendar Sync
- Click on Sync OGcalsync.log
Any other information
Any additional information that may help troubleshoot the issue.
📎 Attach your OGcalsync.log file.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Fix sync problems with the Google Calendar app
Fix sync problems with the Google Calendar app · 1. Make sure you're connected to the Internet. To test if you're connected to...
Read more >Google Calendar connection troubleshooting
In your OnceHub account, go to Profile-> Calendar connection and click the Renew your Google Calendar connection button. Connection errors after ...
Read more >"Unable to connect to Google Calendar" error ...
If you see an error in the top right, that says "Unable to connect to Google Calendar" when you enter your employee's profile,...
Read more >Error: Unable to access Google calendar. Please log in to ...
Information: When setting up Google Integration, you may receive the Error: "Unable to access Google calendar. Please log in to Google Calendar ...
Read more >ERROR: Unable to connect to the Google calendar. #1108
I tried disconnecting and re-connecting the account and it was able to retrieve my calendars one time (enough for me to choose which...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks looks like it has resolved itself now
Looks like a huge jump in Google response times and they’re now rate limiting hard. I would expect the issue to resolve itself once Google have resolved the underlying problem (though there’s nothing reported on their health status yet).
For those who tested under 2.8.4 was the error message reported any differently?