When accessing a server’s iLO 3 web portal or virtual console, you may run into browser compatibility problems, firmware quirks, or access-related issues. This article walks you through the step‑by‑step process of connecting to an iLO 3 controller via its web interface and launching the embedded remote console.

It covers the prerequisites you need before you can start:

• How to connect to the remote management VPN
• How to locate your user credentials
• Meet the required browser and Java specifications
• Troubleshoot common connection errors and apply quick‑fix work‑arounds.

By the end of this article, you will be able to:

• Access the iLO 3 GUI securely from any workstation connected to the remote management virtual private network
• Open the virtual console to perform BIOS configuration, OS installation, or hardware diagnostics without physical presence
• Diagnose and resolve typical connectivity problems that prevent iLO 3 access.

What Is iLO3 and Why Is It Important

iLO 3 (Integrated Lights-Out 3) is a remote management technology used in HPE ProLiant servers that allows administrators to monitor and control hardware independently of the operating system. It provides out-of-band access for tasks like remote console access, power cycling, and system health monitoring, even when the server is turned off or unresponsive.

The remote access console allows you to work on your server as if you were sitting in front of it with a physical screen, monitor and keyboard. This makes it possible to make changes to your server before it boots, or inside its BIOS, which are generally not possible via SSH, RDP or other similar remote management methods.

Leaseweb Remote Management VPN

Before proceeding any further with this guide, make sure that you are connected to our isolated, secure, remote management VPN. Please follow these instructions in order to get connected. Once you are connected, you can proceed with this article.

How to Get Your IPMI IP Address and Credentials

To find the IP address and credentials that correspond to your servers IPMI / iLO 3 interface, follow the steps below:

1. Open the Leaseweb Customer Portal
2. Go to your server’s page under the Dedicated Servers option
3. Select Actions -> Remote Management

A window will appear in the center of your screen, similar to the one shown below. This window contains all the information you need to access your server’s IPMI/iLO 3 interface.

Here you will see the IPMI IP address, as well as a link that will load the web interface when clicked. You will also find the username and password (IPMI Credentials) that you will use to log in to the IPMI / iLO 3 interface. We will explain how to use these later in this article.

Back to the top ↑

How to Launch an IPMI Reset

If you are connected to the remote management VPN but cannot log in with your credentials, or the IPMI interface does not load in your browser, we recommend resetting the IPMI controller. Do this by performing an IPMI reset. Click on the launch an IPMI Reset link at the bottom of the window to proceed.

The IPMI reset job will reboot the server and PXE boot it into an automated live environment. During this process, the server’s IPMI/iLO 3 network settings will be reconfigured, and a new username and password will be generated. Once the reset is complete, the updated credentials will be available in your Customer Portal.

HPE Lights-Out Standalone Remote Console for Windows

For the best experience when accessing your server’s console, we recommend you use HPE Lights-Out Standalone Remote Console for Windows.

HPE Lights-Out Standalone Remote Console for Windows is a lightweight application developed by HP that can be installed on your Windows computer. It allows you to access and control your server’s console directly, without the need to use a web browser.

You can download it directly from the HP website. After downloading it, you can proceed to install it. Once the application is installed, you should find an icon like the one shown below on your desktop or in the Start menu under All Programs.

How to Connect to HPE Lights-Out Standalone Remote Console for Windows

1. Opening the program. You will see an interface like the one shown below:

2. To connect to your server’s console you will need your:
   • Network Address
   • Username
   • Password
3. Get these details by following the steps from How to Get Your IPMI IP Address and Credentials
4. Enter the details and click Connect

Once you are connected, you will see a screen similar to the one shown above. From here you can manage your sever just as if you were sitting physically in front of it with a screen, mouse and keyboard.

Back to the top ↑

iLO 3 Web Interface and Console via Browser

The Integrated Lights-Out 3 web interface allows you to manage your server. You can perform actions like shutdown and reboot your server, monitor the health of the hardware and temperature and so much more.

1. To access it, go to Actions -> Remote Management
2. Click on the Login to IPMI Interface button
   • Alternatively, you can enter the IPMI IP Address as a URL in your browser. In this example, the IP address is 10.59.65.25 so the URL would be https://10.59.65.25/

When the web interface successfully loads, you should see the login screen shown below.

iLO 3 TLS Errors

If you see an SSL/TLS error instead of the iLO 3 login screen, know that these errors are very common when accessing the iLO 3 web interface, especially on older hardware. Below are some of the most common SSL/TLS warnings and errors you may encounter.

Error 1: Potential Security Risk Ahead

The warning appears because the SSL certificate on the iLO3 does not match the address used to access it. Since the iLO3 interface is not publicly exposed, and should remain internal, a publicly trusted SSL certificate is not required.

The warning can be concerning, but it is merely informational and does not pose any danger to your IPMI / iLO 3 access.

To proceed past this error:

1. Click the Advanced button
2. Then select Accept the Risk and Continue

Different browsers may display slightly different buttons, but the process to resolve remains the same.

Error 2: This site can’t provide a secure connection

Some browsers may display a TLS error, as shown below, when accessing the iLO 3 web interface. iLO 3 no longer receives firmware updates and only supports TLS 1.1 or earlier, which can cause this error on modern browsers.

To bypass this error and access the web interface, you will need to temporarily enable TLS 1.1 in your browser. If you did not encounter this error when loading the iLO 3 web interface, you can proceed to the next step.

Back to the top ↑

Logging into iLo3

The username and password to log into iLO 3 can be found inside your Leaseweb Customer Portal – see here.

1. Enter your username and password
2. Click Log In to proceed

You will see the below overview. You can check the status of your server, On / Off, as well as the status of the hardware health.

Loading the Console Via the Web Interface

Before proceeding with this section, please make sure you have Java 8 or better installed on your system. You can download it from Java.com.

1. To open the console, click on the Java Web Start link
2. This will initiate a download. Once the download finishes, double-click on it to run it.

3. Click Continue to finalize the installation

Back to the top ↑

Java Security Errors

You may receive a Java security error message when attempting to launch the Java Web Start, which is very common and a result of Java’s strict security settings. Please follow this KB Article here to add the URL of your server’s IPMI interface into Java’s Exception Site List.

After clicking Continue above, you should see this message. Check off the checkbox to the left and click Run.

The below image confirms that you have successfully opened your server’s console via the web interface:

From this console you can make BIOS level changes and boot your server with custom images. Proceed to the next step to learn how to mount an ISO image.

How to mount an ISO

When managing a server, it is sometimes necessary to use an ISO image to boot the server into specialized software and tools, or to perform a custom operating system installation.

1. Open the console interface
2. Click on the Virtual Devices menu at the top
3. Click on Image File CD/DVD-ROM

4. Find and select the ISO image you need and click Open

5. Click on the Virtual Devices menu at the top once again to confirm your ISO image was successfully mounted, if you see a check mark next to Image File CD/DVD-ROM
   • If no check mark is shown, try again from step 2

6. Reboot the server -> click Keyboard -> CTRL-ALT-DEL. This will initiate a graceful reboot of your server

Back to the top ↑

Troubleshooting ISO Booting

If you successfully mounted an ISO but the server did not boot from it, the boot order may be configured to prioritize the server’s internal disk over the virtual CD-ROM drive. The cause could be that the server started the operating system that was already installed instead of booting from the mounted ISO.

1. To rearrange your boot order, reboot and press the F9 key as the server boots. This will take you into the BIOS menu

2. Go to the Standard Boot Order (IPL) section in the BIOS menu
   • You may notice that the CD-ROM device is set to 3 in the boot order, while the Hard Disk is set to 2. This means the Hard Disk has higher priority. If an operating system is already installed on the Hard Disk, the server will boot into it instead of the ISO you just mounted

3. Using the arrow keys move the CD-ROM option up to number 2
4. Press the ESC key followed by the ESC again to go to the main menu
5. Press F10 to Exit the BIOS menu and reboot.

Back to the top ↑

Alternatives for Custom OS Installation

If you experience issues installing the operating system using the ISO boot method, you can use the netboot.xyz option available through our automation.

Netboot.xyz uses PXE/network booting instead of booting directly from an ISO image. When the server boots from the network, netboot.xyz downloads the installation files and boot components required for the selected operating system directly from the configured repositories. This allows the operating system installation to proceed without mounting or booting from an ISO image.

1. Go to Actions -> Customer Installation
2. Select the boot file netboot.xyz menu
3. Check the Power cycle after the creation of the reservation box
4. Click Submit.

The server will reboot on the netboot.xyz boot file to load the neboot.xyz menu. If you chose to gracefully reboot your server, you could leave the power cycle after the creation of the reservation checkbox unchecked. Once netboot.xyz has booted it should look as shown below.

To learn more about netboot.xyz and other PXE boot option, check out this Knowledge Base article.

Certain domain extensions require you to supply extra information before your registration can be completed. This information is collected in addition to your standard contact details. It depends on the domain extension, your location, and whether you are registering as a private individual or an organisation.

This article explains what is required for each supported domain extension.

.IT – Italian Domains

To register a .it domain, the registrant must be an Italian national or a national of any EU member state. Two scenarios apply depending on whether you are registering as a person or an organisation:

Private Individual (Person)

If you are registering as a private individual, then you must provide the following details:

Organisation

If you are registering as an organisation, then you must provide the following details:

What is Extended Lifecycle Support?

When an operating system (OS) reaches its End-of-Life (EOL) date, the vendor stops issuing security updates, leaving servers and virtual machines on that OS more exposed to vulnerabilities. 

WebPros, the company behind Plesk and cPanel, runs an Extended Lifecycle Support (ELS) program for affected OS versions. This gives customers additional time to plan an upgrade while continuing to receive critical security updates. 

How ELS fees work

Where an ELS program is active, an additional monthly fee applies per control panel license on the affected OS. Leaseweb passes this fee through to customers and it appears as a separate line item on your invoice. 

New ELS fees can be introduced, or prices can be adjusted on a half-yearly or annual basis. Leaseweb will communicate any changes in advance via email. 

Affected operating systems

cPanel

Plesk

How to avoid ELS fees

Upgrading to a supported OS is the only way to remove the ELS fee from your invoice. Leaseweb strongly recommends doing this as soon as possible, as running an EOL OS carries security risks regardless of the ELS program, and fees may increase over time. 

For a list of currently supported operating systems, refer to the official documentation for Plesk and cPanel. 

Leaseweb Managed Kubernetes Availability Target

The monthly Availability of Leaseweb Managed Kubernetes Availability shall be as set forth in the table below (the “Leaseweb Managed Kubernetes Availability Target”).

Leaseweb Managed Kubernetes Services Availability Target is not met in case the following conditions are met:

• all connection requests to the applicable cluster’s Kubernetes endpoint fail after the cluster was successfully created;
• when the number of ready worker nodes is lower than the requested number by more than one (1) node, after the cluster was successfully created; and
• this situation lasts for five (5) or more consecutive minutes.

Read more about the terms and conditions on our website.

• Leaseweb makes commercially reasonable efforts to provide the Leaseweb Managed Kubernetes Availability Target of 99.95% on the Kubernetes control plane of the Leaseweb Managed Kubernetes Services. Leaseweb shall not be held liable for damages if this Service Level is not met. Leaseweb owns the management of the Kubernetes control plane, which is included in the Service Fees.
• Leaseweb will make commercially reasonable efforts to support the scalability of worker nodes. For the avoidance of doubt, the 99.95% the Leaseweb Managed Kubernetes Availability Target applies to the availability of existing worker nodes. Leaseweb shall not be held liable by Customer or any third parties for any damages resulting from an inability to provision additional worker nodes.
• Leaseweb Managed Kubernetes Availability Target does not apply to the accessibility of the Leaseweb Website, Customer Portal or API. the Leaseweb Managed Kubernetes Availability Target is also not applicable (i) when scheduled Maintenance occurs with a minimum of a seventy-two (72) hour notice, (ii) in case of an Excluded Event, or (iii) in case a time-critical update must be applied by Leaseweb.
• In the event that in any calendar month the Leaseweb Managed Kubernetes Availability Target is not met by Leaseweb Customer shall be eligible to receive a Service Credit (the “Leaseweb Managed Kubernetes Availability Credit”). Leaseweb Managed Kubernetes Availability Credit shall be equal to one (1) % of the Monthly Services Fees payable by Customer to Leaseweb for the Leaseweb Managed Kubernetes Services.
• The maximum total amount of Leaseweb Managed Kubernetes Availability Credits that Customer may be eligible to in a particular month, shall be limited to fifty (50)% of the Monthly Services Fees for the Leaseweb Managed Kubernetes Service payable by Customer to Leaseweb.

With the introduction of the Ordering API for VPS, we enable you to order VPS via the API. You can leverage this API to streamline and automate your ordering process, enhancing efficiency and reducing manual effort.

What is included in this release?

• The API supports ordering all available VPS products
• Only verified existing customers who do not need to do prepayment while placing an order via website can place orders via API. If you are already on invoice payment and need to get excluded from prepayment requirement, please reach out to Leaseweb Sales or log a support ticket. If you are a new customer, KYC needs to be done before an order via the API can be available.
• Orders are restricted to the sales organisation the API key belongs to
  • For example, with an API key belonging to the US entity, customers can see and order the VPS products available in our US Data Centers
• Available locations
  • Amsterdam (AMS-01)
  • Frankfurt am Main (FRA-01)
  • London (LON-01)
  • Montreal (MTL-02)
  • San Francisco (SFO-12)
  • Singapore (SIN-01)
  • Sydney (SYD-12)
  • Tokyo (TYO-11)
  • Washington DC (WDC-02)

First steps

1. Generate an API key
   • Go to https://secure.leaseweb.com > Administration > API Keys
   • For detailed instructions, refer to API Key Management
2. For all endpoints, you need to set the following header: X-LSW-Auth: {API_KEY}

Endpoints

There are 3 API endpoints available.

1. List all available VPS
2. Get more information on a particular VPS
3. Place the order

1. List endpoint

/products/vps

With this GET endpoint, you can get all the available VPS products for the provided location. The response of this endpoint shows the base price of a VPS. Applicable discounted prices can be queried using the second endpoint.

2. Get a single VPS and its price

/products/vps/{vpsid}

This GET endpoint provides more details about a particular VPS, such as its price, discounts, and all configuration options.

Please note that not all control panels are compatible with the different operating systems. Refer to the link below for compatibility details.

By default, if no operating system is specified in the GET request, Ubuntu 24.04 is chosen as the default, and the response returns the control panels compatible with that operating system. To see the list of compatible control panels with a different operating system, please specify the respective operating system in the request.

Below is an example request to query the details of VPS 3 in AMS-01 location with Ubuntu 22.04 operating system. The response to this request will include the list of compatible control panels with Ubuntu 22.04.

/v1/products/vps/VPS02_3?&location=AMS-01&operatingSystem=Ubuntu 22.04

3. Order a VPS

/products/vps/{vpsid}/order 

A chosen VPS can be ordered with this POST endpoint. To order multiple VPSes, you should send multiple requests.

While placing an order, several extras can be chosen.

• Disk can be upgraded. This upgrade disk is an extra disk that is added to the VPS.
• An operating system can be chosen. This is free of cost. If you don’t provide any parameter for this, by default it is Ubuntu 24.04
• A Control Panel can be added if required. As mentioned above, it needs to be compatible with the selected operating system.
• A Service Level Agreement can be selected.

API Documentation

The API documentation can be found at https://developer.leaseweb.com/docs/#tag/Ordering/operation/getVpsList1

Examples:

Querying all the available VPS products in the Amsterdam entity

curl --location 'https://api.leaseweb.com/ordering/v1/products/vps?location=AMS-01' \
--header 'Content-Type: application/json' \
--header 'X-LSW-Auth: auth'

Querying more details about Leaseweb VPS 3

curl --location 'https://api.leaseweb.com/ordering/v1/products/vps/VPS02_3?location=AMS-01' \
--header 'Content-Type: application/json' \
--header 'X-LSW-Auth: auth'

Ordering Leaseweb VPS 2 in location AMS-01 with Debian 13, a 50GB disk upgrade, Bronze SLA, 1 year billing cycle for a 3-year contract term

curl --location 'https://api.leaseweb.com/ordering/v1/products/vps/VPS02_2/order?location=AMS-01' \
--header 'Content-Type: application/json' \
--header 'X-LSW-Auth: auth' \
--data '{
"operatingSystem": "Debian 13",
"diskUpgrade": "50GB",
"location": "AMS-01",
"serviceLevelAgreement": "BRONZE",
"billingCycle": "1_YEAR",
"contractTerm": "3_YEARS"
}'

Additional Documentation

You can find more information about the VPS product specifications below.

This article explains how to migrate your existing redirects from the Old Redirect Platform to the New Redirect Platform.

Overview

We have introduced a new redirect platform with improved capabilities and HTTPS support. Since this migration is not automated, customers must manually recreate their redirects in the new platform.

What changed?

Migration steps

Migrate Redirects from the old portal to the new portal

1. Log in to Customer Portal
2. Click on “Redirects” from the left menu

3. Click on the “Old redirects page” button in the top right of the page. This will navigate to the old redirects page.

4. In the old redirect page, note down the following values of the redirect that you want to migrate:
   • Domain
   • Redirect Target
   • Type
5. Click the “Go to new redirects” button in the top right of the page. This will take you back to the new redirects page

6. Click the “Create New Redirect” button in the top right

7. Follow the steps from here: Adding a new redirect

Back to the top ↑

Update DNS configuration

Your next step depends on where your DNS is managed.

DNS managed by Leaseweb

If your domain uses Leaseweb nameservers, then:

1. Go to the hosting overview page
2. Search for the domain name
3. Click on Manage DNS
4. Update or create an A record to point to the new redirect platform IP address

DNS managed by an external provider

If your DNS is managed externally, then log in to your DNS provider. And update or create an A record to point to the new redirect platform IP address.

Back to the top ↑

Secure your redirect (HTTPS)

To make your redirect more secure, you can enable HTTPS using the Let’s Encrypt SSL certificate.

In the new redirect platform, this can be done from the Secure page. For step-by-step instructions, please refer to this guide.

Possible downtime/break scenarios

Migration is generally smooth, but issues may occur in the following cases:

• DNS not updated: Redirect will continue pointing to the old platform. The new redirect will not work.
• Incorrect IP Address: Redirect may fail. The domain may not resolve properly.
• Delay in DNS Propagation: Temporary inconsistent behavior, some users may see the old redirect, others may see the new.
• HTTPS Not Enabled: Redirect may fail for HTTPS requests. The browser may show security warnings.
• Old Platform Dependency: If you delete the old redirect before the DNS update completes, this may stop the redirect from working as expected.

To avoid these issues, always follow the best practices:

• Create the redirect in the new platform first
• Update the DNS
• Verify the redirect is working
• Only then, remove the old redirect

Back to the top ↑

Leaseweb offers a variety of uplink capacity and bandwidth options, ranging from 100Mbps to multiple 100Gbps ports.

Uplink types are split in 2 categories: equipment in shared racks (with a shared Top-of-Rack switch) and racks (Dedicated and Colocation). See more details below:

This article focuses on providing a brief overview of the advanced features and how to enable them as part of your backup plans, such as:

1. How to modify a pre-existing protection plan
2. How to configure this protection plan to enable Advanced features
3. What features are not included as part of the standard protection plan

Modify a pre-existing protection plan

To benefit from the advanced features of Acronis, you first need to create or edit a protection plan. The examples below explain the plan settings from the perspective of a pre-existing protection plan.

The following instructions should lead you to the protection plan settings :

1. In the Management / Protection Plans menu
   
2. Select a Protection plan, and click Edit
   
3. Expand the Backup Section by using the light-blue arrow on the side.
   
4. You will now see advanced options available for this protection plan
   
   

Customize Advanced Options

Here is an overview of the different options that are available under a protection plan, and where to find more information about these features. Feel free to enable one or more of these features according to your needs.

Allows Continuous Data Protection (CDP)​

To enable Continuous Data Protection (CDP)​, simply turn on the toggle for “Continuous Data Protection (CDP)​”:

Antivirus & Antimalware protection

To enable Antivirus & Antimalware protection, turn on the associated Toggle and customize the appropriate options.

Data protection map

To enable Data protection map, turn on the associated Toggle and customize the appropriate options.

Backup of applications

For backup application such as 

• Microsoft SQL Server
• Microsoft Exchange Server
• Microsoft Active Directory
• Oracle Database
• cPanel

The following instructions should guide you on how to enable it for the protection plan :

1. Click “Disabled” beside the “Application backup” category
   
2. Select and customize the application you want to backup as part of this Management plan
   
   

For further information about advanced application backup, please visit the following

One-click recovery

Features not available as part of Standard Protection

While a lot of new features were made available as part of Acronis Standard protection, the following features are only available by purchasing a specific package, that will involve additional costs.

Please contact Leaseweb’s sales team to verify availability if you need one of the following features:

Back to the top ↑

Our Managed Kubernetes platform supports the Gateway API – a modern and flexible way to manage ingress and traffic routing in Kubernetes.

You can either use Cilium as your Gateway API provider out of the box or install any other compatible implementation you prefer.
The platform does not require you to use a specific Gateway API provider. You have full control over which implementation you use.

What Is Gateway API?

Gateway API is a native Kubernetes API that standardizes how traffic enters and moves through a cluster. It is meant to be the long-term replacement for the traditional Ingress API.
Compared to Ingress, Gateway API provides:

• A role-oriented model (cluster operators, platform admins, application owners)
• Clear separation between infrastructure (Gateways) and routing rules (Routes)
• First-class support for advanced use cases such as:
  • Multiple listeners (HTTP, HTTPS, TCP, TLS)
  • Cross-namespace routing
  • Fine-grained traffic policies
• A provider-agnostic contract, allowing multiple implementations to coexist

Thanks to these improvements, more teams are choosing the Gateway API as their preferred way of managing traffic in Kubernetes.

Responsibilities and Operational Model

Cluster Administrator Responsibilities

Gateway API uses Custom Resource Definitions (CRDs) that work with all implementations.
The cluster administrator is responsible for:

• Installing the Gateway API CRDs
• Upgrading the Gateway API CRDs when required
• Ensuring CRD versions are compatible with the chosen provider

Managing the CRD lifecycle is kept separate from installing providers. This helps prevent unexpected changes across your cluster.

Using Cilium as a Gateway API Provider

If you decide to use Cilium as your Gateway API provider, follow these steps:

1. Prerequisites required in the Cilium configuration are already considered by us.
2. The following Gateway API CRDs must be installed. Please follow the instructions for installing the gateway CRDs according to Cilium’s Gateway API documentation.
   • Make sure the version of the Gateway API CRDs you chose to install is compatible with the installed Cilium version in your cluster.
3. After installing the Gateway API CRDs, you need to restart the Cilium Components using the following commands:

kubectl -n kube-system rollout restart deployment/cilium-operator 
kubectl -n kube-system rollout restart ds/cilium

Since you are managing the Gateway APIs, it is important to consider these items:

1. Once in a while, we will update Cilium and will announce it to our customers.
   • Do not forget to update CRDs after Cilium Upgrades if it is required.
2. Configure Cilium Gateway resources according to your traffic requirements.

For detailed installation steps, configuration options, and supported Gateway API features, see the official Cilium documentation.

Using Other Gateway API Providers

If you choose another Gateway API provider, you need to follow their documentation accordingly. Check the provider’s documentation for details on supported features, limitations, and how to upgrade. not modify or restrict third-party Gateway API providers.

Summary

• Gateway API is the modern, extensible successor to Ingress. Our platform supports the Gateway API in a provider-agnostic manner.
• Customers remain free to choose and operate alternative implementations.
• Cilium is fully managed and supported as a Gateway API provider.
• Cluster administrators manage Gateway API CRDs.This approach gives you flexibility, follows standards, and ensures long-term compatibility with Kubernetes.          

Bare metal servers deliver raw performance and give full control. Every workload, application, and service running on a Dedicated Server depends directly on the health of its physical components. That makes hardware monitoring not just useful but essential.

Native hardware monitoring via IPMI

For bare metal servers, Leaseweb provides hardware monitoring:

The hardware health metrics are collected directly from the server’s management interface – without having to install an agent on the operating system and thereby ensuring that we do not interfere with the customer environment.

This includes data from sensors such as temperature, power, fan, and other system health indicators. Each server exposes different metrics depending on the brand and the model.

Key Characteristics

How to enable hardware monitoring on your server

Our monitoring system collects all the metrics via the server’s IPMI interface. For this purpose, we create a dedicated read-only IPMI user called “lswhwmon” on each server.

This user is exclusively used to collect hardware metrics for monitoring.

How to manage hardware monitoring:

1. To create the required user an IPMI reset is needed
   • The user then gets created automatically
2. To disable hardware monitoring, delete the user
   • The details of this user can be found in the remote management portal of the server and under the Credentials page of the server in the Customer Portal:

3. See the collected metrics in the Customer Portal under Usage -> Hardware Monitoring
   • The metrics are refreshed every 5 minutes: