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.
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?
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.
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?
OK, I confirmed normal function on a total of ten machines running the most recent or (nearly most recent) version of the client. The only machine that it fails to run correctly on is the Mac Mini M2 (Apple Silicon) - I have only one (1) device w/ Apple Silicon hardware. Nevertheless, this leads me to believe that it is a build/packaging bug.
I will post to the github client bug tracker and include the OS/version/machine-arch for all those where the client works as expected.
OK, your response poked a big hole in my thoughts… deflated completely, because I thought it was just a Apple Silicon (M1, M2, etc.) problem. Since your Macbook (Pro? 2018 or 2019?) is Intel i9, it seemed to me that it was unlikely to be an architecture-specific problem.
On a hunch, I (re)moved my client cache at : /Users/your-username/Library/Caches/owncloud
and restarted the client in the normal fashion - double clicking. It worked perfectly.
I have not checked to see if it works correctly when doing a first-run on a user’s account (ie. when it can’t locate any owncloud .db files that signify the presence of an already-set-up account.
You can check this easily by simply renaming the dir from owncloud to owncloud-backup , for instance.
I’m not sure why it would make a difference, but perhaps there was a version change that caused an inconsistency. Or perhaps some corrupted data in the cache. Not sure what else it could be.
After a retry…
After trying to replicate this behavior again on my M2 Mac MIni - I was unable to… I am unsure of what it going on - it would not replicate/repeat, so I still don’t know what the problem is.
Perhaps it is something in the preferences file or an interaction between the cache and the preferences…
Correct, I am using 2019 MacBook Pro (2.4 GHz 8-Core intel i9) with 64GB RAM.
So here is the kicker (not sure if I described in this much detail). This may be a problem with ownCloud server 10.3.2 (only?). I have two servers I connect to, regularly. One home, one remote with VPN. So I connect to one at a time only.
I tried your suggestion of deleting the cache folder and it did not make a difference.
Scenario 1: At home network.
Starting owncloud from command line, the client can connect to the server (10.3.2). Quit the client. Start using the GUI, the client shows “Disconnected from: https://owncloud.home/”. Clicking Account → Reconnect option does not do anything other than refresing the “disconnected from….” message.
I then connect to my VPN and can connect to my work owncloud server (10.2.1) by starting the client from the command line or GUI.
Not exactly the same thing but I deployed owncloud server 10.3.2 locally on my laptop and I am not running into the issue when I create a connection to https://localhost
I can start the app from the Applications folder with double clicking and the client can connect to that new server.
So this leads me to believe something is odd about my server owncloud.home; something got that into the state it is at. It is still strange why owncloud client behaves differently as it does based on how it is started though
So the issue appears to be with Owncloud server 10.3.2 and self-signed certificated (even when the CA is trusted by the computer).
I replaced the localhost certificates with mbp2019.home and things work fine; even the owncloud client does not warn about https certificate not being trusted but later when the app is started from GUI, it fails to connect to the server; it does connect when started from command line.
I then downgraded to server version to 10.2.1 (same as my work owncloud server I knew to work) and then all is well with my mbp2019.home also.
So frankly, there is a problem here but it appears to be for specific one or more version in the past and I would not blame anyone not trying to fix it. At the same time, I find it rather curious what the issue is!
| 