-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Compile tengine-3.0.0 with xquic 1.6.1 failed #1875
Comments
follow the https://github.com/alibaba/tengine/blob/master/modules/ngx_http_xquic_module/README.md use xquic-1.6.0 and Tongsuo-8.3.2 works |
and by the way, follow the guide , I configue the nginx, but all the site on the nginx cannot be opened, the error log says:
|
and how to generate the /usr/local/tengine/ssl/default-fake-certificate.pem; for testing? |
Tengine does NOT integrate with xquic latest version currently. Pls. complite tengine 3.0.0 with xquic 1.6.0 specifically. XQUIC_VERSION=1.6.0 wget -c "https://github.com/alibaba/xquic/archive/refs/tags/v1.6.0.tar.gz" |
Thank you @lianglli , and how to generate the /usr/local/tengine/ssl/default-fake-certificate.pem; for testing? pls give some tips, I can't launch the nginx , it always says: "2023/10/13 15:36:15 [emerg] 225267#0: |xquic|xqc_engine_create: fail| |
The tengine-ingress docker image has the default-fake-certificate.pem. BTW, search "generate a self-signed SSL certificate on Linux" from google |
@lianglli of cause, I know how to "generate a self-signed SSL certificate on Linux" and always use the commercial ssl cert for the online sites. I think my question should be , |
Ⅰ. Issue Description
Compile tengine-3.0.0 with xquic 1.6.1 failed
Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅵ. Environment:
sbin/nginx -V
): tengine3.0.0uname -a
): Linux dev4 4.18.0-477.15.1.el8_8.x86_64 fixed bugs of the limit_req module #1 SMP Wed Jun 28 15:04:18 UTC 2023 x86_64 x86_64 x86_64 GNU/LinuxThe text was updated successfully, but these errors were encountered: