Skip to main content

Softaculous: Install WordPress and Other CMS in 1 Minute

Hosting & cPanel · 19.04.2026 · 6 min read
Illustration for “Softaculous: Install WordPress and Other CMS in 1 Minute”

Softaculous is an auto-installer built into cPanel. It deploys more than 400 ready-made scripts — WordPress, Joomla, Drupal, PrestaShop, Magento, and others — through a single form, with no manual database creation or FTP file uploads.

Installing WordPress via Softaculous

cPanel → Software → Softaculous Apps Installer → WordPress → Install.

Installation settings

FieldRecommendation
Choose Protocolhttps://
Choose DomainYour domain
In DirectoryLeave empty (root)
Admin UsernameNot "admin"! Pick a unique one
Admin PasswordAt least 16 characters
Admin EmailYour working email

Only pick https:// for "Choose Protocol" if an SSL certificate for the domain is already issued — otherwise Softaculous writes links to a non-existent https address into the database, and after the certificate is installed you will still have to fix the site through a URL change.

Typical error during installation

If the target directory is occupied by old files or the directory permissions are wrong, the install stops with this message:

Error: Unable to create directory wp-content/uploads. Is its parent directory
writable by the server?

This means the user PHP runs as has no write permission on the target folder — usually because the directory was created manually over FTP with permissions 755 instead of 750/755 for the process owner. The fix is to set 755 permissions on the folder through the cPanel File Manager and retry the install.

The second common failure cause is a database with a similar name already existing from a previous failed attempt:

Error: A MySQL database already exists with the name you provided: example_wp1

Softaculous does not overwrite existing databases automatically for safety reasons. You either need to delete the old database via phpMyAdmin or set a different database name prefix in the advanced installation settings.

Managing installations

Softaculous → All Installations — a list of every CMS installed on the account.

  • Edit — change the URL, directory, or settings
  • Clone — copy the site to another domain (for staging)
  • Backup — create a backup copy
  • Remove — delete the installation along with its files and database

Cloning for staging

Softaculous → My Installations → select the site → Clone
Clone To Domain: staging.example.com
Clone Directory: (leave empty)

A full copy of the site on the subdomain is ready in about 2 minutes.

After cloning, make sure to restrict access to staging through .htaccess (Basic Auth or an IP whitelist), otherwise search engines will index the duplicate content and it will start competing with the main site in search results.

Auto-updates and backups

ComponentAuto-updateRisk
WordPress core (minor)Enabled by defaultLow
WordPress core (major)Disabled by defaultMedium
PluginsConfigured separately in SoftaculousMedium-high
Backup before updateRecommended to enableLowers the risk of every item above

The "Auto Upgrade" option in Softaculous installation settings does not update third-party plugins or themes — it only covers the CMS core. Plugin updates must either be enabled with a separate "Upgrade Plugins" checkbox or run manually from the WordPress admin panel, checking compatibility before applying them. A backup taken before an auto-update uses extra disk space on the plan — on sites with a large media library, watch the quota, otherwise the next update can fail simply because there is no room left for the backup.

When Softaculous does not fit

  • The project needs a non-standard stack — a Node.js backend, Docker containers, task queues — Softaculous only installs PHP scripts from its own catalog
  • You need a controlled Git deploy with code review and version rollback — a cPanel Git Version Control or CI/CD setup fits better here than a one-off install through a web form
  • You need a non-standard PHP version or a rare extension for just one plugin — Softaculous installs the CMS on the account's current active PHP version and does not manage the version itself
  • The site already exists and needs migrating rather than creating from scratch — migration uses a backup and manual database import, not the auto-installer

Verifying the result

# After installation, check file permissions
find ~/public_html -type d -exec chmod 755 {} \;
find ~/public_html -type f -exec chmod 644 {} \;

Open the site in an incognito browser window (no cache) and confirm that both the homepage and the /wp-admin/ admin panel load without 500 errors or a blank white screen. More on installing WordPress manually through cPanel is in the article how to install WordPress via cPanel, and on speeding up an already-installed site in speeding up WordPress: cache, images, and CDN.

Frequently asked questions

What should you do if a WordPress install through Softaculous stops with an error about write permissions on a directory?

That error almost always means the PHP user lacks write permission on the target folder, often because the directory was created manually over FTP with the wrong permissions. The fix is to set the right permissions through the file manager and retry the install; a second common cause is a leftover database with a similar name from an earlier attempt.

Is it fine to pick the https protocol during installation if the SSL certificate has not been issued yet?

No, only choose https if the certificate for the domain has already been issued and is active. Otherwise Softaculous writes links to a non-existent secure address into the database, and once the certificate does appear, the site will still need separate fixing through a URL change — it is simpler to install over http first and switch to https later.

Does a site clone created for staging need extra protection?

Yes, definitely: after cloning, access to the staging copy should be restricted through the server's configuration file, otherwise search engines will index the duplicate content and it will start competing with the main site in results. A basic password or an IP restriction is enough to keep the copy visible only to you and the team.

In which cases is it better to migrate an existing site manually instead of installing a new one through Softaculous?

If a site already exists and needs migrating rather than being created from scratch, an auto-installer is not the right tool — migration uses a backup of the files and a manual database import. The same applies to a non-standard stack without PHP scripts, or a case where one component needs a rare PHP version unavailable on the account.

Was this article helpful?
← Back to Knowledge Base Ask Support