Synology calendar connection issues - need guidance for writing a good bug report

[WildEnte]

I have a Synology DS220 NAS which features a (pretty good) caldav calendar. In the past, I was able to set up the calendar but anymore (might be due to an update to the Synology DSM operating system, not necessarily Vivaldi...)

I need some guidance to write a useful bug report, maybe there is something that I can test. I assume the problem is due to the fact that I want to access the calendar using my local address https://192.168.44.2:5001/[...]/ but I don't have a valid certificate for https://192.168.44.2:5001. I have tried in the past to solve this certificate issue, I am too stupid to get it done (all I have achieved is a lets encrypt certificate via the online routing through synology.me - but I want to use the NAS only within my home network with no outside access)

I get it to work in Thunderbird after adding https://192.168.44.2:5001/ to the exception list in the certificate manager.

In Vivaldi, even though it's a CalDav Calendar, using CalDav does not work. ("CalDav service not found..."). Using the Web Calendar option, something happens:

It never really connects to the calendar (and doesn't add it to the list of available calendars in the client). But when I click on "done" to stop the wait and test the connection, it does find the exact number of events I have set up using the web interface. However, since the calendar does not appear in the list below (and I cannot add it manually either), I'm stuck.

Please let me know if this is enough information or if there is something that I can check in some log or whatnot (need guidance) to write a meaningful bug report.

EDIT: my offer to donate my old Synology DS215j to Vivaldi still stands. Synology NAS are pretty good, and I think that with web panels, Calendar, mail etc Vivaldi could be the perfect browser for Synology NAS.

[WildEnte]

Following Addon: I checked if the problem goes away if I set the synology to accept http connections on port 5000 (instead of redirecting to https on port 5001; these are default Synology settings). Using the address http://192.168.44.2:5000/caldav.php/WildEnte/ the calendar correctly sets up as a CalDav calendar (thanks @max06net helping me on Discord).

Note, if I try to set up the http connection as a web calendar instead of caldav, I see exactly the same behavior as shown above

I conclude that the problem is indeed with the invalid certificate for my local IP address.

[DoctorG]

@wildente Which Vivaldi version is this?

I guess it fails because IPs can not have a valid SSL certificate. You need to use the hostname of the NAS.
Ad have you created a certificate? Read Synology Help at Selbst unterzeichnete Zertifikate

And do not forget to import the certificate to your user certificate store.

[WildEnte]

@doctorg latest Vivaldi snapshot and synology DSM7. 0

I have the let's encrypt certificate, but I don't want to access my NAS via synology.me or the quick connect, but directly and exclusively within my LAN. I guess that there is some way to make it work with funky reverse proxy, host file and netsh commands but that's all above my level of understanding, and I try to avoid configuring things I don't understand. I think I'm not the only one....

So if it is really the certificate issue that prevents Vivaldi calendar to connect, allowing to define exceptions like Thunderbird would be welcome.

[DoctorG]

@wildente said in Synology calendar connection issues - need guidance for writing a good bug report:

I have the let's encrypt certificate

Why so complicated? You do not need a Lets's Encrypt.
Create a self signed, export it and import into users OS Cert Store.

My NAS NAS DS216+II gets its hostname by router DHCP Fritz!Box. I can access it my by hostname with https://ds216plus/ with Vivaldi.

I try to avoid configuring things I don't understand.

Then you can not use SSL with your NAS.

Do you want some help, please ask me in our german
Vivaldi subforum how to create SSL cert on Synology.

[WildEnte]

@doctorg said in Synology calendar connection issues - need guidance for writing a good bug report:

Create a self signed, export it and import into users OS Cert Store.

DSM7 removed the possibility to create a self signed cert... I have tried to figure this out a while ago but gave up - too advanced for me. Again, if Vivaldi allowed to save the exception, all would be fine. (or I can just use the http access ...)

[DoctorG]

@wildente said in Synology calendar connection issues - need guidance for writing a good bug report:

DSM7 removed the possibility to create a self signed cert...

Mist! Arghh. My idea was from older DSM 6.x.

Wait, i try to check how to add exception.
Which OS do you use?

Windows with Powershell
New-SelfSignedCertificate -DnsName "nashostname" -CertStoreLocation "cert:\LocalMachine\My" -NotAfter (Get-Date).AddYears(2)
Quelle: Erstellen selbstsignierter Zertifikate in Windows 10/Windows Server 2016

[WildEnte]

@doctorg I will try, however this means that I will have to a) make this work, b) make it work on my wife's computer, and c) hope nothing breaks going forward.

But think about the average user who bought a NAS and read the latest c't that said the synology calendar is great. They fire up the calendar, look for the caldav address and see "https://192.168.0. 2:5001/caldav/my username"

This address just has to work in Vivaldi. It does in Thunderbird (with some hassle...).

Bug report or feature request?

I wouldn't care too much if Vivaldi supported digest Auth, in which case I could use my domain hosted by all-inkl.com (VB-82551).

[DoctorG]

@wildente OK, i think Vivaldi's BETA of Calendar and bad caldav detection is the culprit.
Sorry, i can not help more as i do not use and test Vivaldi Mail&Cal&Feed any longer, i had too much trouble.

I agree in your post, that Vivaldi should nave a exception list like Mozilla browsers have.

[DoctorG]

@wildente said in Synology calendar connection issues - need guidance for writing a good bug report:

Bug report

A bug, Vivaldi should be able to detect the CalDAV ressource.

[WildEnte]

@doctorg VB-87774

Thanks for your help - as usual, very much appreciated.

[DoctorG]

@wildente said in Synology calendar connection issues - need guidance for writing a good bug report:

VB-87774

I confirmed and hope a dev will check this.

[jumpsq]

@doctorg said:

Sorry, i can not help more as i do not use and test Vivaldi Mail&Cal&Feed any longer, i had too much trouble.

Uh, this makes me curious (about the errors and also what you use instead).

@WildEnte I guess that you could attempt manipulating the DNS. Have a look at which domain is validated by the certificate and map this to 192.168.44.2 in your /etc/hosts (no idea what the equivalent is for windowz is for a fixed DNS entry).

I also can't tell if you need to access the NAS remotely at any time (i.e. via that domain), which would then no longer be possible. (But I'm sure that there will still be software to manipulate your DNS record only when in a specific network.)

[DoctorG]

@jumpsq said in Synology calendar connection issues - need guidance for writing a good bug report:

Uh, this makes me curious (about the errors

• slow mail database
• missing mail signing/encryption
• missing templates
• missing macros
• broken caldav detection
• missing override of SSL certficate errors
• missing remote address book

and more…

and also what you use instead).

The Bat! on Windows and Thunderbird on Linux.

[WildEnte]

@jumpsq with a huge amount of help from @max06net on Discord I got it running with a Let's encrypt certificate. For reference, here is what is required (this is mostly independent from Vivaldi...) maybe it helps some other Synology DSM 7 users.

1. Get a valid Let's encrypt certificate and make sure it doesn't expire:

1a) You will need to have an active domain for the certficate to get renewed. So you will need to go to the DSM Control Panel - Connectivity - External Access - DDNS and add a service. I chose

• Service provider: Synology
• hostname: mychoice.synology.me

1b) Get your certificate in DSM Control Panel - Connectivity - Security - Certficate and add a new Let's encrypt certificate (or replace an existing one). As Domain name, choose the hostname configured in 1a). Make sure to also add this host name in the Field "Subject Alternative Name", otherwise Chromium based browsers will not accept the cert (Firefox does).
If you can, also add the local hostname of your Synology to the Subject Alternative Name, for whatever reason that didn't work for me (... see point 3)

2. Make sure you only open ports that are absolutely required. If you have a good router, forward port 80 to your Synology NAS and be happy. You can have the Synology configure the router for certain services using UPnP. I have a crappy standard Vodafone Router - although I had only forwarded port 80, going to https://mychoice.synology.me:5001 presented me with the DSM login - open for everyone. So off we went to configure the Synology Firewall:

3. Since I couldn't get the certificate to sport my local Synology hostname, I edited the OS host file by adding the line "192.168.44.2 mychoice.synology.me", i.e. redirecting all requests to mychoice.synology.me directly to the Synology NAS. Unfortunately, the host file cannot redirect ports, too, so we also need to define a reverse proxy

4. Go to DSM Control Panel - System - Login Portal - Advanced - Reverse Proxy and configure it such that any request arriving at the standard https port 443 as https://mychoice.synology.me are redirected to port 5001 on the Synology (=localhost address 127.0.0.1)

So.... we jump through hoops to make sure the certificate gets renewed regularly, correct flaws in the router, fool the browser with the host file to talk to the Synology directly on the LAN and then redirect the request to the correct port. (Thanks again @max06net for patience and great guidance).

ALTERNATIVELY Vivaldi could just allow an exception to the certificate error for a local IP address.
(Alternative 2 is to use the http address for the calendar instead of https )