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

Web function 400 Bad Request #5456

Open
QWQyyy opened this issue Jan 8, 2024 · 1 comment
Open

Web function 400 Bad Request #5456

QWQyyy opened this issue Jan 8, 2024 · 1 comment

Comments

@QWQyyy
Copy link

QWQyyy commented Jan 8, 2024

Sir,
I'm getting 400 badgateway error with my NodeJS function (NodeJS 16 runtime)
My OpenWhisk cluster is fine, deployed based on K8s, no errors occur.
image
Of course, I can also directly use the wsk command line to trigger my test function:
image
This seems like everything is working fine, however I am unable to access my function via HTTP request, I have created the relevant POST request API and have HTTP access via the configured 31005 port:
image
image
Therefore, I would like to ask how to adjust my system so that the following HTTP access errors will not occur.
image
My research team and I have encountered this obvious problem and would like to ask some experts for advice.
@style95

@style95
Copy link
Member

style95 commented Jan 9, 2024

It seems you are using apigateway and I think it is not related to a webaction.
If your action is not a webaction, you need proper credentials to invoke your function.
Are you able to invoke your action without any API key?

And it just complains about the bad request, it's not easy to figure out the problem and reason with that.
There might be some logs in apigateway, nginx, controllers, etc.

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