mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #264] Unable to disable http2 #234
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#234
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hashimea on GitHub (Dec 25, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/264
Checklist
jc21/nginx-proxy-manager:latestdocker image?yes
sure
Describe the bug
Unable to disable http2 after enabling it for a host conf.
I checked the http2_enabled value in the database and it is 0. but still the configuration generated with http2 when saving (without http2 selection)
v2.0.14
To Reproduce
Steps to reproduce the behavior:
Expected behavior
not adding http2 to the configuration when database http2_enabled value is 0
Screenshots
If applicable, add screenshots to help explain your problem.
Operating System
ubuntu 19 + docker
@miguelwill commented on GitHub (Feb 9, 2020):
grep listen *.conf :
70.conf:listen 443 ssl http2;
71.conf: listen 80;
72.conf: listen 80;
72.conf:listen 443 ssl http2;
73.conf: listen 80;
74.conf: listen 80;
74.conf:listen 443 ssl http2;
7.conf: listen 80;
8.conf: listen 80;
8.conf:listen 443 ssl http2;
9.conf: listen 80;
as you can see, the http2 enablement filter defined in the template is not being applied correctly, and http2 is enabled when the host is created
@hashimea commented on GitHub (Feb 10, 2020):
@miguelwill http2 is a server-wide port-based configuration. So i think it will be better to take it out from single hosts to some global setting
@ghost commented on GitHub (Jul 30, 2022):
Where / how do i disable http2 globally then? i have the same issue
@ghost commented on GitHub (Jul 30, 2022):
i remote connected into my NPM virtual machine and navigated to the location where my config files are for each proxy host;
cd data/nginx/proxy_hostthen manually edited each of the configs in that location to remove the text "https2" from each entry. i also disabled every example of https2 on switch in the GUI.im not sure how to apply these changes other than just saving the config file and restarting the VM. this has 'saved' the changes within each of the files however the issues im facing casued by enabled https2 is still present.
@ghost commented on GitHub (Sep 7, 2022):
returning to this as its still an issue for me - where and how do we do make this change? could you explain a little more?
@FroggMaster commented on GitHub (Oct 25, 2022):
I'd like some more information on how to disable HTTP2 globally as well.
I'm currently encounter some problems with NGINX/HTTP2 and the easiest solution is to globally disable it but I'm not entirely certain how to do this with NPM.
@github-actions[bot] commented on GitHub (Mar 31, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 11, 2025):
Issue was closed due to inactivity.