Glad to hear I am not the only one. I am still having the same problem.
Client version: 5.3.2.15463
Macos version: Sequoia 15.6.1
| davygravy
August 29 |
- | - |
This is a continuation of the thread/topic here : Could not detect compatible server … for Mac Desktop Client
The Desktop Client, when installed on run on Linux (Debian based), ChromeOS (Android base) and Windows 10 and 11 machines all work normally. Additionally, I’ve discovered that the client installed on MacOS on Intel (non-ARM, non-Silicon) works normally.
Could not detect compatible server at https://owncloud.home Desktop
I have had been hosting my server at home using a self-signed certificate. I use my own CA and thus the client computer considers the owncloud certificate to be valid. I have multiple computers on my network, Windows and Linux that are using ownCloud client successfully. The exception is my macOS machine that I updated to Sequoia and noticed synch was not working. So I am blaming the macOS update. In order to figure things out; I deleted the connection and tried to create it again but I get “C…
I’m in the same situation as the OP of this thread…
-
ownCloud server 10.15.2.0,
-
Sequoia 15.6.1,
-
Mac Desktop client :
ownCloud 5.3.2.15463 1e2be1 Libraries Qt 6.4.3,
OpenSSL 3.1.7 3 Sep 2024
Using virtual files plugin: suffix OS: macos-24.6.0 QPA: cocoa
Same behavior… starting the app in the normal double-click manner results in the “Could not detect compatible server” warning that blocks further function. Starting via command line on the terminal results in proper function.
To be clear, even if the account is set up, verified and correctly synced, once the app is quit, restarting via double-click still results in an error, but a quiet one where it the client simply states that it is disconnected.
So what is the difference between starting the app via gui/double-click and starting it via the CLI/terminal? Is there a script that is bypassed when starting from the CLI?