Created
August 3, 2015 20:52
-
-
Save gt50/2699ee03ce253a32d979 to your computer and use it in GitHub Desktop.
Xencenter connection fail with Windows 10
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Xencenter could not connect to some of my xenservers today. This is an issue with Windows 10 and 512 bit certificates for old version of xenserver. | |
| # My recently built servers have 1024 bit certs. My old servers that have been upgraded several times had 512 bit certs from original installations. | |
| # All of my servers are running 6.5 so the generate_ssl_cert is already set to 1024 default. If you are using older version, modify the script. | |
| # view strength of certificate. If it is 512 it needs to be rebuilt to allow connection from Windows 10. | |
| openssl x509 -in /etc/xensource/xapi-ssl.pem -text | |
| mv /etc/xensource/xapi-ssl.pem xapi-ssl.pem.orig | |
| # By default xenserver uses the ip address for container name on certificate | |
| /opt/xensource/libexec/generate_ssl_cert /etc/xensource/xapi-ssl.pem 10.1.2.42 | |
| xe-toolstack-restart |
Fantastic. This was driving me nuts. Thank you!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Solved my problem perfectly! Thanks!