We’re received this reply from the Synology dev team:
Thank you for the listed points at the point.
The behavior is known to our development and a solution regarding this is being worked on.
Unfortunately, I cannot tell you from our side when exactly there will be a solution, as we have no insight into the development processes.
@devvv4ever As mentioned, I have a Dualstack Lite connection. That means that I cannot do a port forwarding for the IPv4 side of the connection as one public IPv4 is shared with several DSL lines. Only the IPv6 is a dedicated address. And there is no port forwarding on IPv6.
So, to address my NAS, I need to address it via IPv6.
I could follow your advice and do IPv6 DynDNS. But this only works with internet clients with an IPv6 address. Unfortunately, there are still DSL providers 2021 in Germany who still provide only an IPv4 address.
So, I need a protocol switcher for IPv4 sources to my NAS IPv6 destination. The easiest way is Synology Quickconnect.
I can resolve the A and AAAA record (via “dig”) of my quickconnect URL <quickconnectID>.de3.quickconnect.to to IP addresses. But how can I ensure that Davx5 deals with this correctly and also selects the IPv6 address instead of the IPv4 address?
@devvv4ever Thanks for your follow up. I was syncing to the Synology Calendar “My Calendar”. To be sure I changed the name to something very distinctive and posted on my phone making sure I was posting to that calendar. And it worked! So guess it was user error on my part. Thanks again for your help.
@rfc2822 I think I’ve figured out the reason for the error message.
When I previously tried to enter the ip-adress, I asked the app to prepend https://, which is probably the reason why it didn’t allow for “:5001” to work. My best guess is that the app does the error check without virtually prepending https.
Tested it while manually adding https and port, and now it is working flawlessly.
i have been trying that as well now - however i am still not sure about the exact details and order.
delete the address book on Synology,
( The CardDav Server is creating one Addressbook per user - i am admin and therefore i cannot just delete the addressbook in question)
create a new empty address book,
I assume that this should be done on the phone as the Synology would also not allow me to do that.
And when we speak about phone do you mean in the contacts app or the DAVx5 ( the last one i tried with below result)
Here is what i have been doing:
deleting the contacts from phone again
deleting the contacts from CardDav Server
Attempting to import the contacts.vcf from phone into DAVx5 Account (Phone)
This did not work (no specific error - just cant be imported presented by Android)
deleted the DAVx5 addressbook on the phone via DAVx5 App
Attempting to create new Addressbook via DAVx5 in App - does not work with an error 403 Forbidden
Can you specify exactly where each action has to be performed ?
Thanks in Advance.
Ok never mind the above 🙂 - the import that showed me not possible before worked now - the downloaded file was empty - i could retrieve it though. The issue was resolved exactly as you told me… I have to document that for myself in case that it will happen again.
Thanks a lot for the quick help and replies…
Really enjoying the app so far- keep up the good work.
The WebDAV package included their (they = Synology) old calendar server. Then they have created a separate Calendar package – so why use the old WebDAV package (without calendar UI) when they have now a real Calendar package available? I also guess that WebDAV calendars won’t get much support if there’s an active Calendar package which is actively maintained.
Do you see any reasons to recommend their old WebDAV package instead of their new Calendar pacakge?
The Calendar package seems to provide a CardDAV service, too. This is why “CardDAV” appears in DAVx⁵ accounts created for Synology Calendar. You can even create an address book using DAVx⁵. However, this feature is not officially supported and there’s no user interface in the Calendar package. So, use the CardDAV server package instead (see below).
My installation is exactly as stated in the set up instructions, so DAVx5 should be able to diagnose the problem.
You can imagine the Synology staff probably won’t be interested in supporting a third party app that doesn’t even run on their hardware.
Well, your interpretation of ‘tested-with’ probabely does not take the biscuit. It’s not about selling any Synology app such as CardDAV server with DAVx5, but more of indicating basic compatibility. And in fact, Synology CardDAV server works in general with DAVx5 which I can confirm from my own experience.
Second, DAVx5 cannot be made responsible for some strange behaviour (e.g. redirection) outside the scope of DAVx5 and the expectation ‘should be able to diagnose the problem’ is of course desireable however not very realistic.
Third, using a Synology forum similar to this one is not about bothering Synology staff, more about asking other Synology users.
Back to the issue, redirection may occur for several reasons. So there are several potential places to cross-check. Since you logs show CardDAV standard ports for http and https, it would be worth to have a look at the CardDAV settings for redirection from http to https. Furthermore, you might also want to check the DSM reverse proxy for potential redirection of the port in question.
However, the easy way out might be - at least temporarily for testing purposes - to deactivate http to https redirection in CardDAV server and setup any device with https.
So here was the solution for me coming from synology assistance (Malek was super nice to help me):
1/ On the NAS, in control panel, “external access”, tab DDNS : create a synology address… it will be something like that: <name>.synology.me
2/ On the NAS, Set a fixed ip address on the local network to the nas : to do that, go to control panel/network/tab:network interface and modify the LAN line “manual ip config” the line IP address with the number you want (for me 192.168.1.24)
3/ on your box, open ports 5001 (connect to it through its local address and modify its NAT configuration. open a port for your nas in TCP port 5001
so here, the nas is accessible fro the outside on its caldav
4/ on the android DAV5X, open it, add a account, select URL and there add put the URL: https://<name>.synology.me:5001/caldav/<your_id>/aiioyb/
and enter your <your_id> and your password (the one to connect to your nas, at the id session).
All clear now!
I think/hope I am not the only one in the world who need some further explanation on (for many people obvious) things.
Maybe it is a good idea to post your last explanation somewhere in the manual.
Thanks for your help, I won’t bother you anymore…
yes I have, but I have to find an alternative way to reaching my NAS since I can’t just do https://nas.mydomain.com:8443 as I am using a reverse proxy to make sure my subdomains point to specific ports on the NAS.
My current setup is:
I have a subdomain (contacts.mydomain.com) (443) which points to my DDNS mydomain.ddns.net. The DDNS points to my network, and the 443 reaches my NAS, goes through a reverse proxy and points to a specific port in the NAS (in this case 8008). I need to do this to make sure I have a recognised SSL certificate from my domain.