starred/outlookcaldavsynchronizer

Fork 0

mirror of https://github.com/aluxnimm/outlookcaldavsynchronizer.git synced 2026-04-26 03:25:48 +03:00

[GH-ISSUE #309] Nginx Modern Configuration not supported #300

New issue

Open

opened 2026-02-25 20:31:21 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 20:31:21 +03:00

Owner

Originally created by @vallant on GitHub (Mar 18, 2021).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/309

Hello,
first of all- thanks for your work! This plugin is awesome, i use it alongside my self-hosted nextcloud server.
I recently changed my server setup and switched from apache to nginx as a reverse-proxy, in this process i also updated the SSL configuration of the proxy.
I've noticed that when using the "modern" configuration below (obtained by the mozilla config generator), it fails to connect with the error that is attached.
If i switch to the intermediate configuration, the connection works fine.
Obviously the TLS1.3 support option is activated (if not i'd expect a protocol-mismatch error message).
Is there a way around this? I'd really like to keep use the modern SSL configuration on my server.
Best, Stephan

# modern configuration
ssl_protocols TLSv1.3;

# intermediate configuration
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;

error.log

Originally created by @vallant on GitHub (Mar 18, 2021). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/309 Hello, first of all- thanks for your work! This plugin is awesome, i use it alongside my self-hosted nextcloud server. I recently changed my server setup and switched from apache to nginx as a reverse-proxy, in this process i also updated the SSL configuration of the proxy. I've noticed that when using the "modern" configuration below (obtained by the mozilla config generator), it fails to connect with the error that is attached. If i switch to the intermediate configuration, the connection works fine. Obviously the TLS1.3 support option is activated (if not i'd expect a protocol-mismatch error message). Is there a way around this? I'd really like to keep use the modern SSL configuration on my server. Best, Stephan # modern configuration ssl_protocols TLSv1.3; # intermediate configuration ssl_protocols TLSv1.2 TLSv1.3; ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384; [error.log](https://github.com/aluxnimm/outlookcaldavsynchronizer/files/6162425/error.log)

kerem commented

2026-02-25 20:31:22 +03:00

Author

Owner

@aluxnimm commented on GitHub (Mar 19, 2021):

What exactly are your general options/ssl and tls settings? And what Windows/Outlook and .Net versions installed?

@aluxnimm commented on GitHub (Mar 19, 2021): What exactly are your general options/ssl and tls settings? And what Windows/Outlook and .Net versions installed?

kerem commented

2026-02-25 20:31:22 +03:00

Author

Owner

@vallant commented on GitHub (Mar 29, 2021):

Hi- sorry for the late reply.
I'm using Outlook 2016 and Windows 10 Enterprise (10.0.19042).
Which is the exact command for finding out the .Net version?
The TLS settings are the following.

@vallant commented on GitHub (Mar 29, 2021): Hi- sorry for the late reply. I'm using Outlook 2016 and Windows 10 Enterprise (10.0.19042). Which is the exact command for finding out the .Net version? The TLS settings are the following. ![Capture4](https://user-images.githubusercontent.com/11185241/112810487-5ec0c180-907b-11eb-805b-ed5eaba7a4a1.PNG) ![Capture3](https://user-images.githubusercontent.com/11185241/112810509-63857580-907b-11eb-8a1a-b23cf18f52e2.PNG) ![Capture2](https://user-images.githubusercontent.com/11185241/112810719-9d567c00-907b-11eb-8f66-82fc0e5cb33c.PNG) ![Capture1](https://user-images.githubusercontent.com/11185241/112810731-a21b3000-907b-11eb-912a-c3ad5358f9c9.PNG)

kerem commented

2026-02-25 20:31:22 +03:00

Author

Owner

@flo-mic commented on GitHub (Jul 27, 2021):

I have the same issue on windows 10 Home 21H1 with Outlook 365 (Version 2106). In the general settings the TLS 1.3 option is enabled. If I enable TLS 1.2 on the webserver the connection is working without any issues. The CalDav Sync Version is 4.1 and .Net 4.8 is installed on the system

@flo-mic commented on GitHub (Jul 27, 2021): I have the same issue on windows 10 Home 21H1 with Outlook 365 (Version 2106). In the general settings the TLS 1.3 option is enabled. If I enable TLS 1.2 on the webserver the connection is working without any issues. The CalDav Sync Version is 4.1 and .Net 4.8 is installed on the system

kerem commented

2026-02-25 20:31:22 +03:00

Author

Owner

@alainwolf commented on GitHub (Mar 6, 2022):

I have the same issue with a Nextcloud server running on a Synology NAS (Nginx -> Apache HTTPD -> PHP -> Nextcloud -> WebDAV).

I found the following announcement from Microsoft in August 2020 regarding TLS 1.3 support:
https://www.microsoft.com/security/blog/2020/08/20/taking-transport-layer-security-tls-to-the-next-level-with-tls-1-3/

There it also says that "... TLS 1.3 support will also be added to .NET beginning with version 5.0. ...".

Looking trough the release announcements of this project, it mentions upgrade of the NET framework to 4.8 with release 4.0.0 in November 2020,

Since then, no release-announcements mention the .NET framework or version 5.0 of it.

I'm not a Windows developer myself, so I don't know how this plays out in users desktops.

@alainwolf commented on GitHub (Mar 6, 2022): I have the same issue with a Nextcloud server running on a Synology NAS (Nginx -> Apache HTTPD -> PHP -> Nextcloud -> WebDAV). I found the following announcement from Microsoft in August 2020 regarding TLS 1.3 support: <https://www.microsoft.com/security/blog/2020/08/20/taking-transport-layer-security-tls-to-the-next-level-with-tls-1-3/> There it also says that "... TLS 1.3 support will also be added to .NET beginning with version 5.0. ...". Looking trough the [release announcements](https://github.com/aluxnimm/outlookcaldavsynchronizer/releases) of this project, it mentions upgrade of the NET framework to 4.8 with [release 4.0.0 in November 2020](https://github.com/aluxnimm/outlookcaldavsynchronizer/releases/tag/v4.0.0), Since then, no release-announcements mention the .NET framework or version 5.0 of it. I'm not a Windows developer myself, so I don't know how this plays out in users desktops.

kerem commented

2026-02-25 20:31:22 +03:00

Author

Owner

@aluxnimm commented on GitHub (Feb 16, 2023):

C# VSTO Add-Ins don't support .Net 5/7 unfortunately, see
https://developercommunity.visualstudio.com/t/please-port-visual-studio-tools-for-office-vsto-to/757925

@aluxnimm commented on GitHub (Feb 16, 2023): C# VSTO Add-Ins don't support .Net 5/7 unfortunately, see https://developercommunity.visualstudio.com/t/please-port-visual-studio-tools-for-office-vsto-to/757925