CalDAV, CardDAV no route to host

When setting up my locally hosted CalDAV server, Baikal btw. running in a docker container, I’m getting the error:

eM Client 10.3.4517+5b1983290a (iOS)
17:14:56 Familie CalDAV / CardDAV Kontoeigenschaften werden synchronisiert: Für Host https://cal.xxx/dav.php/principals/Familie/
17:14:56 Familie [CalDAV / CardDAV] MailClient.Accounts.ConnectionException: No route to host (cal.xxx:443)
 ---> System.Net.Http.HttpRequestException: No route to host (cal.xxx:443)
 ---> System.Net.Sockets.SocketException (65): No route to host
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError, CancellationToken) + 0x40
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16) + 0x58
   at System.Net.Sockets.Socket.<<ConnectAsync>g__WaitForConnectWithCancellation|285_0>d.MoveNext() + 0x1b8
--- End of stack trace from previous location ---
   at System.Net.Http.HttpConnectionPool.<ConnectToTcpHostAsync>d__52.MoveNext() + 0x730
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.<ConnectToTcpHostAsync>d__52.MoveNext() + 0x7a4
--- End of stack trace from previous location ---
   at System.Net.Http.HttpConnectionPool.<ConnectAsync>d__51.MoveNext() + 0x398
--- End of stack trace from previous location ---
   at System.Net.Http.HttpConnectionPool.<CreateHttp11ConnectionAsync>d__80.MoveNext() + 0x234
--- End of stack trace from previous location ---
   at System.Net.Http.HttpConnectionPool.<InjectNewHttp11ConnectionAsync>d__79.MoveNext() + 0x2e4
--- End of stack trace from previous location ---
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.<WaitWithCancellationAsync>d__1.MoveNext() + 0x100
--- End of stack trace from previous location ---
   at System.Net.Http.HttpConnectionPool.<SendWithVersionDetectionAndRetryAsync>d__50.MoveNext() + 0x774
--- End of stack trace from previous location ---
   at System.Net.Http.AuthenticationHelper.<SendWithAuthAsync>d__17.MoveNext() + 0x388
--- End of stack trace from previous location ---
   at System.Net.Http.RedirectHandler.<SendAsync>d__4.MoveNext() + 0x1d4
--- End of stack trace from previous location ---
   at System.Net.Http.DecompressionHandler.<SendAsync>d__16.MoveNext() + 0x320
--- End of stack trace from previous location ---
   at MailClient.Protocols.InteractionController.HttpClientCertificationValidationMessageHandler.<SendAsync>d__4.MoveNext() + 0x260
--- End of stack trace from previous location ---
   at MailClient.Protocols.Common.HttpClientHandlers.HttpClientBackoffHandler.<SendAsync>d__1.MoveNext() + 0x14c
--- End of stack trace from previous location ---
   at System.Net.Http.HttpClient.<<SendAsync>g__Core|83_0>d.MoveNext() + 0x39c
--- End of stack trace from previous location ---
   at MailClient.Protocols.CalDav.ProtocolCommands.Connector.RunCommand(CalDavAccount, ICommand, CancellationToken, Boolean) + 0x214
   --- End of inner exception stack trace ---
   at MailClient.Protocols.CalDav.ProtocolCommands.Connector.RunCommand(CalDavAccount, ICommand, CancellationToken, Boolean) + 0x888
   at MailClient.Protocols.CalDav.FolderSynchronizer.UpdateOptions(Uri[], Dictionary`2, CancellationToken) + 0x244
   at MailClient.Protocols.CalDav.FolderSynchronizer.Bootstrap(WorkerStatus, CancellationToken) + 0x7dc
   at MailClient.Protocols.CalDav.CalDavAccount.EnsureBootstrap(WorkerStatus, CancellationToken) + 0x24
   at MailClient.Protocols.CalDav.CalDavGenericCommand.EnsureBootstrap(WorkerStatus) + 0x40
   at MailClient.Commands.EnsureBootstrapCommand.Execute(WorkerStatus) + 0x28
   at MailClient.Commands.Command.Process(WorkerStatus) + 0x98
  AccountId = 54cd2ad8-74f9-4ee7-aa02-b1016a9c8e15
  AccountName = Familie
  RunInPlace = False

I’m using the latest emClient on iPadOS, provided in Testflight app, version 10.3.4517
The very same URL I’m using within emclient is perfectly working in iPadOS own settings for the Apples calender settings.

I’m using the same domain with slightly different path on my Windows PC with Thunderbird and on many Android smartphones without any issues. So basically, the setup works as well as the domain and path.
Ironically, the URL I’m trying to set up on iPadOS work with emClient under Windows.

Any idea why emClient on iPadOS 18.x fails this way?

Edit: Some further testing revealed that when using the IP-address and port of the Baikal server, instead of the domain, the same error appears, so there is apparently no DNS issue involved.

Do those same CalDAV and CardDAV url work in eM Client for desktop ?

Just checked, and I can confirm the same URL works with emClient 10 on Windows. The same URL I’m trying to set up on iPadOS now.

Ok as they work on eM Client V10 for desktop but not the mobile, then suggest to send that issue to [email protected]

1 Like

Done! Thanks!