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

[BUG] HTTP/2 disabled? #330

Closed
1 task done
motionthings opened this issue Jul 7, 2023 · 2 comments
Closed
1 task done

[BUG] HTTP/2 disabled? #330

motionthings opened this issue Jul 7, 2023 · 2 comments

Comments

@motionthings
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Not really a bug from you.
More a question from me.

After the latest update i got a lot of 504 errors.
I had to disable HTTP/2 in my proxy (HA-proxy) to make it work.
Did someone disable HTTP/2 support in the latest release?

Expected Behavior

Not really something I need but I had to disable HTTP/2 for the container.

Steps To Reproduce

OPNsense 23.1.11 with HA-proxy 4.1
Unraid 6.12.2

Enable HTTP/2 in HA-proxy and you'll get 504 errors on the nextcloud instance.
I've had the same config in HA-proxy for years without any problems.

Environment

- OS:Unraid/Slack
- How docker service was installed: Came with Unraid. Docker version is 20.10.24.

CPU architecture

x86-64

Docker creation

Created through the Unraid appstore

Container logs

Logs have no errors since this is a Proxy config problem.
@github-actions
Copy link

github-actions bot commented Jul 7, 2023

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@nemchik
Copy link
Member

nemchik commented Jul 8, 2023

As far as I can tell, nginx still does not support proxying http2 (ex: if you were using swag, or another reverse proxy that uses nginx, I am not sure about haproxy). Ref: linuxserver/reverse-proxy-confs#576 we did add the http2 directive to all proxy confs to solve a different issue, and it should also be included by default in the nextcloud nginx confs

listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server;

Check your container logs to be sure the nginx confs are up to date (it will list which ones are not).

Also, haproxy does not use nginx and you are proxying port 80 it would not have http2 as that's only set on port 443.

If the client connecting to your proxy can connect with http2 to the proxy that should be plenty, and having the connection be http2 from the proxy to nextcloud shouldn't make a huge difference.

@nemchik nemchik closed this as completed Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants