mirror of
https://github.com/cloudpanel-io/cloudpanel-ce.git
synced 2026-04-05 20:31:58 +02:00
invalid parameter "quic" on new sites for Ubuntu 22.04 aarch64 (nginx/1.21.4) - Vhost Template Mismatch
#30
Reference in New Issue
Block a user
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 @w3K-one on 10/27/2025
CloudPanel version(s) affected
2.5.2
Description
Bug Description
On a CloudPanel 2.5.2 installation running on Ubuntu 22.04.5 LTS (aarch64/ARM64), Nginx fails to start after a new site is created and the server is restarted. One can also see the failures if vhost is edited on the CloudPanel web interface.
The error log (and
nginx -t) showsnginx: [emerg] invalid parameter "quic".This appears to be a version mismatch:
quic,http3 off;) directives.d2xpdm4jldf31f.cloudfront.net) provides an Nginx binary (1.21.4-15+clp-jammy) that was not compiled with HTTP/3 support (--with-http_v3_module).include /etc/nginx/global_settings, which does not exist in this package.Environment
aarch64(ARM64)nginx/1.21.4(Full package:1.21.4-15+clp-jammy)Nginx Build Configuration (
nginx -V)The installed Nginx build is missing the required HTTP/3 module. Note the presence of
--with-http_v2_modulebut the absence of--with-http_v3_module.How to reproduce
To Reproduce
nginx -tto see the cascade of errors, starting withinvalid parameter "quic".Possible Solution
Workaround / Manual Fix
To get the site working, the vhost file generated by CloudPanel must be manually edited to remove the incompatible directives and add the compatible ones.
This involves:
quiclisten lines.http2 on;andhttp3 off;lines.http2to thelisten 443 ssllines (which this Nginx build does support)./etc/nginx/global_settingsfile.Here is a
diffof the generated file vs. the working file:Proposed Solution
The Nginx binary provided in the CloudPanel
aarch64repository for Jammy should be re-compiled with HTTP/3 support (--with-http_v3_module) to match the vhost templates generatedAdditional Context
No response