All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
OVH/Kimsufi IPMI via Java applet madness
I am trying to connect to any of my 3 servers using the IPMI Java Applet, to no avail. I think I tried everything I could, various old Java versions together with OpenWebStart, different security settings, it all still fails with:
JNLPClassLoader: Finding library iKVM64.dll
JNLPClassLoader: Finding library SharedLibrary64.dll
Retry =1
Retry =2
Retry =3
Retry =4
Retry =5
Retry =6
Retry =7
Retry =8
Retry =9
Retry =10
And then I am getting "connection failed". I can telnet to the IP address from the JNLP file on port 5900 just fine. The IPMI is functional in the OVH dashboard: confirmed using IPMI Test and the HTML KVM.
I need Java to publish custom ISO, the HTML KVM is an older one and doesn't support ISO uploading.
Since this is Kimsufi, I understand IPMI is not normally supported by OVH on these servers, so I can't have their support look into it?
I'll appreciate any help.

Comments
You can use their rescue system and kexec netboot.xyz, or any other system actually.
apt-get update && apt-get install -y kexec-tools wget
mkdir /tmp/netboot && cd /tmp/netboot
wget https://boot.netboot.xyz/ipxe/netboot.xyz.lkrn
kexec -l netboot.xyz.lkrn
kexec -e
If your .iso is not in the list, like Windows, you can raw dd if to the local disk and adjust boot params. This makes it totally possible to install any OS without IPMI at all, it's just a nice bonus to have it.
Change the boot mode to OVH's rescue distro, and either use netboot.xyz like @luckypenguin suggested or launch an installer / live system ISO with QEMU.
For example with my KS-5 or KS-LE-B which both have two NVMe drives, I launch the Debian 13 live system ISO with:
Then you can VNC into your server at [server_ip]:5900.
But I strongly recommend using VNC encryption with X509 certificates, you need to generate a CA root and a server certificate then change the
-vncoption as described in the QEMU docs. Also use a password.Ive had issues with jnlp when yhe server had both html5 and Java options
Support acknowledged that supermicro has acknowledged the same but no eta on the fix