> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/bare-metal/dedicated-servers/how-tos/connect-to-the-server-using-ipmi.md).

# Connect to the server using IPMI

***

All dedicated servers from Glesys can be remotely managed via IPMI (Intelligent Platform Management Interface). This is a system that allows access to the server’s screen and keyboard as if you had physical access to the server. It enables you to reinstall the server’s operating system, access the BIOS, and more.

With IPMI, it is also possible to monitor hardware RAID, server temperatures, PSU status, and much more. Additionally, you can turn the server on and off via IPMI.

The IPMI login credentials for the server are included in the email you received from Glesys with the server details. This email contains both an HTTPS address for the server’s IPMI and a link to retrieve the login credentials.

Start by clicking the link to retrieve the login credentials. The link begins with [*secrets.glesys.com*](http://secrets.glesys.com). When the page opens, the credentials are hidden, and you must click **View secret** to reveal them.

<figure><img src="/files/aa3PPXgaTDzyEG7edHi8" alt=""><figcaption></figcaption></figure>

The credentials are now displayed. Make sure to save them in a secure location. They will only be available for 14 days, after which they will be permanently deleted.

<figure><img src="/files/uxl5qXBpfrW9GenjGIZm" alt=""><figcaption></figcaption></figure>

To access the server’s IPMI address, you first need to create a VPN with Glesys and connect to it. This is because the IPMI address is an internal IP address that is not accessible via the internet. Instructions on how to create and connect to a VPN can be found in the [Virtual Private Network (VPN)](/products/connectivity/network-services/virtual-private-network-vpn.md) chapter.

Once you are connected to the VPN tunnel, click on the link in the email to open the IPMI login page. A warning will appear stating that the connection is not secure, but this is only because the certificate is self-signed. The connection is still encrypted. Click **Advanced** in the web browser.

<div align="left"><figure><img src="/files/KTmTHp9MIQzg6NbcGAcw" alt="" width="563"><figcaption></figcaption></figure></div>

In the next dialog box, click **Proceed to 10.1.xx.xx (unsafe)**. In the Firefox browser, this option is instead called **Accept the Risk and Continue**.

<div align="left"><figure><img src="/files/Ex8aK5im22d95sWgsX4q" alt="" width="563"><figcaption></figcaption></figure></div>

In the next step, you log in to the IPMI interface. The credentials were provided when you clicked the link in the email from Glesys.

<div align="left"><figure><img src="/files/rXDovJPHPCrg9LycR6Tt" alt="" width="563"><figcaption></figcaption></figure></div>

You will now arrive at the overview, which looks like the image below.

<figure><img src="/files/PBQIKCtDpF478Ux6omAb" alt=""><figcaption></figcaption></figure>

## Console access&#x20;

There are some minor differences between the IPMI interfaces of X10- and X11-based servers, mainly where to find the different consoles. Apart from the interface differences, currently, the Java-based console doesn't work in X10-based servers.

### HTML5-based console

{% tabs %}
{% tab title="X10" %}
To open the console and remotely control the server—for example, if you have accidentally locked yourself out from SSH or RDP—you click on **Remote Control** in the menu. Then, click on **iKVM/HTML5** and then on the **iKVM/HTML5** button. A console window will then open.

<figure><img src="/files/vzNRumkcIk6VxWDwzdLc" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="X11" %}
To open the console and remotely control the server—for example, if you have accidentally locked yourself out from SSH or RDP—you click on **Remote Control** in the top menu. Then, click **Remote Console** in the left-hand menu.

By default, the preferred console is the Java-based one. To switch to the HTML5-based console, click the **here** link, as shown in the screenshot.

<figure><img src="/files/lEduLiYqVwlunQ6dHwwR" alt=""><figcaption></figcaption></figure>

On the next page, select **HTML5** and click **Save**.

<figure><img src="/files/dcLuhlofZBl0oK7TE8MO" alt=""><figcaption></figcaption></figure>

You will now return to the previous page. Here, click **Launch Console**.

<figure><img src="/files/ubl3ylU5qo3Yc1Vg9Pz9" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

If you experience issues with the keyboard, such as not finding the correct special characters, there is a virtual keyboard available via the button just below the console.

<figure><img src="/files/AujEod7n7E6QU3vmkYY7" alt=""><figcaption></figcaption></figure>

### Java-based console

There is also a more advanced Java-based console. Among other features, it supports more keyboard layouts and allows mounting ISO files directly from the local computer to the server. The latter is useful to reinstall the server’s operating system.

{% hint style="warning" %}
The X10 dedicated servers do not have a working Java console at the moment. Use the HTML5-based console instead. If you need to reinstall your X10 dedicated server's operating system, contact Glesys support at <support@glesys.se>.
{% endhint %}

The Java-based console requires Java Web Start to run. This is included when installing the JRE (Java Runtime Environment) on the computer. The easiest way to download Java is from [www.java.com/en/download/manual.jsp](https://www.java.com/en/download/manual.jsp). Select the version that matches your computer and operating system.

Once Java is installed on the computer, you can start the Java-based console.&#x20;

{% tabs %}
{% tab title="X10 (currently not working)" %}
You find the Java-based console under **Remote Control → Console Redirection**. Here, click **Launch Console**.

<figure><img src="/files/ZmTO23BsHQ33iMOIqoU9" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="X11" %}
The Java-based console is the preferred one in X11-based servers. Click **Remote Control** in the top menu. Then, click **Remote Console** in the left-hand menu. It should read *"Current interface: JAVA plug-in"*. If that is the case, click **Launch Console**. If the currently selected console is the HTML5-based one, click the link (the one that says **here**) on the page and select ***JAVA plug-in*** instead.

<figure><img src="/files/WqPn40bepK3imcTXYRcQ" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

A file named *launch.jnlp* will be downloaded to the computer. This is the file you need to run with Java Web Start to launch the console.

In Microsoft Windows, the file can be started by simply double-clicking it. In Linux and macOS, run it using the following command:

{% code title="Command" %}

```
javaws launch.jnlp
```

{% endcode %}

You will now see a warning that the certificate is not valid, which is expected. Click **Continue**.

<div align="left"><figure><img src="/files/xzBj35BCO0CohETxrAEs" alt=""><figcaption></figcaption></figure></div>

Next, you will see another warning dialog stating that the Java application may pose a security risk. Check that the *Publisher* is *Super Micro Computer, Inc* and that the *Location* is the IP address of the server’s IPMI. If this information is correct, tick the box to accept the risk and then click **Run**.

<div align="left"><figure><img src="/files/biVb4yPKZYhlTreonW1W" alt=""><figcaption></figcaption></figure></div>

The console now starts and looks like the image below.

<div align="left"><figure><img src="/files/ZL8mHEbzBGdvmQmAudJV" alt=""><figcaption></figcaption></figure></div>

{% hint style="success" %}
Note that you must download a new *launch.jnlp* file each time you log in to the IPMI interface. A *launch.jnlp* file is only valid for a single login session.
{% endhint %}

### Reinstall the server's operating system from an ISO file

See [Install/reinstall the server's operating system](/products/bare-metal/dedicated-servers/how-tos/install-reinstall-the-servers-operating-system.md).

## Monitor the server's health

Through the IPMI interface, you can monitor the server's health. Among other things, you can check the server's temperatures, RAID health, and even the individual disks' status. Click on **Server Health** in the IPMI menu to browse through all the available readings.

The disk information is located under **Server Health** in the IPMI menu. At the bottom of the sidebar menu, you find **Storage Monitoring**. Here, you can select either **Physical View** to see individual disks or **Logical View** to check the status of the RAID. For example, if you select **Physical View** and then click **more** for a specific disk, you can see details such as *Error Count*, *SMART Event*, and *Media Error*.

<div align="left"><figure><img src="/files/Dwce2RMnCIfvO9HdvLNC" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glesys.com/products/bare-metal/dedicated-servers/how-tos/connect-to-the-server-using-ipmi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.