HTTP/2 protocol error since ownCloud client update

help

#1

Expected behaviour

After installing ownCloud I should be able to add my server and connect to it.

Actual behaviour

The connection fails saying “HTTP/2 protocol error”.

Steps to reproduce

  1. Install ownCloud client 2.5.0 (build 10560) on Windows (Win10 64-bit) or perform automatic upgrade from previous version.
  2. Add a new server configuration
  3. When finishing by pushing the “Connect…” button it fails saying “Error: HTTP/2 protocol error”
  4. Downgrading to an older client version (e.g. 2.4.3.10188) solves the problem.

Server configuration

Operating system: {unknown as no admin access}
Web server: {unknown as no admin access}
Database: {unknown as no admin access}
PHP version: {unknown as no admin access}
ownCloud version: 10.0.9.5
Storage backend (external storage): {unknown as no admin access}

Client configuration

Client version: 2.5.0.10560
Operating system: Windows 10, 64-bit
OS language: English
Installation path of client: C:\Program Files (x86)\ownCloud

Logs

  1. Client logfile: Output of owncloud --logwindow or owncloud --logfile log.txt
    See here: https://gist.githubusercontent.com/fabbra/e5e5b1a8a2b5ea1892f07ce016657a5b/raw/96cb5d37da467e48677b98ac8031a5cdf07bafcd/gistfile1.txt

  2. Web server error log: {unavailable as no admin access}

  3. Server logfile: ownCloud log (data/owncloud.log): {unavailable as no admin access}


#2

Hey,

i did the following search:

https://www.google.com/search?q=“HTTP%2F2+protocol+error”+“owncloud”

and found e.g. the following bug report:

Maybe you can find some notes / hints related to your message in there?


#3

Hi there
I am the admin of the server with this issue.

Server info:
owncloud version: 10.0.10.4 (updated since bug report opened)
Operating system: FreeBSD
Web server: Apache (I believe)
Database: 10.1-MariaDB
PHP version: 7.2.11

@tom42: The bug finally links to the fix (https://github.com/owncloud/client/pull/6353). As far as I understand, the fix should have been incorporated also in the latest client versions, right? Therefore I assume this fix didn’t solve the problem or it is not same problem or the fix has somehow been removed.

I can confirm now, that the bug happens with multiple clients all having Windows 10 64bits using the latest owncloud client (2.5.0).

The ownlcloud log which correspond to such an error:

{"reqId":"e0c15377-86a4-4755-a04c-6f42b90213d0","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"--","app":"OC\\Authentication\\Token\\DefaultTokenProvider::getToken","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"token 1097928f6629f10847b1b6e573c282616cfa933fec428d29eca5c29d7ce4ab9ec0069dfc515cecddfcdcface479fc7ae7d0fe290b1f693e6a72efe72511ab35e does not exist"} {"reqId":"e0c15377-86a4-4755-a04c-6f42b90213d0","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"--","app":"OC\\User\\Session::login","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"regenerating session id for uid roman, password set"} {"reqId":"e0c15377-86a4-4755-a04c-6f42b90213d0","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"--","app":"OC\\Authentication\\Token\\DefaultTokenProvider::getToken","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"token 1097928f6629f10847b1b6e573c282616cfa933fec428d29eca5c29d7ce4ab9ec0069dfc515cecddfcdcface479fc7ae7d0fe290b1f693e6a72efe72511ab35e does not exist"} {"reqId":"e0c15377-86a4-4755-a04c-6f42b90213d0","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"--","app":"OC\\User\\Session::validateToken","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"token 1097928f6629f10847b1b6e573c282616cfa933fec428d29eca5c29d7ce4ab9ec0069dfc515cecddfcdcface479fc7ae7d0fe290b1f693e6a72efe72511ab35e, not found"} {"reqId":"b766a11b-a2f6-4b35-ba43-d213b621d461","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"XY","app":"OC\\Authentication\\Token\\DefaultTokenProvider::getToken","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"token e0f5bceaac30cb1e0f3a2e391d531ec2debb8387a6f60b79665ebc34002952caa4062061203a690faf3dfcd4322e938a3f8e2c5a610e9d9ca7981a5e4d8d6398 does not exist"} {"reqId":"b766a11b-a2f6-4b35-ba43-d213b621d461","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"XY","app":"OC\\Authentication\\Token\\DefaultTokenProvider::getToken","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"token 1097928f6629f10847b1b6e573c282616cfa933fec428d29eca5c29d7ce4ab9ec0069dfc515cecddfcdcface479fc7ae7d0fe290b1f693e6a72efe72511ab35e does not exist"} {"reqId":"b766a11b-a2f6-4b35-ba43-d213b621d461","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"XY","app":"OC\\Authentication\\Token\\DefaultTokenProvider::generateToken","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"generating token e0f5bceaac30cb1e0f3a2e391d531ec2debb8387a6f60b79665ebc34002952caa4062061203a690faf3dfcd4322e938a3f8e2c5a610e9d9ca7981a5e4d8d6398, uid XY, loginName XY, pwd set, name Mozilla\/5.0 (Windows) mirall\/2.5.0 (build 10560), type temporary"} {"reqId":"b766a11b-a2f6-4b35-ba43-d213b621d461","level":0,"time":"2018-10-24T09:27:59+00:00","remoteAddr":"XY","user":"XY","app":"OC\\Authentication\\Token\\DefaultTokenProvider::getToken","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"token 1097928f6629f10847b1b6e573c282616cfa933fec428d29eca5c29d7ce4ab9ec0069dfc515cecddfcdcface479fc7ae7d0fe290b1f693e6a72efe72511ab35e does not exist"}

This is the apache log:

XY - - [24/Oct/2018:11:27:56 +0200] "PROPFIND /remote.php/webdav/ HTTP/2.0" 207 342 "-" "Mozilla/5.0 (Windows) mirall/2.5.0 (build 10560)" XY - - [24/Oct/2018:11:27:59 +0200] "PROPFIND /remote.php/webdav/ HTTP/2.0" 207 304 "-" "Mozilla/5.0 (Windows) mirall/2.5.0 (build 10560)"

Currently, we have a workaround in place using an older client version (2.4.3).

Thanks for taking another look.
Best,
rmk


#4

Hey,

if i understand the issue i had posted correctly the bug with HTTP/2 is caused by a “Qt5” package and not directly by the sync client. According to https://owncloud.org/changelog/desktop-client/ the sync client 2.4.1 should contain a fix for this.

So to me this looks like which could be a different issue here, maybe there is even a new issue in newer versions.

Personally i just would create a new issue at the sync client bugtracker as i don’t think that many users here at such a community forums can help if e.g. 2.4.3 is working but a newer version like 2.5.0 not. :confused:


#5

Thanks for your help. I opened the following issue: