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

Unable to launch dashboard-proxy due to tls certificate error #4375

Open
vcetinick opened this issue Jan 20, 2024 · 2 comments
Open

Unable to launch dashboard-proxy due to tls certificate error #4375

vcetinick opened this issue Jan 20, 2024 · 2 comments
Labels

Comments

@vcetinick
Copy link

Summary

After freshly installing microk8ts on my machine, I'm still having issues trying to get the dashboard working when running the dashbooard-proxy command.

It looks like my local IP address has changed (DHCP lease expired) and I now have a different IP address compared to what the SSL certificate is valid for.

How can I fix this error and get the dashboard working again?

What Should Happen Instead?

Reproduction Steps

` microk8s dashboard-proxy

Checking if Dashboard is running.
Infer repository core for addon dashboard
Waiting for Dashboard to come up.
Trying to get token from microk8s-dashboard-token
Waiting for secret token (attempt 0)
Dashboard will be available at https://127.0.0.1:10443
Use the following token to login:
xxxx
error: error upgrading connection: error dialing backend: tls: failed to verify certificate: x509: certificate is valid for 192.168.1.129, 172.24.0.1, 172.21.0.1, 172.28.0.1, 172.19.0.1, 172.17.0.1, 172.29.0.1, 192.168.200.1, 172.26.0.1, 172.30.0.1, 172.23.0.1, 172.25.0.1, 172.27.0.1, 172.22.0.1, 172.20.0.1, 172.18.0.1, 172.31.0.1, 192.168.80.1, 192.168.49.1, 2a02:168:67bf:1:90c8:b642:bb9f:997d, 2a02:168:67bf:1:eab:9bf6:4b52:58fd, not 192.168.1.134
`

Introspection Report

Can you suggest a fix?

Reissue the SSL certificate on the new IP address and document how this can be achieved?

Are you interested in contributing with a fix?

@victor-cetinic
Copy link

I managed to resolve the issue by refreshing the ca.crt using the following command and after double checking that ca cert templates in the microk8ts installation folders were up to date with my latest ip address

sudo microk8s refresh-certs --cert ca.crt

Copy link

stale bot commented Dec 18, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants