-
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
help request: Erro 500 after update to version 3.4.2 #9931
Comments
This seems to be due to incorrect ssl configuration, not sure if it is caused by etcd. |
This is the full config.yml, so, I supose the other parameters are using some default.
|
If you use K3s, can you show the relevant SSL-related CRD information? For example, certificate information. |
I don't see the dashboard repository being updated actively maybe that is the reason? 🤔 |
Hi, I mistyped, target version is 3.4.1. The start version was 3.2.2. After some tests, version 3.3.0 also works perfectly, using certificates from ones loaded from dashboard or ingress. Failure is on version 3.4.1 only. |
After new tests, even start fresh, need this combination to see this problem:
|
lines 332 after "if " add " matched_ssl and " because matched_ssl perhaps nil.
This config does not excute at the h2 protocol, and the browser can reproduce it 2-3 minutes after opening the page. |
@zimbres, please use the admin API for loading certs/keys many users have reported compatibility issues with the dashboard and APISIX when managing keys/certs. |
For the latest test that I performed I loaded certs by referencing then with ApisixTls CR |
@zimbres, please share your route and upstream configurations. |
Hi
|
are you using the ingress controller and installing it using the helm chart? If yes, please share the helm chart installation command as well. Sorry for the hassle. |
No problem. Its Helm managed by Flux:
|
I'm in the same situation, installed on GKE using the helm chart (v1.5.1), I'm using the admin api directly for almost everything except the certificates that are added via ApisixTls resources and the ingress controller (which I understand also calls the admin api anyway). Initial requests appear to work fine, but after a while I get the same lua errors and apisix becomes unusable until I restart the pod. I have issues when browsing the dashboard via the gateway (using Brave), but also with a few express APIs, calling them via Thunder Client (in VSCode) works exactly once, then the gateway returns 500. Interestingly, calling the APIs via Insomnia works just fine, so some clients fare better than others. |
This is an intermitten bug seen during some load tests and on some particular browsers by other users. This is also being tracked here - #9610 |
Fix created for this and reasons explained here - #10066 |
3.5 fixes it. Thanks |
We can not reproduce the issue on the master branch anymore, because the commit #9903 after 3.4.1: adds ssl_client_hello_by_lua_block. This phase used by apisix always constructs ngx.ctx.matched_ssl: Lines 205 to 207 in f47c2d7
|
Description
I'm running apisix in a K3s kubernetes, only changes in default deployments are:
Routes are created via dashboard with HTTPS redirect enabled, also the certificates are loaded via dashboard.
In the version 3.2.2-debian container everything works like a charm. when updated to version 3.4.1-debian, in a regular browser window, only the first request works, the next ones fail with 500 Internal Server Error and the message is logged:
In a private windows of browser, works everything, the first and next requests.
By the way, I tried to move to version 3.4.1 to have loki plugin, but I could not find it on dashboard, what I missed?
Environment
apisix version
):3.4.1
uname -a
):Linux apisix-749c68bbd7-z7hsc 5.15.0-1039-oracle #45~20.04.1-Ubuntu SMP Fri Jul 14 16:53:50 UTC 2023 aarch64 GNU/Linux
openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):{"boot_time":1690738678,"version":"3.4.1","id":"c839d476-24bd-45cb-aba0-6fd237236c0c","hostname":"apisix-749c68bbd7-z7hsc","etcd_version":"3.5.0"
}3.0.1
luarocks --version
):luarocks: command not found
The text was updated successfully, but these errors were encountered: