mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 11:35:47 +03:00
[GH-ISSUE #151] CalDavSynchronizer.DataAccess.WebDavClientException: Timeout? #615
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#615
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @marcelbrueckner on GitHub (Aug 10, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/151
Since today I'm getting an error on every sync run.
I currently have about 10500 calendar entries and therefore it could take some time to load.
When I'm pointing my browser to the endpoint of my CalDAV calendar it took about 30 seconds to load (which means that my server is reachable).
I tried to reduce the objects to sync from 60 days to 30 days in the past and from 180 to 90 days in the future, but without success.
I also tried it out with and without closing the connection after every request.
My configuration:
Client: Outlook 2013 on Windows 7 Pro (behind a proxy)
Server: Baikal 0.4.5 on Synology DSM 6
SSL/TLS connection with a Let's Encrypt Certificate
The same configuration worked until yesterday.
UPDATE: Check for update doesn't work either. Maybe internal proxy changes? How can I find out?
@aluxnimm commented on GitHub (Aug 10, 2016):
what proxy settings are you using in network settings? can you connect from Internet Explorer with same proxy settings? for slow servers increase timeout in general options.
@marcelbrueckner commented on GitHub (Aug 24, 2016):
Hi, sorry for the late response.
Seems like there was an issue on the proxy side. It worked again the day after my issue without any changes on my client.