• 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 Unable to access Plesk due to disk capacity exceeded.

eyrffd

New Pleskian
Server operating system version
AlmaLinux 8.7 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.48.0
Hello.

I just joined the Plesk forum. Even if it's awkward, please understand. Please let me know if I am violating the rules of the Plesk forum.

----------

I can't access my Plesk panel. When accessing the Plesk panel, only a blank white window is displayed.

My website is also accessible but does not work properly. Some pages load up to the title but the rest of the content doesn't, and on some pages the CSS doesn't load. Also, some images are not displayed.

I think the reason this is happening is that the disk capacity is exceeded. I logged in via SSH and checked the disk capacity, and it was full. So I tried to log in to Plesk via SSH, see what was taking up the most space, and take action. So when I ran the plesk login command, I got an "exit status 255".

There's nothing I can do now. How can I solve the problem?

----------

Thank you.
 
>> There's nothing I can do now.
Well, you can free up some disk space by removing the files/logs you no longer require via SSH. I'd start with locating large log files, for example:
# find /var/log -type f -size +100M

Treat that as an example, which might be or not relevant in your case.
 
>> There's nothing I can do now.
Well, you can free up some disk space by removing the files/logs you no longer require via SSH. I'd start with locating large log files, for example:
# find /var/log -type f -size +100M

Treat that as an example, which might be or not relevant in your case.
Thank you for answer. Fortunately, I seem to have found a way.
 
Back
Top