Bug 20035 - Owncloud client too old for newest servers
Summary: Owncloud client too old for newest servers
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-28 11:20 CET by Marcus Zurhorst
Modified: 2017-11-15 08:45 CET (History)
3 users (show)

See Also:
Source RPM: owncloud-client-1.8.3-1.mga5.src.rpm
CVE:
Status comment:


Attachments

Description Marcus Zurhorst 2016-12-28 11:20:14 CET
Description of problem:

I switched over to Nextcloud server several months ago, and the old Owncloud client was working fine all the time.
When I upgraded the Nextcloud server from version 10 to version 11 yesterday, I now see that the old client version 1.8.3 does not support the client version any longer.

The error message is:
"Error downloading https://Nextcloud-URL/remote.php/webdav/ - server replied: Forbidden (Unsupported client version)"

Consequently, my file syncronization is not working any longer.



Version-Release number of selected component (if applicable):
Owncloud Client: 1.8.3   
Nextcloud Server:  11.0.0   (Dec 13, 2016)
7


This is a tricky situation since Nextcloud seems to be more end-user friendly and larger fraction of the community changed to the fork.
Now we have a ancient client and people switch to the nextcloud server, which may cause additional incompatibility in the near future.

Not exactly sure whether the Nextcloud part of the story makes this bug report obsolete. But I guess that the old client would have issues with a newer Owncloud server as well.
Marja Van Waes 2016-12-30 09:32:32 CET

CC: (none) => marja11
Assignee: bugsquad => mageia

Comment 1 Marcus Zurhorst 2017-01-01 14:41:20 CET
In the Mageia forum [1], I received the hint to try the latest Owncloud client (v.2.2.4) from the Mageia Backports repository. 

I tried this, and it works flawlessly. This seems to be an acceptable workaround for mga5, thus I am documenting it here in case somebody else is running into a similar issue.


[1]  https://forums.mageia.org/en/viewtopic.php?f=7&t=11530
Comment 2 Morgan Leijström 2017-05-17 00:15:53 CEST
They are tricky beasts... i wrote a wiki page
https://wiki.mageia.org/en/OwnCloud#Upgrading

CC: (none) => fri

Comment 3 Morgan Leijström 2017-06-02 14:23:12 CEST
I intentionally leave this bug open for a while to make it easier to find the resolution (comment 1, 2)
Comment 4 José Jorge 2017-11-15 08:45:29 CET
I think we can close it now that MGA6 is out for a while. To any cloud users, there is a client update to test :

https://bugs.mageia.org/show_bug.cgi?id=21015

and a server upgrade  :

https://bugs.mageia.org/show_bug.cgi?id=22026

Status: NEW => RESOLVED
CC: (none) => lists.jjorge
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.