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

Get https://172.17.0.1/api/v1/namespaces: x509: cannot validate certificate for 172.17.0.1 because it doesn't contain any IP SANs #1908

Closed
rhdotone opened this issue Feb 25, 2017 · 6 comments

Comments

@rhdotone
Copy link

Running :
./bin/wsk property set --namespace guest

error: Authenticated user does not have namespace 'guest '; set command failed: Get https://172.17.0.1/api/v1/namespaces: x509: cannot validate certificate for 172.17.0.1 because it doesn't contain any IP SANs

However if I run in insecure mode,

./bin/wsk -i property set --namespace guest

It sets fine.

Due to this when I try to set "Service Node Config" in Node-RED UI, I also get

[Error: Error encountered calling OpenWhisk: Error: self signed certificate]

I am assuming it is because I cannot setup insecure from Node-RED

Is there anyway I can fix this certificate issue in openwhisk?

@rabbah
Copy link
Member

rabbah commented Feb 25, 2017

You can use certbot to generate a signed certificate https://certbot.eff.org/.

@rabbah
Copy link
Member

rabbah commented Feb 25, 2017

Did you try to disable TLS for nodered? :

Try that by exporting NODE_TLS_REJECT_UNAUTHORIZED = "0" in your environment.

@rabbah
Copy link
Member

rabbah commented Feb 25, 2017

Lastly, you can use http://172.17.0.1:10001 instead as your openwhisk API host.

@tardieu
Copy link
Contributor

tardieu commented Mar 1, 2017

@rabbah I encountered the same issue. The workaround does the trick. But is the certificate error the expected behavior? If it is, the doc should discuss it.

@rabbah
Copy link
Member

rabbah commented Mar 1, 2017

They do but not in the best place: https://github.com/openwhisk/openwhisk/tree/master/tools/vagrant#ssl-certificate-configuration-optional.

See this discussion for a longer debate about this: #1570 (and related pr #1838).

@rabbah
Copy link
Member

rabbah commented Mar 10, 2017

Closed by #2000.

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

No branches or pull requests

3 participants