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

help request: about add a route then all requst return 404 error #8132

Closed
vavikast opened this issue Oct 20, 2022 · 5 comments
Closed

help request: about add a route then all requst return 404 error #8132

vavikast opened this issue Oct 20, 2022 · 5 comments

Comments

@vavikast
Copy link

Description

Hello I'm Very newbie into API Gateway. I install apisix and apisix controller in kubernetes, but I use apisix controller only
install dashbord, mostly I use apisix + consul。now my apisix is ok until add a rule ,the rule local_proxy other domain,like that.
location /scrm-organization-api {
proxy_pass http://xxx,yyyy.com;
}
then you can use the local_proxy,but after a minutes . all request will return 404. include the dashboard,apisix-admin.
but the apisix logs only print 404, I can't get userful log .
the apisix can't use, but it look like ok, and the alway print the log.

this is ok :
企业微信截图_16662501419613
when add a rule :
image
image

after a minutes
all reuqest will 404.
企业微信截图_16662483851071
image
image

Environment

  • APISIX version (run apisix version): 2.14.1
  • Operating system (run uname -a): ID=alpine VERSION_ID=3.14.6
  • OpenResty / Nginx version (run openresty -V or nginx -V): openresty/1.19.9.1
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info): 3.4.18
  • APISIX Dashboard version, if relevant: 2.13.0
  • LuaRocks version, for installation issues (run luarocks --version): 3.8.0
  • Hem info: NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
    apisix ingress-apisix 1 2022-06-27 12:05:12.308797023 +0800 CST deployed apisix-0.10.0 2.14.1
@tzssangglass
Copy link
Member

tzssangglass commented Oct 21, 2022

From your logs and accordingly, the 404 is returned form upstream, not from APISIX.

@vavikast
Copy link
Author

when I add the rule , all request will return 404, not only the proxy domain, it's mean the apisix can't handle any request just return 404. I can get response from the upstream direct connection。
I find apisix memory increase,so i suspect apisix endless loop。
what should i do next

@tzssangglass
Copy link
Member

I observed that you added several routes with uri /*. You can adjust the logging level in apisix and restart again, and see if the route hit by the 404 request is the expected route.

when I add the rule , all request will return 404,

Are you saying that the admin API will also 404?

If possible, please provide minimal replication use cases.

I need to know.

  1. what was the route in etcd before the 404

  2. what routing configuration was added and then APISIX suddenly returned all 404

  3. what is the test request

  4. the APISIX configuration file

so I can reproduce it in my local.

@vavikast
Copy link
Author

I deploy anoth one, but i can't reproduce it.
so can you remote control my computer, or you send your email to me ,you direct use the apisix .

@vavikast
Copy link
Author

Thanks for tzssangglass, The key to solve problem is the fix : #7466, I upgrade the apisix to 15.0, It's fine .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants