sync problem with ios

[stoi2000]

Hi
i have just installed baikal on raspberry pi and it works fine in browser, evolution mail on desktop and even under blackberry os10. thx for that! If i am trying to sync my baikal calendar with my iphone (ios 13.5.1) the sync will not be sucessfull. I have found some informations that ios is not properly working because there are some rewriting rules inside the webserver are missing.

thanks for help in advance!
stoi2000

[ckulka]

Hi there, can you link the articles you found? I'll have a look and can add those changes.

[stoi2000]

Hi ckulka
Thanks for your reply and sorry for my late answer. The article i have found is in german language and can be found under: https://www.cyon.ch/blog/CalDAV-CardDAV-Server-Baikal#Setup
I'll translate the important Information into ENG:

`for macOS, iOS and iPadOS Users
When the accounts set up via Baïkal are set up later, the Apple operating systems search for the corresponding PHP files in the wrong place. In this case the following entry in the control file .htaccess, which must be located one directory above the Baïkal subdomain, helps:

RewriteEngine On
RedirectMatch 301 ^/.well-known/caldav /baikal/html/cal.php
RedirectMatch 301 ^/.well-known/carddav /baikal/html/card.php
`
I am really new to docker so it's maybe on my side that i cannot establish a connection to my iphone.
Thanks for your support and help!

stoi2000

[ckulka]

Hi @stoi2000,

thanks, unfortunately I don't think that's it because it is already part of the Docker image (both apache and nginx):

baikal-docker/files/apache.conf

Lines 9 to 11 in a8e7d11

	RewriteEngine On
	RewriteRule /.well-known/carddav /dav.php [R,L]
	RewriteRule /.well-known/caldav /dav.php [R,L]

baikal-docker/files/nginx.conf

Lines 10 to 11 in a8e7d11

	rewrite ^/.well-known/caldav /dav.php redirect;
	rewrite ^/.well-known/carddav /dav.php redirect;

I used the configuration setup from the official installation and troubleshooting guide. Difference to your article is that both are served from dav.php, I believe they merged cal.php and card.php in the 0.6 release... I think.

• https://sabre.io/baikal/troubleshooting/
• https://sabre.io/baikal/install/#apache-vhost-installation

Can you test if that redirect works on your setup by going to https://your-domain.com/.well-known/carddav and check if you are being redirected to https://your-domain.com/dav.php?

[BobWs]

I have also experienced sync problems. I am using Baikal behind a reverse proxy and found out that if you redirect to port 80 then .well-known does not work, but if I redirect to port 443 then .well-known works. And this without changing the .htacces File.

[ckulka]

Hi @stoi2000 ,

I'm guessing you solved this issue already somehow, but in case you haven't or someone else comes across this: check out #37, someone else had an issue with iOS when using Baikal with Traefik.

The fix is to add rewrite rules to Traefik (unsure why it's needed there too...) and the example has been updated:

baikal-docker/examples/docker-compose.ssl.yaml

Lines 18 to 22 in 8cb1ae3

	# Required for iOS, see https://github.com/ckulka/baikal-docker/issues/37
	traefik.http.middlewares.baikal-dav.redirectregex.regex: "https://(.*)/.well-known/(card|cal)dav"
	traefik.http.middlewares.baikal-dav.redirectregex.replacement: "https://$$1/dav.php/"
	traefik.http.middlewares.baikal-dav.redirectregex.permanent: "true"
	traefik.http.routers.baikal.middlewares: "baikal-dav"

[kvndl]

Are there any current fixes for getting iOS operational without the use of Traefik? Currently have everything going through my own Nginx setup using NPM.

Attempted to add those rewrite rules manually, but the error I get when trying to sync remains the same: Unable to connect to account -- this is after signing into said account via Settings.

When I try to reload/sync my calendar, it hits me with the following logs: Gist

Worth mentioning that everything works without a hitch when using a client such as Evolution.

Thanks in advance for any intel! 😄

[ckulka]

Sorry, I missed this questions completely. Can you try the following: change the target port of the Baikal container in NPM from port 80 to 443 and recreate the account in iOS?

My guess is that Apache first redirects on the plain HTTP port 80 instead of the HTTPS port 443, because (from Apache's perspective) the request came on port 80. By routing the incoming request to Baikal's HTTPS port 443, the redirect remains on HTTPS and it should be fine.

This is basically the same solution proposed by @BobWs just for NPM, with my explanation as to why it works.

[Jezz3]

I had the same Problem. Tested it and now it works. For the URL I use https://example.domain.com/dav.php/principals/myuser
Thank you very much for the solution.