• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Unallocated partition and lower ram [How to make Plesk aware of hardware changes?]

exceedsrl

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
18.0.57
Hi everyone,
I have a small problem, I can't understand if it's caused by Plesk or by the VPS.
Basically we upgraded the VPS from the ovh provider, doubling everything, core, ram and storage.
At the start I had 2 cores, 4GB of RAM and 80GB of storage, now I have everything doubled, therefore, 4 cores, 8GB of RAM and 160GB of storage.
After updating, ovh tells me that I have to allocate the partition myself.
By launching the command that tells me ovh, I already see all 160GB of the partition. Despite this, on Plesk it continues to see 80GB, furthermore, again on Plesk, in the monitoring I see 4GB of RAM, while in the server information I see 8GB.
Is there something I need to do? I attach the screenshots.
 

Attachments

  • 1.PNG
    1.PNG
    8.6 KB · Views: 1
  • 2.PNG
    2.PNG
    5 KB · Views: 1
  • 3.PNG
    3.PNG
    43.6 KB · Views: 0
  • 4.PNG
    4.PNG
    19.3 KB · Views: 0
  • 5.PNG
    5.PNG
    47 KB · Views: 1
Back
Top