I can log in to Nextcloud with v2.14.22, but get the error message "In order to synchronize, please upgrade your application to version 3.0.0+" (see screenshot below). The relevant About dialog is shown above under Desktop version info.
But with both v3.0.14 and v3.0.15, and using exactly the same credentials, attempts to log in to Nextcloud brings the error message "Error. Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was: request to https://xxx.yyy.cloud/remote.php/webdav/Joplin/ failed, reason: (Code ETIMEDOUT)" (see second screenshot below). The relevant About dialog is shown as a screenshot below.
These processes have been repeated many times with the same results. I'd be delighted if some kind soul would point me in the right direction.
Your sentence above is a bit unclear to me :
Did you upgrade your desktop version, or did you install v3 aside v2 and re-input your credentials?
(You are on Linux like me, so while you don't tell which flavor, upgrading from v2 to v3 should be something simple like sudo apt install xxx.deb for instance...)
Thank you for your reply as well as your interest. I'm sure that you're right with respect to the upgrades but in ignorance, I deleted Joplin, installed a new version (2.14.33, 3.0.14 and 3.0.15) and re-entered my credentials each time.
My Linux is Mint 22.0.
I might add that I have Joplin on two separate Android devices, on both of which Joplin is working perfectly. At present, awaiting a solution, I have no Joplin installation in my Linux box.
I could also add that I have a second Linux box, also Mint, with identical symptoms. It's on v2.14 and also shows the message "In order to synchronise, please upgrade your application to version 3.0.0+".
But, as I said, the two Androids are working well.
I believe that in the update to v3.x the underlying database or structure changed. So you need to run similar versions on the different platforms to allow sync to work properly.
I confirm I also got the 'in order to synchronize plese update... to v3' in my Debian machine, which I did and al went well.
Now, it may be a bit different from you because my previous v2.xx was indeed already set to sync properly before theu pdate, so all I needed to do was a Linux upgrade with just no new server setup.
In your case, you may need to install a blank v3.x and then run the relatively longer setup associated to joining a NEW Joplin instance, which involves tranferring passwords etc. IIRC.
