You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Of course, I can also directly use the wsk command line to trigger my test function:
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:
Therefore, I would like to ask how to adjust my system so that the following HTTP access errors will not occur.
My research team and I have encountered this obvious problem and would like to ask some experts for advice. @style95
The text was updated successfully, but these errors were encountered:
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.
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.
Of course, I can also directly use the wsk command line to trigger my test function:
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:
Therefore, I would like to ask how to adjust my system so that the following HTTP access errors will not occur.
My research team and I have encountered this obvious problem and would like to ask some experts for advice.
@style95
The text was updated successfully, but these errors were encountered: