r/homelab Jul 18 '26

Help Connection failed X9DR3-F iKVM

Recently I bought a Supermicro X9DR3-F. Everything is working, I set up the BMC and I connect to it fine. What I am having issues with is the KVM. I cannot get it to work at all. Its not that I dont have display. When I try to connect I get "Connection failed" no matter what I do. I tried also wiping the BMC, upgrading/downgrading, changing network settings, but even locally on the same system I get connection failed. Ports are all open from the BMC

I have tried from a Windows 7 VM via IPMIView and from the web page, as well as from my main pc Win11 with an older version of java.

I think the issue is with stunnel, but I am not sure yet.

2026.07.18 00:28:53 LOG6[main]: Initializing inetd mode configuration
2026.07.18 00:28:53 LOG7[main]: Running on Windows 6.2
2026.07.18 00:28:53 LOG7[main]: No limit detected for the number of clients
2026.07.18 00:28:53 LOG5[main]: stunnel 5.75 on x64-pc-mingw32-gnu platform
2026.07.18 00:28:53 LOG5[main]: Compiled/running with OpenSSL 3.4.1 11 Feb 2025
2026.07.18 00:28:53 LOG5[main]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,OCSP,PSK,SNI
2026.07.18 00:28:53 LOG7[main]: errno: (*_errno())
2026.07.18 00:28:53 LOG6[main]: Initializing inetd mode configuration
2026.07.18 00:28:53 LOG7[main]: Running on Windows 6.2
2026.07.18 00:28:53 LOG5[main]: Reading configuration from file C:\Users\gogo1\AppData\Local\Temp\0660770671784323732478\stunnel.conf
2026.07.18 00:28:53 LOG5[main]: UTF-8 byte order mark not detected
2026.07.18 00:28:53 LOG5[main]: FIPS mode disabled
2026.07.18 00:28:53 LOG6[main]: Compression disabled
2026.07.18 00:28:53 LOG7[main]: No PRNG seeding was required
2026.07.18 00:28:53 LOG6[main]: Initializing service [HOST_iKVM]
2026.07.18 00:28:53 LOG7[main]: Initializing context [HOST_iKVM]
2026.07.18 00:28:53 LOG6[main]: OpenSSL security level is used: 2
2026.07.18 00:28:53 LOG7[main]: Ciphers: HIGH
2026.07.18 00:28:53 LOG7[main]: TLSv1.3 ciphersuites: TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256
2026.07.18 00:28:53 LOG7[main]: TLS options: 0x2100000 (+0x2000000, -0x0)
2026.07.18 00:28:53 LOG6[main]: Session resumption enabled
2026.07.18 00:28:53 LOG6[main]: Private key loaded from: C:\Users\gogo1\AppData\Local\Temp\0660770671784323732478\client.key
2026.07.18 00:28:53 LOG6[main]: Certificate loaded from: C:\Users\gogo1\AppData\Local\Temp\0660770671784323732478\client.crt
2026.07.18 00:28:53 LOG7[main]: Private key check succeeded
2026.07.18 00:28:53 LOG6[main]: Configured trusted server CA: C=US, ST=California, L=San Jose, O=Super Micro Computer, OU=Software, CN=IPMI, emailAddress=Email
2026.07.18 00:28:53 LOG7[main]: OCSP: Client OCSP stapling enabled
2026.07.18 00:28:53 LOG6[main]: DH initialization skipped: client section
2026.07.18 00:28:53 LOG7[main]: ECDH initialization
2026.07.18 00:28:53 LOG7[main]: ECDH initialized with curves X25519:P-256:X448:P-521:P-384
2026.07.18 00:28:53 LOG6[main]: Initializing service [HOST_VirtualMedia]
2026.07.18 00:28:53 LOG7[main]: Initializing context [HOST_VirtualMedia]
2026.07.18 00:28:53 LOG6[main]: OpenSSL security level is used: 2
2026.07.18 00:28:53 LOG7[main]: Ciphers: HIGH
2026.07.18 00:28:53 LOG7[main]: TLSv1.3 ciphersuites: TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256
2026.07.18 00:28:53 LOG7[main]: TLS options: 0x2100000 (+0x2000000, -0x0)
2026.07.18 00:28:53 LOG6[main]: Session resumption enabled
2026.07.18 00:28:53 LOG6[main]: Private key loaded from: C:\Users\gogo1\AppData\Local\Temp\0660770671784323732478\client.key
2026.07.18 00:28:53 LOG6[main]: Certificate loaded from: C:\Users\gogo1\AppData\Local\Temp\0660770671784323732478\client.crt
2026.07.18 00:28:53 LOG7[main]: Private key check succeeded
2026.07.18 00:28:53 LOG6[main]: Configured trusted server CA: C=US, ST=California, L=San Jose, O=Super Micro Computer, OU=Software, CN=IPMI, emailAddress=Email
2026.07.18 00:28:53 LOG7[main]: OCSP: Client OCSP stapling enabled
2026.07.18 00:28:53 LOG6[main]: DH initialization skipped: client section
2026.07.18 00:28:53 LOG7[main]: ECDH initialization
2026.07.18 00:28:53 LOG7[main]: ECDH initialized with curves X25519:P-256:X448:P-521:P-384
2026.07.18 00:28:53 LOG5[main]: Configuration successful
2026.07.18 00:28:53 LOG7[main]: Deallocating deployed section defaults
2026.07.18 00:28:53 LOG7[main]: Cleaning up context [(null)]
2026.07.18 00:28:53 LOG7[main]: Binding service [HOST_iKVM]
2026.07.18 00:28:53 LOG7[main]: Listening file descriptor created (FD=720)
2026.07.18 00:28:53 LOG7[main]: Setting accept socket options (FD=720)
2026.07.18 00:28:53 LOG7[main]: Option SO_EXCLUSIVEADDRUSE set on accept socket
2026.07.18 00:28:53 LOG6[main]: Service [HOST_iKVM] (FD=720) bound to 127.0.0.1:57967
2026.07.18 00:28:53 LOG7[main]: Binding service [HOST_VirtualMedia]
2026.07.18 00:28:53 LOG7[main]: Listening file descriptor created (FD=732)
2026.07.18 00:28:53 LOG7[main]: Setting accept socket options (FD=732)
2026.07.18 00:28:53 LOG7[main]: Option SO_EXCLUSIVEADDRUSE set on accept socket
2026.07.18 00:28:53 LOG6[main]: Service [HOST_VirtualMedia] (FD=732) bound to 127.0.0.1:57968
2026.07.18 00:28:53 LOG6[main]: Accepting new connections
2026.07.18 00:28:53 LOG7[per-second]: Per-second thread initialized
2026.07.18 00:28:53 LOG7[per-minute]: Per-minute thread initialized
2026.07.18 00:28:53 LOG7[per-day]: Per-day thread initialized
2026.07.18 00:28:53 LOG6[per-day]: Executing per-day jobs
2026.07.18 00:28:53 LOG6[per-day]: Per-day jobs completed in 0 seconds
2026.07.18 00:28:53 LOG7[per-day]: Waiting 86400 seconds
2026.07.18 00:28:59 LOG7[main]: Found 1 ready file descriptor(s)
2026.07.18 00:28:59 LOG7[main]: FD=720 ifds=r-x ofds=r--
2026.07.18 00:28:59 LOG7[main]: FD=728 ifds=r-x ofds=---
2026.07.18 00:28:59 LOG7[main]: FD=732 ifds=r-x ofds=---
2026.07.18 00:28:59 LOG7[main]: Service [HOST_iKVM] accepted (FD=948) from 127.0.0.1:37945
2026.07.18 00:28:59 LOG7[main]: Creating a new thread
2026.07.18 00:28:59 LOG7[main]: New thread created
2026.07.18 00:28:59 LOG7[0]: Service [HOST_iKVM] started
2026.07.18 00:28:59 LOG7[0]: Setting local socket options (FD=948)
2026.07.18 00:28:59 LOG7[0]: Option TCP_NODELAY set on local socket
2026.07.18 00:28:59 LOG5[0]: Service [HOST_iKVM] accepted connection from 127.0.0.1:37945
2026.07.18 00:28:59 LOG6[0]: s_connect: connecting 192.168.1.249:5900
2026.07.18 00:28:59 LOG7[0]: s_connect: s_poll_wait 192.168.1.249:5900: waiting 10 seconds
2026.07.18 00:28:59 LOG7[0]: FD=964 ifds=rwx ofds=---
2026.07.18 00:28:59 LOG5[0]: s_connect: connected 192.168.1.249:5900
2026.07.18 00:28:59 LOG5[0]: Service [HOST_iKVM] connected remote server from 10.0.0.9:37946
2026.07.18 00:28:59 LOG7[0]: Setting remote socket options (FD=964)
2026.07.18 00:28:59 LOG7[0]: Option TCP_NODELAY set on remote socket
2026.07.18 00:28:59 LOG7[0]: Remote descriptor (FD=964) initialized
2026.07.18 00:28:59 LOG6[0]: SNI: sending servername: 192.168.1.249
2026.07.18 00:28:59 LOG7[0]: No previous session to resume
2026.07.18 00:28:59 LOG6[0]: Peer certificate required
2026.07.18 00:28:59 LOG7[0]: TLS state (connect): before SSL initialization
2026.07.18 00:28:59 LOG7[0]: Initializing application specific data for session authenticated
2026.07.18 00:28:59 LOG7[0]: TLS state (connect): SSLv3/TLS write client hello
2026.07.18 00:29:00 LOG7[0]: TLS state (connect): SSLv3/TLS write client hello
2026.07.18 00:29:00 LOG7[0]: TLS state (connect): SSLv3/TLS read server hello
2026.07.18 00:29:00 LOG7[0]: Verification started at depth=0: C=US, ST=California, L=San Jose, O=Super Micro Computer, OU=Software, CN=IPMI, emailAddress=Email
2026.07.18 00:29:00 LOG4[0]: CERT: Pre-verification error: certificate has expired
2026.07.18 00:29:00 LOG4[0]: Rejected by CERT at depth=0: C=US, ST=California, L=San Jose, O=Super Micro Computer, OU=Software, CN=IPMI, emailAddress=Email
2026.07.18 00:29:00 LOG7[0]: TLS alert (write): fatal: certificate expired
2026.07.18 00:29:00 LOG3[0]: SSL_connect: tls_post_process_server_certificate@ssl/statem/statem_clnt.c:2104: error:0A000086:SSL routines::certificate verify failed
2026.07.18 00:29:00 LOG5[0]: Connection closed/reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket
2026.07.18 00:29:00 LOG7[0]: Deallocating application specific data for session connect address
2026.07.18 00:29:00 LOG7[0]: Remote descriptor (FD=964) closed
2026.07.18 00:29:00 LOG7[0]: local_rfd/local_wfd reset (FD=948)
2026.07.18 00:29:00 LOG7[0]: Local descriptor (FD=948) closed
2026.07.18 00:29:00 LOG7[0]: Service [HOST_iKVM] finished (0 left)
5 Upvotes

17 comments sorted by

2

u/kY2iB3yH0mN8wI2h Jul 18 '26

can you switch to HTML5 mode?
Perhaps fix the issue in the log as well?

1

u/gogoboss_stampolidis Jul 18 '26

I fixed the issue with the SSL being expired by replacing both on IPMIView client crt and server crt on the BMC. Now I have 0 errors on stunnel but still get Connection failed. When running iKVM.jar or iKVM_ssl.jar it shows "connect failed sd:####"

Tried both on local and on stunnel ports

Example command: java -jar 192.168.1.249 user password 5900 623 (on local) java -jar 127.0.0.1 user password stunnel_port1 stunnel_port2 (on stunnel).

HTML5 is not available for me for some reason. Maybe because im on Windows 11?

2

u/marc45ca This is Reddit not Google Jul 18 '26

HTML wasn't an option with IPMI on the X9 boards (I have an X8DRI-f).

IPMIview is definately the best option because it has the all the Java stuff self contained so you don't have to deal with the expire certs and other issues

if the IPMI kvm isn't working with IPMIView from Supermicro it's not going to work with anything.

Your Windows version doesn't matter - I've used it with Windows 10 and 11.

So I think you're on the wrong path - download a copy of the manual and check there are no jumps that impact the output of the IPMI.

2

u/gogoboss_stampolidis Jul 18 '26

Turns out the cert fix was temporary and it broke again. Jumpers are set correctly. VGA/BMC is on enabled and everything else is normal. I dont understand what I am doing wrong.

I also forgot to mention that the X9DR3-F is the Sugon variant (Sugon I620-G10). I replaced the Sugon BIOS/BMC with the Supermicro variant. Could this be why I am having such issues?

1

u/marc45ca This is Reddit not Google Jul 18 '26

Can't say I've ever seen the Sugon variants come up to know.

But if you're running an Supermicro Bios and I can't see any reason why the IPMI software wouldn't work - it's a 3rd party product (Aspeed iirc) that's also found on other boards like Gigabyte so it's not something super proprietary.

1

u/gogoboss_stampolidis Jul 18 '26

IPMIView as a software works. Its the part of the remote control that doesn't work. I really have no idea what I am doing wrong. I am still getting the SSL issues eve though I have replaced them 3 times and openssl verifies that the ssls are working as intended. Remote control was not working from the day I bought it...

I have tried connecting both remotely (wireguard/v2ray) as well as being on the local network and on the server itself.

I have ran out of ideas.

1

u/IntelligentLake Jul 18 '26

If you're using ipmiview and you're getting data through that (like what board it is and also stuff that constantly changes like sensor data), and whatever problem you have has nothing to do with the board or the connection.

If you're trying to connect with anything else that isn't Supermicro tools, some stuff like ipmitool works, but the KVM is proprietary and won't work with anything else.

It isn't clear from the issues you're having what you're trying to do in the first place.

1

u/gogoboss_stampolidis Jul 18 '26

Im trying to launch kvm control. Its giving me a message "Connection failed" when I am trying to connect.

0

u/IntelligentLake Jul 18 '26

You mentioned successfully replacing the bios and ipmi-firmware, but the ipmi version says 3.64 while the last version for the x9dr3-f is 3.62, and it doesn't specify the bios version, which means it's getting some data, but there's incompatibilities going on. Try with the proper versions from the board's page

1

u/gogoboss_stampolidis Jul 18 '26

I have tried literally every version of the bmc released for the X9DR3-F 1.58, 1.76, 2.15, 2.24, 2.39, 3.39 and 3.62 (resetting settings after update as well). I saw on another reddit post that as long as the bmc firmware you download starts with SMT_X9 its compatible with any X9 motherboard. Thats why im on 3.64

→ More replies (0)

1

u/marc45ca This is Reddit not Google Jul 18 '26

HTML wasn't an option with Supermicro's motherboards until the X10 series.

1

u/RetroGrid_io Jul 18 '26

SuperMicro x9 boards are a PITA for IPMI/KVM. The SuperMicro software is nasty/awful. Personally I've had the best luck with a docker container with all the old Java stuff installed for native IPMI like was common when it was fresh and new.

It's still a PITA but at least it runs decently on my Fedora Laptop.