Skip to content
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

Closed
jackk01 opened this issue May 7, 2022 · 10 comments
Assignees

Comments

@jackk01
Copy link

jackk01 commented May 7, 2022

Current Behavior

When using apisixroute to expose services, you will often be redirected to port 9080 or 9443 of the apisix-gateway container.
image

Expected Behavior

No response

Error Logs

No response

Steps to Reproduce

helm install

Environment

  • APISIX version (run apisix version):
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):
@jackk01
Copy link
Author

jackk01 commented May 7, 2022

helm chart info:
apiVersion: v2
appVersion: 2.13.1

@tzssangglass tzssangglass changed the title bug: 使用apisixroute暴露服务时,会经常重定向到apisix-gateway容器的9080或者9443端口 bug: when using apisixroute to expose the service, it will often redirect to port 9080 or 9443 of the apisix-gateway container May 7, 2022
@tzssangglass
Copy link
Member

I think this is a known issue that APISIX and Jenkins work unhealthy and we are fixing it.

ref: #4942

@jackk01
Copy link
Author

jackk01 commented Jun 23, 2022

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!!!

@tzssangglass
Copy link
Member

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.

@github-actions
Copy link

github-actions bot commented Jun 9, 2023

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.

@github-actions github-actions bot added the stale label Jun 9, 2023
@adriano-brito-ts
Copy link

adriano-brito-ts commented Jun 22, 2023

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
Metallb 0.13.9
APISIX Gateway 3.3.0
APISIX Ingress Controller 1.6.1

Any clue when this issue will be fixed?

Thanks!

@github-actions github-actions bot removed the stale label Jun 23, 2023
@nilimaomni
Copy link

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?

@Nainterceptor
Copy link

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 🤷‍♂️

@shreemaan-abhishek shreemaan-abhishek moved this to 📋 Backlog in Apache APISIX backlog Dec 29, 2023
@Revolyssup Revolyssup self-assigned this Jan 21, 2024
@Revolyssup Revolyssup moved this from 📋 Backlog to 🏗 In progress in Apache APISIX backlog Jan 21, 2024
@Revolyssup
Copy link
Contributor

@Nainterceptor This issue should be fixed for ingress controller with this solution. #4942 (comment)

@Revolyssup
Copy link
Contributor

This issue should be fixed for ingress controller with this solution. #4942 (comment)
Please reopen if needed

@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Apache APISIX backlog Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

6 participants