2.4.0: Fails to connect with HTTP2 #6285
Labels
Milestone
Comments
|
If the client receives a 503 reply from the server it will assume it's temporarily unavailable and try again later. When a browser or curl were used to access the same url they sent a GET request. That doesn't tell us about what would happen for a PROPFIND that the client probably sent. A client log file might be helpful for investigating this issue (https://doc.owncloud.org/desktop/2.3/troubleshooting.html#saving-files-directly). |
|
I suppose the server log might contain information about why there is an error. |
|
@ckamm - here is the requested client log: |
|
@ogoffart - the apache log you requested: |
|
and here comes a cleaned nextcloud log - the places with f*word are places where sensible user informations like user or cleartext passwords was leaked into the log: btw - i'm not the user who wrote the debian bug - so we are at least two unhappy users - and more will follow, if owncloud hit testing |
|
I have the same issue with nextcloud 12.0.4 and owncloud-client 2.4.0. Downgrading the owncloud-client to 2.3.x solved the issue for me as well. NGINX complains that fastcgi returned '0' for remote.php when accessed with owncloud-client 2.4.0. No errors from fpm is outputted. |
|
The log does not tell much, what's interesting is: Maybe this corresponds to So the error would be In 2.4, we changed a bit the authentication worflow in order to support oauth, but we don't have information on what is wrong. |
|
I just checked with a Nextcloud 12 demo instance and saw the issue at hand; the server is replying to The 503 error you see on the server logs/client is the result of opening |
|
I tested a bunch of different setups.
And for me it all worked. Except the demo.nextcloud.com . However as some users also reported it I suspect some webserver config magic. If anybody can share their webserver config? |
|
In the debug log of the owncloud client I can find the following line: And indeed the client woks again as soon as I deactivate http2 in my nginx config. The strange thing is: demo.nextcloud.com doesn't support http2. So may be there is another problem.? |
|
So there might be different problem in play here. The problem on the nextcloud demo server might not be the same as what other reports. Please be explicit about your webserver. and the symptom of the problem. @bastei: Do you see the errors 503, like @hefee reports. You can see if you are using http/2 because of a log message like this when starting the sync: HTTP/2 was not tested so good because the version of Qt that is shipped by owncloud is still Qt 5.6 which does not support it. However HTTP/2 works for me with apache and owncloud 10. (btw, @bastei , this stream closed message is normal.) |
|
I get the 503 errors, too: nginx |
|
ogoffart - yes, i use http2 |
|
I use NGINX with HTTP/2 as well for my Nextcloud 12.0.4.3. My owncloud-client is built with LibreSSL (2.5.5) on qt 5.9.3. |
|
@SamuAlfageme: Here are the server logs from the moment the affected owncloud client starts: |
|
@bastei I see both 507 coming from the (new) |
|
@SamuAlfageme Unfortunately the logs are very familiar with So, |
|
I confirm this bug is still happening with Nextcloud 13. I confirm this bug disappeared when not using HTTP/2 with the nginx configuration. I repeat: disabling HTTP/2 solves this issue. However, this is not a workaround for me. I need HTTP/2 for other websites my server is serving. |
|
3 tasks
|
@bastei @Glandos Would be interesting to see if you can compile the client with Qt 5.10 (or 5.9.4) and if this makes a difference. https://doc.owncloud.org/desktop/2.4/building.html Or you give out a test account to @ogoffart who has a newer Qt? e-mail is his github at woboq.com ... @hefee When does debian switch to Qt 5.9.4? The problem could be https://bugreports.qt.io/browse/QTBUG-64359 |
|
I'm lost the interest in this issue nearly fully - my server configuration is fine, the 2.4 Windows client works fine. Version: So my only guess is the used ssl version in debian - anyways, happy debugging. EDIT: installed the obs packages on a current sid - works fine: So until it is solved i will use the 2.3.x client |
|
On openSuse Tumbleweed: The RPM info (sorry for localized field names): So, it seems that the Debian build is to blame. Qt 5.10 is in experimental, but I don't know how long it will take to make it into unstable. So @hefee if you can report on the Debian bug that this is linked to a combination of Qt version and HTTP/2 server, it seems the root cause. |
guruz
changed the title
guruz
added a commit
that referenced
this issue
Feb 9, 2018
|
Has anyone reprduced the bug with owncloud rather than nextcloud? (@SamuAlfageme, did you ?) Anybody else tried upgrading Qt to solve the problem? Since @Glandos went from debian to opensuse, there might be other factor in play (such as the openssl version) Even then , we don't have confirmation this is not a server issue? What are the nextcloud server log saying about this error 503? Why is it happening? |
In one test (on Debian), I only disabled http2 on my nginx server. No less, no more. And without HTTP/2, it worked. |
|
@ogoffart about
Nope, been poking an ownCloud 10.0.4 deployed with nginx over HTTP/2 for a bit and got no traces whatsoever of errors 5XX that could be attributed to the protocol bump. I think the conditions to reproduce this are highly dependent on how the server was deployed (env-wise) We do have daily builds w/ Qt 5.10 already available in https://build.opensuse.org/package/show/isv:ownCloud:testpilot:daily:master/testpilotcloud-client @bastei @Glandos @agaida @hefee care to give it a spin? Nextcloud/Apache logs (or even stack traces if we're looking at concurrency issues) from the time of the incidents will come in very handy to determine why the server is misbehaving and which client requests lead to that. |
|
@Glandos : but the opensuse build works even with HTTP/2 ? |
|
@ogoffart Yes. |
guruz
added a commit
that referenced
this issue
Feb 12, 2018
|
I'm quite sure it is QTBUG-64359 :-) So I consider this fixed with #6353 |
guruz
added a commit
that referenced
this issue
Feb 13, 2018
guruz
added a commit
that referenced
this issue
Feb 14, 2018
|
Has anyone seen issues with HTTP2 in 2.6.0 similar as in #7610 ? Please comment there... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Debian user complains, that the new occ 2.4.0 do not connect anymore to Nextcloud 12. Worked with 2.3.3 perfectly. Here the bts/886395:
When I use the logging window here are some of the network error I
have:
The 503 HTTP Error seems strange as I can access the web interface of
nextcloud through firefox. When I try to reach the aforementioned URL
with firefox I've got a message telling me that I reached a WebDAV
interface which indicates that everything is normal.
I also have this error:
But when I use curl to fetch this page I receive the expected JSON:
Also there's a thread in the NextCloud forum: help.nextcloud.com/owncloud-desktop-client-2-4-0-with-nextcloud-12
The text was updated successfully, but these errors were encountered: