[GH-ISSUE #1550] HTTP3 + QUIC support

kerem commented

2026-02-26 06:36:04 +03:00

Owner

Originally created by @nyanmark on GitHub (Nov 2, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1550

With QUIC support being in most of today's browsers, and tools already excising to enable QUIC within nginx I believe it would be a good idea to add the support to NPM helping users speed up those huge video streams.

Originally created by @nyanmark on GitHub (Nov 2, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1550 With QUIC support being in most of today's browsers, and tools already excising to enable QUIC within nginx I believe it would be a good idea to add the support to NPM helping users speed up those huge video streams.

kerem added the

enhancement

label

2026-02-26 06:36:04 +03:00

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@iamgadgetman commented on GitHub (Jun 2, 2022):

It would be nice to be able to use NPM to connect to internet radio servers that use QUIC.

@iamgadgetman commented on GitHub (Jun 2, 2022): It would be nice to be able to use NPM to connect to internet radio servers that use QUIC.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@ingarb commented on GitHub (Oct 7, 2022):

Hope this can be added to NPM. I would imagine if you don't have QUIC Google might rank your site lower copared to a site that does have QUIC. It would also make your site a little fit faster - also leading to a higher ranking.

@ingarb commented on GitHub (Oct 7, 2022): Hope this can be added to NPM. I would imagine if you don't have QUIC Google might rank your site lower copared to a site that does have QUIC. It would also make your site a little fit faster - also leading to a higher ranking.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@danfratamico commented on GitHub (Dec 20, 2022):

I totally agree here, this needs to be a top priority.

@danfratamico commented on GitHub (Dec 20, 2022): I totally agree here, this needs to be a top priority.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@timnolte commented on GitHub (Jan 21, 2023):

I was going about the route of using NPM in front of a Docker/container setup only to realize that although the web server I'm running should support QUIC & HTTP/3 unfortunately NPM doesn't. Having NPM in front of any containers/services I start up is very handy but I'd sure like the ability to use QUIC & HTTP/3. Keeping an eye on this.

@timnolte commented on GitHub (Jan 21, 2023): I was going about the route of using NPM in front of a Docker/container setup only to realize that although the web server I'm running should support QUIC & HTTP/3 unfortunately NPM doesn't. Having NPM in front of any containers/services I start up is very handy but I'd sure like the ability to use QUIC & HTTP/3. Keeping an eye on this.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@nonlinearsugar commented on GitHub (Apr 20, 2023):

It's still experimental/beta in Nginx and only available as separate packages/in a separate branch. https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/ https://github.com/nginx-quic/nginx-quic

While I lend my support to those asking, I don't think this can/should go anywhere on the NPM side before Nginx merge it into their stable branch.

@nonlinearsugar commented on GitHub (Apr 20, 2023): It's still experimental/beta in Nginx and only available as separate packages/in a separate branch. https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/ https://github.com/nginx-quic/nginx-quic While I lend my support to those asking, I don't think this can/should go anywhere on the NPM side before Nginx merge it into their stable branch.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@thesantiagosp commented on GitHub (Jun 3, 2023):

It's still experimental/beta in Nginx and only available as separate packages/in a separate branch. https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/ https://github.com/nginx-quic/nginx-quic

While I lend my support to those asking, I don't think this can/should go anywhere on the NPM side before Nginx merge it into their stable branch.

It's already merged, right?

@thesantiagosp commented on GitHub (Jun 3, 2023): > It's still experimental/beta in Nginx and only available as separate packages/in a separate branch. https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/ https://github.com/nginx-quic/nginx-quic > > While I lend my support to those asking, I don't think this can/should go anywhere on the NPM side before Nginx merge it into their stable branch. It's already merged, right?

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@nonlinearsugar commented on GitHub (Jun 3, 2023):

Yeah. Time permitting, I think this is ready for @jc21 to action.

https://nginx.org/en/docs/quic.html

@nonlinearsugar commented on GitHub (Jun 3, 2023): Yeah. Time permitting, I think this is ready for @jc21 to action. https://nginx.org/en/docs/quic.html

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@squadramunter commented on GitHub (Sep 2, 2023):

Any update on this?

@squadramunter commented on GitHub (Sep 2, 2023): Any update on this?

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@multipliedtwice commented on GitHub (Sep 3, 2023):

Would be amazing to have it

@multipliedtwice commented on GitHub (Sep 3, 2023): Would be amazing to have it

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@stanthewizzard commented on GitHub (Sep 19, 2023):

would be awesome ... no news ?

NGINX now officially supports HTTP/3 with QUIC. It is available as part of NGINX 1.25.1 mainline version for open source users and NGINX Plus R30 for enterprise customers.]

@stanthewizzard commented on GitHub (Sep 19, 2023): would be awesome ... no news ? NGINX now officially supports HTTP/3 with QUIC. It is available as part of NGINX 1.25.1 mainline version for open source users and [NGINX Plus R30](https://www.nginx.com/blog/nginx-plus-r30-released/) for enterprise customers.]

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@llek1000 commented on GitHub (Sep 22, 2023):

I hope we will see this added in the near future, I am already using NGINX with HTTP/3 on some of my servers and it can improve things significantly with larger sites!
Please, this needs to be implemented. As the comment above said, it is already in mainline version of NGINX.

@llek1000 commented on GitHub (Sep 22, 2023): I hope we will see this added in the near future, I am already using NGINX with HTTP/3 on some of my servers and it can improve things significantly with larger sites! Please, this needs to be implemented. As the comment above said, it is already in mainline version of NGINX.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@devius commented on GitHub (Nov 4, 2023):

so please, me too....
I am waiting for it.....

@devius commented on GitHub (Nov 4, 2023): so please, me too.... I am waiting for it.....

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@LDprg commented on GitHub (Nov 8, 2023):

Also all big Websites now support http/3 (Google, Microsoft, Cloudflare, Amazon, Meta). So I think it is getting time for a implementation.

@LDprg commented on GitHub (Nov 8, 2023): Also all big Websites now support http/3 (Google, Microsoft, Cloudflare, Amazon, Meta). So I think it is getting time for a implementation.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@FluffyDiscord commented on GitHub (Jan 6, 2024):

Any updates?

@FluffyDiscord commented on GitHub (Jan 6, 2024): Any updates?

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@fengyuclub commented on GitHub (Jan 12, 2024):

Any updates?

@fengyuclub commented on GitHub (Jan 12, 2024): Any updates?

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@iwyz0 commented on GitHub (Jan 15, 2024):

Any updates?

@iwyz0 commented on GitHub (Jan 15, 2024): Any updates?

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@scampower3 commented on GitHub (Jan 16, 2024):

OpenResty 1.25.3.1 added support for HTTP/3.

@scampower3 commented on GitHub (Jan 16, 2024): OpenResty 1.25.3.1 added support for HTTP/3.

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@lateautumn233 commented on GitHub (Jan 26, 2024):

Hello, I have tried to add HTP3 support for nginx-proxy-manager

If you are interested in this, you can give it a try

docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/
Source code: https://github.com/lateautumn233/nginx-proxy-manager

@lateautumn233 commented on GitHub (Jan 26, 2024): Hello, I have tried to add HTP3 support for nginx-proxy-manager If you are interested in this, you can give it a try docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/ Source code: https://github.com/lateautumn233/nginx-proxy-manager

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@iwyz0 commented on GitHub (Jan 26, 2024):

Hello, I have tried to add HTP3 support for nginx-proxy-manager

If you are interested in this, you can give it a try

docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/ Source code: https://github.com/lateautumn233/nginx-proxy-manager

You did what they couldn't do. Thank you

@iwyz0 commented on GitHub (Jan 26, 2024): > Hello, I have tried to add HTP3 support for nginx-proxy-manager > > If you are interested in this, you can give it a try > > docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/ Source code: https://github.com/lateautumn233/nginx-proxy-manager You did what they couldn't do. Thank you

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@daedric7 commented on GitHub (Jan 26, 2024):

Should this be as simple as replacing docker image in the compose?

@daedric7 commented on GitHub (Jan 26, 2024): Should this be as simple as replacing docker image in the compose?

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@lateautumn233 commented on GitHub (Jan 26, 2024):

Yes
But currently only the amd64 architecture is available

lateautumn233
@.***

---Original---
From: @.>
Date: Sat, Jan 27, 2024 01:21 AM
To: @.>;
Cc: @.@.>;
Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550)

Should this be as simple as replacing docker image in the compose?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

@lateautumn233 commented on GitHub (Jan 26, 2024): Yes But currently only the amd64 architecture is available lateautumn233 ***@***.*** ---Original--- From: ***@***.***> Date: Sat, Jan 27, 2024 01:21 AM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550) Should this be as simple as replacing docker image in the compose? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

kerem commented

2026-02-26 06:36:05 +03:00

Author

Owner

@daedric7 commented on GitHub (Jan 26, 2024):

Yes But currently only the amd64 architecture is available lateautumn233 @.***
…
---Original--- From: @.> Date: Sat, Jan 27, 2024 01:21 AM To: @.>; Cc: @.@.>; Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550) Should this be as simple as replacing docker image in the compose? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

I did it.

It seems H3 is being enabled:

npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      Current database version: none
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] Migrating Up...
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] proxy_host Table altered
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] redirection_host Table altered
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] dead_host Table altered

But, in chrome, only H2 is being used:

I'll debug further later tonight.

@daedric7 commented on GitHub (Jan 26, 2024): > Yes But currently only the amd64 architecture is available lateautumn233 ***@***.*** > […](#) > ---Original--- From: ***@***.***> Date: Sat, Jan 27, 2024 01:21 AM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550) Should this be as simple as replacing docker image in the compose? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***> I did it. It seems H3 is being enabled: ``` npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info Current database version: none npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] Migrating Up... npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] proxy_host Table altered npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] redirection_host Table altered npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] dead_host Table altered ``` But, in chrome, only H2 is being used: ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/4562461/d24bbba8-743c-487a-84fc-628c74918218) I'll debug further later tonight.

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@daedric7 commented on GitHub (Jan 26, 2024):

Yes But currently only the amd64 architecture is available lateautumn233 @.***
…
---Original--- From: @.> Date: Sat, Jan 27, 2024 01:21 AM To: _@**._>; Cc: _@.@._>; Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550) Should this be as simple as replacing docker image in the compose? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: _@_.*>

I did it.

It seems H3 is being enabled:
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      Current database version: none
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] Migrating Up...
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] proxy_host Table altered
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] redirection_host Table altered
npm-1  | [1/26/2024] [5:28:15 PM] [Migrate  ] › ℹ  info      [http3_support] dead_host Table altered
But, in chrome, only H2 is being used:

I'll debug further later tonight.

Disregard, i had to refresh the NPM ui to get the new option showing :)

@daedric7 commented on GitHub (Jan 26, 2024): > > Yes But currently only the amd64 architecture is available lateautumn233 _**@**_.*** > > […](#) > > ---Original--- From: _**@**_._**> Date: Sat, Jan 27, 2024 01:21 AM To: _**@**_.**_>; Cc: _**@**_._**_**@**_.**_>; Subject: Re: [NginxProxyManager/nginx-proxy-manager] HTTP3 + QUIC support(Issue #1550) Should this be as simple as replacing docker image in the compose? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: _**@**_.***> > > I did it. > > It seems H3 is being enabled: > > ``` > npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info Current database version: none > npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] Migrating Up... > npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] proxy_host Table altered > npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] redirection_host Table altered > npm-1 | [1/26/2024] [5:28:15 PM] [Migrate ] › ℹ info [http3_support] dead_host Table altered > ``` > > But, in chrome, only H2 is being used: > > ![image](https://private-user-images.githubusercontent.com/4562461/300060030-d24bbba8-743c-487a-84fc-628c74918218.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDYyOTA3MDYsIm5iZiI6MTcwNjI5MDQwNiwicGF0aCI6Ii80NTYyNDYxLzMwMDA2MDAzMC1kMjRiYmJhOC03NDNjLTQ4N2EtODRmYy02MjhjNzQ5MTgyMTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDEyNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDAxMjZUMTczMzI2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjQ2ZmU0NmQwYmI1N2ZhZDIxNGRjYWY4ZWZhMDJmYjIxY2M4MDMyYjFlZDc5Y2MwZmI3NTIxZTJmOTQyYmZkNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Onma1EoULfGpHRbUtFV26mLnZ91TEaOi27Gfx5D8M5w) > > I'll debug further later tonight. Disregard, i had to refresh the NPM ui to get the new option showing :)

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@lateautumn233 commented on GitHub (Feb 3, 2024):

Hello, I have tried to add HTP3 support for nginx-proxy-manager

If you are interested in this, you can give it a try

docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/ Source code: https://github.com/lateautumn233/nginx-proxy-manager

Other architectures
docker pull lateautumn233/nginx-proxy-manager:test

I need more testing, and if there are no issues, I will try to contribute upstream

@lateautumn233 commented on GitHub (Feb 3, 2024): > Hello, I have tried to add HTP3 support for nginx-proxy-manager > > If you are interested in this, you can give it a try > > docker: https://hub.docker.com/repository/docker/lateautumn233/nginx-proxy-manager/ Source code: https://github.com/lateautumn233/nginx-proxy-manager Other architectures `docker pull lateautumn233/nginx-proxy-manager:test` I need more testing, and if there are no issues, I will try to contribute upstream

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@RainmakerRaw commented on GitHub (Feb 14, 2024):

Other architectures docker pull lateautumn233/nginx-proxy-manager:test

I need more testing, and if there are no issues, I will try to contribute upstream

Working a-OK on arm64 (Radxa Rock 5 model B), for me. Page loads confirm http/3 and it's working perfectly. I can finally use NPM again!

@RainmakerRaw commented on GitHub (Feb 14, 2024): > Other architectures `docker pull lateautumn233/nginx-proxy-manager:test` > > I need more testing, and if there are no issues, I will try to contribute upstream Working a-OK on arm64 (Radxa Rock 5 model B), for me. Page loads confirm http/3 and it's working perfectly. I can finally use NPM again!

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@timnolte commented on GitHub (Feb 17, 2024):

FYI, if you haven't seen recently that there is at least 1 open CVE for HTTP/3 + QUIC in Nginx. It was actually the subject of one of the core devs leaving the project and forking Nginx. I'd be careful about pushing this forward as the support is still marked experimental.

@timnolte commented on GitHub (Feb 17, 2024): FYI, if you haven't seen recently that there is at least 1 open CVE for HTTP/3 + QUIC in Nginx. It was actually the subject of one of the core devs leaving the project and forking Nginx. I'd be careful about pushing this forward as the support is still marked experimental.

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@timnolte commented on GitHub (Feb 17, 2024):

Here are the details for reference. https://my.f5.com/manage/s/article/K000138444

@timnolte commented on GitHub (Feb 17, 2024): Here are the details for reference. https://my.f5.com/manage/s/article/K000138444

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@timnolte commented on GitHub (Feb 17, 2024):

It does look like a fixed version was released, however there is a part of me that is concerned that the HTTP/3 + QUIC module is considered experimental still.

@timnolte commented on GitHub (Feb 17, 2024): It does look like a fixed version was released, however there is a part of me that is concerned that the HTTP/3 + QUIC module is considered experimental still.

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@lastsamurai26 commented on GitHub (Feb 23, 2024):

Portainer didn't show that udp port 443 or 80 is open ?

i tried this https://github.com/ZoeyVid/NPMplus
However, since I work with docker networks and no ports are free, only 443 and 80 somehow don't work for me :-(

@lastsamurai26 commented on GitHub (Feb 23, 2024): Portainer didn't show that udp port 443 or 80 is open ? ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/3257844/dd6943e7-ebcb-400f-b0ef-8f10c60fd193) i tried this https://github.com/ZoeyVid/NPMplus However, since I work with docker networks and no ports are free, only 443 and 80 somehow don't work for me :-(

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@tgarif commented on GitHub (Mar 9, 2024):

Hi @lateautumn233, I tried your version of NPM + quic enabled but somehow after inspecting the network tab it seems like the protocol doesn't use http3 but instead it uses http/1.1 or http2 (if enabled). I did expose port 443/udp from the docker compose already.

Another thing that I've tried is to add reuseport at the listen directive for quic and it does work if I have only one proxy host. If I add a new proxy host, it will not work with reuseport. Any advise you can give on my situation?

@tgarif commented on GitHub (Mar 9, 2024): Hi @lateautumn233, I tried your version of NPM + quic enabled but somehow after inspecting the network tab it seems like the protocol doesn't use http3 but instead it uses http/1.1 or http2 (if enabled). I did expose port 443/udp from the docker compose already. Another thing that I've tried is to add `reuseport` at the listen directive for quic and it does work if I have only one proxy host. If I add a new proxy host, it will not work with `reuseport`. Any advise you can give on my situation?

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@lateautumn233 commented on GitHub (Mar 9, 2024):

Hi @lateautumn233, I tried your version of NPM + quic enabled but somehow after inspecting the network tab it seems like the protocol doesn't use http3 but instead it uses http/1.1 or http2 (if enabled). I did expose port 443/udp from the docker compose already.

Another thing that I've tried is to add reuseport at the listen directive for quic and it does work if I have only one proxy host. If I add a new proxy host, it will not work with reuseport. Any advise you can give on my situation?

@lateautumn233 commented on GitHub (Mar 9, 2024): > Hi @lateautumn233, I tried your version of NPM + quic enabled but somehow after inspecting the network tab it seems like the protocol doesn't use http3 but instead it uses http/1.1 or http2 (if enabled). I did expose port 443/udp from the docker compose already. > > Another thing that I've tried is to add `reuseport` at the listen directive for quic and it does work if I have only one proxy host. If I add a new proxy host, it will not work with `reuseport`. Any advise you can give on my situation? Maybe it's related to this https://stackoverflow.com/questions/76348128/enabling-quic-http-3-on-multiple-domains-with-nginx-1-25

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@vincent1890 commented on GitHub (Aug 17, 2024):

update pls ?
https://nginx.org/en/docs/quic.html

@vincent1890 commented on GitHub (Aug 17, 2024): update pls ? https://nginx.org/en/docs/quic.html

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@stanthewizzard commented on GitHub (Aug 17, 2024):

On my side I siwtched to caddy. Conf file is finally easier. Http3 out of the box

@stanthewizzard commented on GitHub (Aug 17, 2024): On my side I siwtched to caddy. Conf file is finally easier. Http3 out of the box

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@hongmd commented on GitHub (Aug 23, 2024):

Any update? halou

@hongmd commented on GitHub (Aug 23, 2024): Any update? halou

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@iwyz0 commented on GitHub (Aug 23, 2024):

http3 is actually very important, I don't understand why it isn't given priority.

@iwyz0 commented on GitHub (Aug 23, 2024): http3 is actually very important, I don't understand why it isn't given priority.

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@vincent1890 commented on GitHub (Aug 30, 2024):

Any update on this? @jc21

@vincent1890 commented on GitHub (Aug 30, 2024): Any update on this? @jc21

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@hersche commented on GitHub (Nov 1, 2024):

hi lateautumn233, i would like to ask if you can update your image on docker-hub. this project added a acme-plugin recently which i use and which does not allow me to use your version.

hopefully that http3-change is gonna be integrated here soon. thanks a lot for your work!

@hersche commented on GitHub (Nov 1, 2024): hi [lateautumn233](https://github.com/lateautumn233), i would like to ask if you can update your image on docker-hub. this project added a acme-plugin recently which i use and which does not allow me to use your version. hopefully that http3-change is gonna be integrated here soon. thanks a lot for your work!

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@dpalic commented on GitHub (May 13, 2025):

any update on this issue? now 3.5y old

@dpalic commented on GitHub (May 13, 2025): any update on this issue? now 3.5y old

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@hongmd commented on GitHub (May 13, 2025):

Moving to Caddy 👍

@hongmd commented on GitHub (May 13, 2025): Moving to Caddy 👍

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@sleighton commented on GitHub (Sep 9, 2025):

Guys, no need to announce. Just go.

@sleighton commented on GitHub (Sep 9, 2025): Guys, no need to announce. Just go.

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@taimadoCE commented on GitHub (Oct 10, 2025):

Nothing about it? Is it planned?

@taimadoCE commented on GitHub (Oct 10, 2025): Nothing about it? Is it planned?

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@thefeli73 commented on GitHub (Oct 10, 2025):

Nothing about it? Is it planned?

@taimadoCE check out npm+ (fork) https://github.com/ZoeyVid/NPMplus?tab=readme-ov-file#compatibility-to-upstream

@thefeli73 commented on GitHub (Oct 10, 2025): > Nothing about it? Is it planned? @taimadoCE check out npm+ (fork) https://github.com/ZoeyVid/NPMplus?tab=readme-ov-file#compatibility-to-upstream

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@taimadoCE commented on GitHub (Oct 10, 2025):

Nothing about it? Is it planned?

@taimadoCE check out npm+ (fork) https://github.com/ZoeyVid/NPMplus?tab=readme-ov-file#compatibility-to-upstream

I'm in linux/arm/v7. That fork doesn't support it.

@taimadoCE commented on GitHub (Oct 10, 2025): > > Nothing about it? Is it planned? > > [@taimadoCE](https://github.com/taimadoCE) check out npm+ (fork) https://github.com/ZoeyVid/NPMplus?tab=readme-ov-file#compatibility-to-upstream I'm in linux/arm/v7. That fork doesn't support it.

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@LDprg commented on GitHub (Oct 10, 2025):

@taimadoCE use caddy instead, it has http3 support . You won't get a gui, but I switched some time ago and I am very happy with it.

@LDprg commented on GitHub (Oct 10, 2025): @taimadoCE use caddy instead, it has http3 support . You won't get a gui, but I switched some time ago and I am very happy with it.

kerem commented

2026-02-26 06:36:06 +03:00

Author

Owner

@taimadoCE commented on GitHub (Oct 10, 2025):

@taimadoCE use caddy instead, it has http3 support . You won't get a gui, but I switched some time ago and I am very happy with it.

Yes...I need to investigate how to migrate my local domains with duckDNS to get http3 support on them...

Example: portainer.myname.duckdns.org

@taimadoCE commented on GitHub (Oct 10, 2025): > [@taimadoCE](https://github.com/taimadoCE) use caddy instead, it has http3 support . You won't get a gui, but I switched some time ago and I am very happy with it. Yes...I need to investigate how to migrate my local domains with duckDNS to get http3 support on them... Example: portainer.myname.duckdns.org

Rows
Columns

[GH-ISSUE #1550] HTTP3 + QUIC support #1176