Skip to content
HostupSupport
hostup.se

Warnings on your VPS: disk, CPU and pending restart

Checked against the client area 29 October 2026

Sometimes a notice at the top of the server’s page says that something is limited or waiting for a restart. This page explains what each notice means and what to do. The disk and CPU notices show on the Overview tab. Pending changes show on every tab.

Open your servers in the client area

Remove a temporary disk limit

Section titled “Remove a temporary disk limit”

The Temporary disk limit active notice appears when the server reads or writes far more on its disk than normal. The disk is then slower until the limit is removed. The notice shows how much the server writes or reads per day compared with the size of the disk. Expires shows when the limit ends by itself. If it has been applied several times within 30 days, it has no end date.

  1. Find out what on the server is writing or reading so much. What to check lists the most common causes, for example heavy swapping because the server has too little RAM.
  2. Fix the cause.
  3. Click I've fixed it — remove the limit.
  4. Click Remove the limit now.

The limit is removed straight away. If the heavy disk activity is still going on, it is applied again automatically.

  • If swapping is the cause, reduce the memory load or give the server more RAM. Click Upgrade plan (more RAM) in the notice. The Billing tab opens, where you change package. On a VPS billed by the hour, the support form for raising a limit opens instead. See Upgrade or downgrade your VPS or web hosting.
  • You get an email when the limit is applied. If you can remove it yourself, the email has a link that does the same as the button.
  • If the limit is on writes and has been applied several times within 30 days, you can’t remove it yourself. The notice then says so. Open a ticket once the cause is fixed. Support removes the limit after a review.

Open a ticket

Lift a CPU limit

Section titled “Lift a CPU limit”

The CPU limited to 50 % notice appears when the server has run at full load for several days. It may then use CPU time equal to half of its vCPUs. The server keeps running as usual but works more slowly when it needs more than that. The first time, you get an email warning before the limit is applied.

  1. Find out what is using the CPU. What to check explains how. It is often a process that is stuck, or a program an outsider has started.
  2. Stop the process or fix the cause.

You don’t need to do anything else. The limit is lifted by itself once the load has stayed low for a day. The threshold is shown under Lifted automatically in the notice.

Restart for pending changes

Section titled “Restart for pending changes”

The Pending Configuration Changes notice means the server has changes that only take effect when it is restarted, for example a new CPU type or changed memory. Each change is shown with its new value. Current shows what applies now.

  1. Pick a time when the server can be down for a short while.
  2. Click Reboot Now in the notice.
  3. The Restart server dialog opens. Click Restart.

The changes apply once the server has started again. A restart from inside the server is not enough. Restart it from the client area.

  • If it says No deadline - reboot when convenient, there is no time limit.
  • If it shows a date, the restart should be done before then. If you can’t make it, click Request Extension. The date moves forward straight away. The number of extensions is limited. When they are used up, it says No more extensions available.
  • If the change is a new CPU profile, the notice explains what that means. Performance, specifications and price are not affected.

Good to know

Section titled “Good to know”