New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Unable to run JViewer to connect to server via KVM
So I am trying to connect to dedicated server via KVM (I think it's also called IPMI over KVM but I am not sure) but getting error when I run this .jnlp file. The error is given in screenshot below.
After that I went into Java settings and enabled all TLS versions but still getting same error.
How to fix this issue?
This discussion has been closed.
Comments
Is Java up to date on your system? I've had issues with Supermicro IPMI java files before because of this.
Yes. I just checked for update again and it says that I have the latest Java version.
Seem tls/ssl issues, try option 'Do not check' TLS in your image, and use IE 9.
"Do not check" TLS also didn't work. Nothing to do with IE9 as it is a separate application.
Just for giggles open it up in FF or Chrome.
What is the "series" of the Supermicro?
Try to uncheck TLS higher than 1.0 . The server only support 1.0 and i think it have "version intolerance".
Getting this error when I only use TLS 1.0 and uncheck others.
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)Can't seem to find series of Supermicro. This is the control panel I have.
How old is this server?
That firmware is 7 years old...
no idea to be honest haha
Grab the motherboard model and pop it here, ill see if there is any update you can do.
That’s most likely a very old server with eg. an X7-series motherboard or older even.
You may want to try IPMIView as there is a big chance that it only supports SSLv3 and that isn’t supported in modern versions of Java.
https://www.supermicro.com/SwDownload/SwSelect_Free.aspx?cat=IPMI
Open up the server and either take a picture or let us know the motherboard model.
Didn't work. When I run IPMIView from command prompt after providing IP etc. then nothing happens. Control simply returns.
Here's motherboard info
CPU is
Dual Intel Xeon E5620 @ 2.4GHz (8 Cores +HT)You're already on the latest firmware.
There's some BIOS update (if you already don't have it) that fixes the spectre meltdown but that's about it.
I’ve had success connecting to x8 IPMI by downgrading to an older version of Java Runtime Environment. I think version 8 IIRC. I also don’t have problems connecting from a Linux desktop with IcedTea-web
Yeah thinking of making an Ubuntu VM to try it from.
I had some issues with an old server once, the solution was to simply use java jre 7u80 in my case.
Installed 7u80 and now I am getting different error.
Then I noticed that only TLS1.0 is checked in Java settings so I went ahead and also checked 1.1 and 1.2 and now I get this error:
java.net.ConnectException: Connection refused: connectyou can try these containers just build for this problem of java shit.
https://hub.docker.com/r/solarkennedy/ipmi-kvm-docker
or
https://hub.docker.com/r/fresta/ipmi-console
Installed Docker for the first time. Then downloaded that container and ran and now I can see the browser but problem is unable to login as I keep getting error
The form token is invalidActually I have a .jnlp file which I want to run but I don't know how to transfer that into container so I tried to login so I can download it but it doesn't work.
You may use a lower version of JAVA, something like JAVA 6 and it should work.
I was finally able to run this
https://hub.docker.com/r/fresta/ipmi-consolebut getting similar Java error when running that .jnlp file.Could this be an issue with hosting provider? May be there is some configuration issue?
Found the solution. I simply opened .jnlp file in Notepad++ and changed https to http
Now when I double click to open, I see this window.
After spending hours trying to solve this issue, I am chomping at the bit to share my solution. For me, there were several pieces to the puzzle:
1. Install OpenWebStart via their website or simply use choco install openwebstart.
2. The jnlp file was malformed and designed for use by my server hosting company, via some detective work, I found the two 10.50.yy.xx IP addresses needed to be replaced with public 69.10.yy.xx IP addresses.
3. Mounting a DVD and having it used from St Louis to NYC, a 50ms ping time was too much. I stood up a VM at my server hosting company, then did what needed to be done.
My servers are now on-line, the big issue for me was the ability to robustly remotely mount the Debian DVD so I could do a custom install, there must be a better way to do this, however my server hosting company doesn't seem to offer one, so this is the path I chose.