Softaculous is the one-click application installer built into Plesk that deploys WordPress, Joomla, Magento, Nextcloud and hundreds of other web applications for you. Every so often an install stops part-way and reports that it failed. When that happens, the error Softaculous recorded is what tells you why, and reading it turns a vague "it did not work" into a fixable, specific fault.
This guide shows you, as the owner of a Plesk subscription on Noiz hosting, where Softaculous records a failed installation, how to read that record, and a worked example of a common failure and its fix.
Last reviewed: 27 July 2026, against the current stable release of Softaculous. This guide is written for Noiz Plesk hosting and is kept current against Softaculous. It complements, and does not replace, the official Softaculous documentation linked below.
Official Documentation Reference
- Softaculous Logs in the Admin Panel (server-administrator reference for the on-disk log files).
- Softaculous documentation home.
Prerequisites
- A Plesk hosting subscription on Noiz with Softaculous available (you reach it from the Plesk left-hand menu under Applications, or from the Websites & Domains tab).
- An installation that has failed, so there is an error to look at.
Read the on-screen error first
When an installation fails, Softaculous does not hide the reason. The results page shows the failure with a red banner and a short message describing what went wrong, and the installation is usually rolled back so it does not leave a half-built site behind. This on-screen message is the single most useful thing you have as a subscription owner, because you can see it without any server-level access.
Before you do anything else, read that message in full and copy it somewhere. Nine times out of ten it names the exact problem: a directory that is not empty, a database limit reached, or a download that did not complete. If you closed the page too quickly, start the same install again and let it fail once more so you can capture the wording.
Where Softaculous keeps its error logs
Behind the on-screen message, Softaculous writes a persistent record to two log files on the server:
/var/softaculous/error_log.logcaptures critical failures inside Softaculous itself./var/softaculous/logs/softaculous.logrecords general operational activity, at the logging level set in Softaculous.
A server administrator reads these from within the Softaculous Admin Panel under Settings > Error Logs, where a drop-down chooses which of the two files to display and the entries appear in a panel below.
Scope, honestly: those two files and the Softaculous Admin Panel live at the server level, not inside your subscription. On Noiz managed Plesk hosting you have your subscription in Plesk, not shell access or the server-wide Softaculous Admin Panel, so you cannot open /var/softaculous/error_log.log yourself. That is by design and it keeps the shared server secure. If the on-screen message is not enough to solve the problem, this is where Noiz support steps in: raise a ticket and Noiz will pull the matching lines from the server-level log for your subscription. If instead you run your own Plesk server and hold the administrator login, you can open the Admin Panel path above directly.
A worked example: the target directory is not empty
One of the most common Softaculous failures on a Plesk subscription reads along these lines on the results page, and is mirrored in the log:
Installation Failed
The directory you have specified already exists and is not empty.
Please specify an empty directory or a directory that does not exist.Why it happens: Softaculous refuses to install over the top of existing files so that it never overwrites content you meant to keep. This appears when you try to install into the domain root (httpdocs) of a subscription that already has a site in it, or into a subfolder you used for a previous install and did not clear.
How to fix it:
- Decide where the new application should live. To put it at the top level of the domain (for example
yourdomain.com), the In Directory field on the Softaculous install form must be left empty. - To install into a subfolder instead (for example
yourdomain.com/blog), enter a folder name that does not yet exist in In Directory. - If you genuinely want to reuse a location that already has files, remove the old contents first using the Plesk File Manager (or delete the previous installation from the Softaculous Installations list so Softaculous cleans it up for you), then run the install again.
Other common failures and their fixes
- Database limit reached (message mentions creating the database, or a MySQL error): your hosting plan has a fixed number of databases and you have used them all. Remove an unused database in Plesk under Databases, or move to a plan with a higher limit.
- Disk quota exceeded: the install runs out of space part-way. Free up space in File Manager or upgrade the plan, then retry.
- Download or mirror failure (message mentions failing to download the install package, or a cURL error): the server could not fetch the application package. This is transient more often than not, so retry after a few minutes. If it keeps failing it is a server-side matter, so contact Noiz.
- Permission or write errors (failed to create a directory or file): usually a leftover from a previous failed attempt. Clear the target directory as in the worked example above, then reinstall.
Still stuck?
If the on-screen error does not point to something you can change yourself, the answer is almost always in the server-level Softaculous log, which Noiz can read for you. Open a ticket from your Noiz client area, quote the exact wording of the failure and the application, domain and directory you were installing into, and Noiz support will check /var/softaculous/error_log.log for your subscription and tell you exactly what to do next.
