Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP/2 protocol error #1072

Closed
mfeske opened this issue Feb 5, 2019 · 32 comments
Closed

HTTP/2 protocol error #1072

mfeske opened this issue Feb 5, 2019 · 32 comments

Comments

@mfeske
Copy link

mfeske commented Feb 5, 2019

Expected behaviour

By Installing under Ubuntu theire is an error "HTTP/2 protocol error"

Actual behaviour

Tell us what happens instead

Steps to reproduce

  1. Download Nextcloud-2.5.1-x86_64.AppImage
  2. start installation
  3. url from server
  4. choose folder
  5. start

Client configuration

Client version:
2.5.1

Operating system:
Ubuntu
OS language:
German
Qt version used by client package (Linux only, see also Settings dialog):

Client package (From Nextcloud or distro) (Linux only):

Installation path of client:

Server configuration

Operating system:

Web server:

Database:

PHP version:

Nextcloud version:

Storage backend (external storage):

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

Template for output < 10 lines

  1. Client logfile: Output of nextcloud --logwindow or nextcloud --logfile log.txt
    (On Windows using cmd.exe, you might need to first cd into the Nextcloud directory)
    (See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)

  2. Web server error log:

  3. Server logfile: nextcloud log (data/nextcloud.log):

@nem0nxt

This comment has been minimized.

@ohrie

This comment has been minimized.

@enoch85 enoch85 added the bug label Apr 14, 2019
@enoch85
Copy link
Member

enoch85 commented Apr 15, 2019

I can reproduce this error on a fresh installation with the Nextcloud VM scripts.

Nextcloud version 15.0.7
Client 2.5.2 (Windows, downloaded from nextcloud.com)

This is the configuration in question:

# Enable HTTP/2 server wide
print_text_in_color "$ICyan" "Enabling HTTP/2 server wide..."
cat << HTTP2_ENABLE > "$HTTP2_CONF"
<IfModule http2_module>
    Protocols h2 h2c http/1.1
    H2Direct on
</IfModule>
HTTP2_ENABLE
print_text_in_color "$IGreen" "$HTTP2_CONF was successfully created"
a2enmod http2
restart_webserver

@xianx
Copy link

xianx commented May 30, 2019

I cannot also sync files for this bug. Please fix it. Owncloud fixed it from their latest client https://techtun.es/drFf5W and nextcloud is overlooking it.

@bityoda
Copy link

bityoda commented Jun 1, 2019

Same for me it's annoying. I just updated the server to the latest version. Problem persists. Is there some plan to fix this, or can i help by providing some logs?

On the nginx server side there is a warning probably related to the problem:
2019/06/15 17:07:02 [warn] 7#7: *57 a client request body is buffered to a temporary file /var/cache/nginx/client_temp/0000000004

There is no space or right problem on the server side file system.

The file to upload has in example a size of 6M. Increasing the client_body_buffer_size to 10M in Nginx has no effect. Furthermore it seems that the first client upload after starting the nextcloud client works and the next files are failing.

@tflidd
Copy link
Contributor

tflidd commented Jun 16, 2019

I cannot also sync files for this bug. Please fix it. Owncloud fixed it from their latest client https://techtun.es/drFf5W and nextcloud is overlooking it.

It would be better to link the specific github issue and pull request. I only found this one:
owncloud/client#6353
but it is already backported to Nextcloud:
e82869d

There were other issues with configuration problems. This command turned out to be helpful if the server is responding correctly:

curl --head --http2 https://<my_server/

It should give a HTTP/2 200 status and shouldn't throw an error.

@enoch85
Copy link
Member

enoch85 commented Jun 16, 2019

It should give a HTTP/2 200 status and shouldn't throw an error.

In my case both my domains that are having issues throws HTTP/2 200, an they are still having issues with the client. Using the latest and the greatest of course.

@ghost
Copy link

ghost commented Jun 17, 2019

I do encounter the same problem with client 2.5.3 RC2 on Windows 10 Pro.
As far I could find, it mainly happens with jpg and png files >1 MB

@ghost
Copy link

ghost commented Jun 17, 2019

@camilasan Could this be related to / same issue as owncloud/client#7020 ?

possible Patch? owncloud/client@a58e439

@enoch85
Copy link
Member

enoch85 commented Jun 25, 2019

I think this can be closed casue I think I found the cause.

Everyone that have the app files_antivirus enabled, raise your hand. 🖐️

I noticed that clamav was really heavy on my CPU when I uploaded files in the client and I also had plenty of issues with HTTP/2 protocol error, so I thought, "wonder what happens if I disable the files_antivirus app?"

Well, no more issues, and the syncing got much faster.

@ghost
Copy link

ghost commented Jun 25, 2019

You might have a point there: I also have files_antivirus active, allthough my machine has more then anough cpu- and ram-power. It really shouldn't be a problem.

Question remains also, if the desktopclient or the files_antivirus app have a problem in combination which each other.

@enoch85
Copy link
Member

enoch85 commented Jun 25, 2019

allthough my machine has more then enough cpu- and ram-power. It really shouldn't be a problem.

I ran this test on a pretty decent Xeon CPU with 12 cores added to the system, so I think that doesn't matter, rather the files_antivirus app that have some flawed code. My best guess anyway.

@enoch85
Copy link
Member

enoch85 commented Jun 25, 2019

@Lars1963

Pretty funny that your avatar raises the hand btw. :D

Everyone that have the app files_antivirus enabled, raise your hand.

@ghost
Copy link

ghost commented Jun 25, 2019

I raised a issue on https://github.com/nextcloud/files_antivirus. May be someone over there has a idea.

@enoch85
Copy link
Member

enoch85 commented Jun 25, 2019

I'm closing this as it's most probably are related to the files_antivirus app or clamav.

Please reopen if you experience issues not related to the above.

@enoch85 enoch85 closed this as completed Jun 25, 2019
@xianx
Copy link

xianx commented Jun 26, 2019

This is not antivirus issue. Nexcloud Client throw error when HTTPS/2 is enabled on server. Where antivirus came to this issue? I dont understand. Its related to HTTPS/2 support on Nextcloud Desktop Client.

@enoch85
Copy link
Member

enoch85 commented Jun 26, 2019

@xianx so you are not running files_antivirus?

@xianx
Copy link

xianx commented Jun 26, 2019

@enoch85 nope.

@enoch85 enoch85 reopened this Jun 26, 2019
@xianx
Copy link

xianx commented Jun 26, 2019

On owncloud https://techtun.es/GeykDW they removed it https://techtun.es/OwBBvw

@solracsf
Copy link
Member

Subsidiary question, any of you are using nGinx as HTTP server?
In my case, im' using nGinx and not having that problem.

@ghost
Copy link

ghost commented Sep 10, 2019

Yes, I'm using NGINX and having this problem. Only solution for now is disabling http2-support for NGINX. This problem is also otherwise mentioned in combination with NGINX. see #16138

@enoch85
Copy link
Member

enoch85 commented Sep 10, 2019

@acs-ferreira I use Nginx as Reverse Proxy, and HTTP/2 is enabled on both sides.

@solracsf
Copy link
Member

OK, so this is not Webserver related. I'm also using files_antivirus app (ClamAV daemon not on the same server) and i can't reproduce...

@felinira
Copy link

I have this error too, no files_antivirus app and protocol error. Is there anything I can check to find out more? Server logs don't say anything...

@kibrovic
Copy link

Having the same issue on multiple devices:

OS: Debian 10 and Windows 10

Nextcloud version 2.5.1git
Using Qt 5.11.3, built against Qt 5.11.3
Using 'OpenSSL 1.1.1d 10 Sep 2019'

Windows is using 2.6.0

Server: nginx

For now, I'm downgrading to 2.3.3 which doesn't cause this problem.

Log on gist

File names replaced with FILE1,2,3. Problematic file is FILE1. I didn't include rest of the files throwing error (log show same thing).

It seems that problem is Qt http2 stack. OwnCloud disabled it

@MacLemon
Copy link

MacLemon commented Nov 21, 2019

Same problem started popping up here recently.

Server

  • Nextcloud 16.0.4, 16.0.5, 17.0.1
  • OS: FreeBSD 12.0
  • nginx 1.17.6
  • PHP 7.2.24
  • HTTP/2 enabled

Nextcloud Client

  • macOS 10.12.16 (High Sierra)
  • NextCloud app 2.6.0, 2.6.1

Verified Workaround

  • Downgrade to NextCloud Client 2.5.3release (build 20190724) without making any changes to the server setup. (Works fine with HTTP/S and Nextcloud 17.0.1)

@phonon112358
Copy link

Same issue here...
I use the Windows client (Version 2.6.2stable-Win64 (build 20191224)).
On my server, I have Debian 10, nginx 1.14.2, php 7.3, nextcloud 17.0.2.

To me, it seems that only some file formats aren't synchronised (e.g. .jpg), but others work (e.g. .pdf, .doc, .odt)... can you confirm?

As workaround, I disabled http2 in my nginx configuration for now. Everything works fine now.
However, I hope that this issue will be resolved soon!!!

@lucker999
Copy link

I can confirm that for some file extensions (for instance .sh) the windows client (Version 2.6.2stable-Win64 (build 20191224)) refuses to sync with server Nextcloud 18.0 on OS: FreeBSD 12.1-p2, PHP 7.3 with http2 enabled.

Also confirm that downgrading to 2.5.3daily-Win64 (build 20190725) completely eliminated the problem.

@EugenVau

This comment has been minimized.

@misch7
Copy link
Member

misch7 commented Mar 2, 2020

Also confirm that downgrading to 2.5.3daily-Win64 (build 20190725) completely eliminated the problem.

With #1823 in the 2.6.4 release HTTP/2 will be disabled by default for now and may be enabled manually by supplying the environment variable: OWNCLOUD_HTTP2_ENABLED=1

Please also see: #1397

@github-actions
Copy link

github-actions bot commented May 6, 2021

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label May 6, 2021
@github-actions
Copy link

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests