[BUG] Seafile 10.0.1 CE (docker) with SeaDrive 3.0.7 on Mac OS X Sonoma

Hej,

after upgrading my docker to Seafile 10 CE my SeaDrive no longer works correctly on Mac OS Sonomoa clients. SeaDrive on the Mac is upgraded to 3.0.7.

In Finder I can click on the “SeaDrive” on the left menu and do get four links (My Libraries, Shared Libraries, etc.). However no contents are displayed inside the four links.

[12/18/23 12:46:27] repo-mgr.c(3554): adding account https://XXXXX.de XXXXX@XXXXXXXXX.de.
[12/18/23 12:47:54] workingset-mgr.c(813): cache size limit is 10000000000
[12/18/23 12:57:54] workingset-mgr.c(813): cache size limit is 10000000000
[12/18/23 13:07:54] workingset-mgr.c(813): cache size limit is 10000000000
[12/18/23 16:27:15] workingset-mgr.c(813): cache size limit is 10000000000
[12/19/23 03:48:24] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 05:49:29] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 05:49:51] workingset-mgr.c(813): cache size limit is 10000000000
[12/19/23 06:23:11] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 06:23:40] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 06:50:30] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 07:27:15] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 07:51:37] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 08:52:42] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 09:20:58] http-tx-mgr.c(717): libcurl failed to GET https://XXXX/seafhttp/accessible-repos/?repo_id=30342e00-d5f0-45e4-aff4-03431be8ea42: Couldn't resolve host name.
[12/19/23 09:26:20] workingset-mgr.c(813): cache size limit is 10000000000
[12/19/23 09:36:20] workingset-mgr.c(813): cache size limit is 10000000000
[12/19/23 09:50:49] workingset-mgr.c(813): cache size limit is 10000000000
[12/19/23 10:00:49] workingset-mgr.c(813): cache size limit is 10000000000
[12/19/23 11:33:21] workingset-mgr.c(813): cache size limit is 10000000000
[12/19/23 13:03:04] workingset-mgr.c(813): cache size limit is 10000000000

This points to a DNS issue on the client. However nslookup on the client works just fine using the DNS-server specified via DHCP. Is the a hard-coded DNS server inside SeaDrive client which may be firewalled?

Thanks, -MN