Bobcares

Supermicro java console connection failed – How we fix it?

by | Dec 4, 2019

Are you receiving an error “Supermicro java console connection failed”? We can help you.

The error occurs when we try to access the remote console from IKVM.

At Bobcares, we often get requests from our customers regarding console access failure as a part of our Server Management Services.

Today, let’s see how our Support Engineers resolve Supermicro java console connection failed.

 

Causes for Supermicro java console connection failed

When we log in to the management interface then try to access the remote console, the browser will download a .jnlp file. When trying to open the file the error occurs.

The common reasons for the error to occur are:

  • Java application missing
  • IP not present in Java Exception list
  • Java not up-to-date
  • IPMI firmware not up-to-date
  • IKVM port not open in the firewall

The sample error looks like

Supermicro java console connection failed

Let’s discuss how our Support Engineers resolve this error for our customers.

 

How we fix Supermicro java console connection failed

Recently one of our customers contacted us to resolve java console connection failed error.

Add IP to the exception list

This error occurs because the current version of Java no longer allows self-signed applications to run by default. In order to allow the application to run, the URL of the IKVM device must be added to Java’s site exception list. We provide the below steps to our customers to fix this error.

1. On the local machine open java and select configuration Java.

2. Within the Java Control Panel go to Security.

3. Select Edit Site List

4. Now add the IPMI IP address to the list.

http://ipmiip
https://ipmiip

5. The remote application will try to connect using SSL. Thus https must be added.

5. Then relaunch the remote console. Now an SSL warning message appears. Click the checkbox and click on continue.

Now will be able to access the console.

Update JAVA

One of the common reasons the error is that the JAVA application is not up-to-date. We recommend our customers to update the Java in the local machine and try to connect to the remote console.

IPMI firmware

If the IPMI firmware is not up-to-date. We can get the console connection failed error. So we update the firmware. Let’s discuss how our Support Engineers update the firmware.

1. We log in to the management interface. Then go to Maintenance and select Firmware update.

2. Now we enable update mode by clicking the Enter Update Mode.

3. Then we upload the ZIP file. Once the file is uploaded the screen will show the current and the newly added firmware.

4. After confirming the version we select start Upgrade.

5. Once the update is complete the management interface will reboot. It will return back to the login screen.

Now we login to the console and we can access the remote console.

If we still face an error even after the update we use the Factory Default option in the web interface to connect.

 

IKVM port

If the IKVM server port is not opened in the server. The console will fail to open.

We will be able to access the management interface since it uses port 80 and 443. We check the port from the web interface and open the port in the firewall.

After opening the port. Then we will be able to access the remote console.

 

[Need any assistance in fixing this error? – We’ll help you]

 

Conclusion

In short, we have discussed the causes of the “java console connection failed” error.  Also, we saw how our Support Engineers resolve the error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF