-
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
bug: when using apisixroute to expose the service, it will often redirect to port 9080 or 9443 of the apisix-gateway container #7003
Comments
helm chart info: |
I think this is a known issue that APISIX and Jenkins work unhealthy and we are fixing it. ref: #4942 |
@tzssangglass @tao12345666333 Upgrade to APISIX v2.14.1, The problem still exists!!! |
pls determine if your question is the same as #4942. |
This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions. |
Also facing this issue, using APISIX with Keycloak + OpenID plugin. Setting redirect plugin with "http_to_https: true" it returns "domain:9443/uri", it should return port 443 instead of 9443! Kubernetes 1.26.1 Any clue when this issue will be fixed? Thanks! |
I'm also facing same issue. Trying to expose keycloak using apisix ingress controller, When hitting admin it returns "http://domain.com:9080/admin" (pending). Any solution for this issue? |
Same issue here using apisix ingress controller and keycloak, after few days of trying to find a workaround (like setting up proxy protocol...), we are finally using haproxy for keycloak 🤷♂️ |
@Nainterceptor This issue should be fixed for ingress controller with this solution. #4942 (comment) |
This issue should be fixed for ingress controller with this solution. #4942 (comment) |
Current Behavior
When using apisixroute to expose services, you will often be redirected to port 9080 or 9443 of the apisix-gateway container.
![image](https://user-images.githubusercontent.com/62927162/167243486-02c971f7-b541-4520-bdf4-c9a6ad247c09.png)
Expected Behavior
No response
Error Logs
No response
Steps to Reproduce
helm install
Environment
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: