Free tools Windows power users keep installed
One-click scans. No signup required.
To host ClassicPress, you need a publicly reachable web host, a domain, HTTPS, a supported PHP and database stack, and a way to transfer files. Most site owners can install it either manually with SFTP or through Softaculous or Installatron when their hosting panel provides one. Developers who need repeatable deployments can use Composer, but that route changes the normal file layout and web-root configuration.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
This guide covers the requirements, host-selection checks, exact installation sequence, one-click installers, WordPress migration, HTTPS, backups, updates, and the deployment problems that most often prevent a new ClassicPress site from working.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What ClassicPress hosting actually requires
ClassicPress is self-hosted software. Unlike a hosted website builder, it does not provide the server, domain, database, email, backups, or TLS certificate for you. You rent or operate a server and install ClassicPress into that environment.
A usable production setup has these parts:
- Public hosting: shared hosting, a virtual server, managed WordPress-compatible hosting, or your own server with a public IP address.
- A domain name: the domain or subdomain visitors will use.
- Web server: Apache, Nginx, or LiteSpeed configured to serve the site and, where needed, process rewrite rules.
- PHP: a version supported by the ClassicPress release you install.
- MySQL or MariaDB: a database and a database user with permission to create and update tables.
- HTTPS: an SSL/TLS certificate, such as a free Let’s Encrypt certificate, with the domain pointing to the host.
- File access: preferably SSH and SFTP, or a hosting-panel file manager.
Your host may supply several of these automatically. A one-click installer can create the database and files, while a managed host may also handle certificates, backups, and updates. You still need to verify what is included rather than assuming that every plan supports ClassicPress.
#1 Best Overall
ClassicPress version requirements
Requirements can change between releases. Use the ClassicPress requirements page as the authority when you deploy, and compare its current values with the versions offered by your host. The version guidance below reflects the requirements and recommendations documented for ClassicPress 2 and the newer release guidance available at the time of writing.
| Component | Minimum documented requirement | Recommended setup |
|---|---|---|
| PHP | PHP 7.4 | PHP 8.3 or 8.4; newer release guidance says PHP 8.4 or greater |
| Database | MySQL 5.0 or higher | MySQL 5.7 or higher, or MariaDB 10.3 or higher; newer release guidance says MariaDB 10.4 or greater |
| Web server | Apache 2.4 | Apache 2.4 with mod_rewrite, Nginx, or LiteSpeed |
| Transport security | HTTPS is required for a proper production site | An active SSL certificate, commonly from Let’s Encrypt |
The newer and older recommendations differ slightly, so do not treat one version number as permanent. Ask the host which PHP, MySQL or MariaDB, and web-server versions are available now and confirm them against the requirements page for the exact ClassicPress release you plan to use.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose an installation method
There are three practical deployment paths. The best choice depends on whether you value simplicity, control, or automation.
| Method | Best for | Control and repeatability | Host requirements |
|---|---|---|---|
| Manual ZIP installation | Site owners who want a transparent, conventional setup | Full control over files and database settings; repeatable with a documented checklist | File transfer access and a MySQL or MariaDB database |
| Softaculous or Installatron | Users whose cPanel, DirectAdmin, Plesk, or similar panel exposes ClassicPress | Fast setup; advanced options depend on the panel and host | The host must offer the installer and a supported PHP version |
| Composer | Developers managing deployments as code or installing release and nightly builds | Highest automation potential, but a different project layout and web-root model | SSH, Composer, and server configuration that keeps the project root private |
One-click installation does not mean the host is managed for you. You remain responsible for the domain, HTTPS, updates, backups, and diagnosing application errors unless your plan explicitly includes those services.
Check a host before you buy or configure it
Compatibility is more important than a low introductory price. Send the host a concise checklist and save its answers in your deployment notes.
- Which PHP versions can you select for this domain, and can you choose PHP 8.3 or 8.4?
- Which MySQL or MariaDB versions are running, and can you create a separate database and user?
- Is the web server Apache 2.4, Nginx, LiteSpeed, or another supported configuration?
- For Apache, is
mod_rewriteenabled so pretty permalinks work? - Does the control panel offer ClassicPress through Softaculous or Installatron?
- Can you use SSH and SFTP, and what hostname, port, and account permissions are required?
- Is an SSL certificate included, and can you use Let’s Encrypt?
- How are backups scheduled, where are they stored, and how do you restore a single site?
- Does the host provide a staging site or an easy way to clone production?
- Does it automatically update WordPress installations, and can that behavior be disabled for a migration?
- What support channel handles database, DNS, PHP, and certificate problems?
Provider pricing, uptime promises, migration assistance, and affiliate terms change frequently and are not established by ClassicPress documentation. Verify those items directly before committing.
Manual ClassicPress installation with SFTP
Manual installation is the most portable method. The official guide recommends arranging an SSH account and using SFTP to copy files. SFTP encrypts the transfer; ordinary FTP sends credentials and data without the same protection.
Prepare the server and local tools
You need a hosting account or server, a domain pointed toward it, a file-transfer program, and a MySQL or MariaDB database. FileZilla and Cyberduck are examples of SFTP clients. If your host provides shell access, you can also use command-line tools such as sftp and unzip.
Before uploading, decide whether ClassicPress will live at the domain root, such as example.com, or in a subdirectory, such as example.com/blog. The choice affects the installation directory and the URL visitors will use.
Follow the six-step sequence
- Download the latest ClassicPress ZIP. Obtain the release from the official ClassicPress download location and keep the ZIP until the site is working so you can identify exactly what was installed.
- Unzip it locally. Extract the archive on your computer. Upload the extracted files, not merely the ZIP file, unless your host specifically provides a server-side extraction tool.
- Upload the files. Connect with SFTP and place the unzipped ClassicPress files in the document root for the domain, or in the subdirectory selected for the site. Confirm that the directory contains the application files and that the web server can read them.
- Create a database and user. In the hosting panel, create a MySQL or MariaDB database, a database user, and a strong password. Grant the user all permissions on that database. Record the database name, username, password, and database host; some hosts use a server name other than
localhost. - Open the domain. Visit the domain in a browser. If the files and DNS are in place, ClassicPress should redirect you to its installation screen. A blank page, server error, or DNS error at this point indicates a hosting, file-placement, PHP, or DNS problem rather than an incorrect database password.
- Complete the installer. Enter the database name, user, password, and host exactly as supplied by the host. Choose the site title, administrator username, administrator password, and email address. Submit the installer and sign in to the administration area.
If you cannot find the database-creation controls, ask the host for the exact panel path and the database host value. Shared hosts often prepend an account identifier to database and user names, so copying only the name you intended may produce an authentication failure.
Secure the first login
Use a unique administrator username and a long password that is not reused elsewhere. Confirm that the administration URL loads over HTTPS, then remove any temporary archive or installation files your host left outside the document root. Set the site and administration URLs to the final HTTPS address before publishing content.
Install ClassicPress with Softaculous or Installatron
ClassicPress documents one-click availability through Installatron and Softaculous in panels including cPanel, DirectAdmin, and Plesk. Some hosts also expose Virtualmin or Docker-based options. The exact labels and fields vary by host.
Softaculous quick installation
- Sign in to the hosting control panel and open Softaculous.
- Search for ClassicPress and choose the install action.
- Select the protocol and domain. Use the HTTPS version once the certificate is active.
- Leave the installation directory empty for a root-domain site, or enter a directory name for a subdirectory installation.
- Enter the site name, description, administrator account, password, and email address.
- Submit the form and wait for the installer to create the files and database.
- Open the reported site and administration URLs, then test HTTPS and permalinks.
The documented Softaculous guidance says the host must support at least PHP 7.4 and recommends PHP 8.3 or 8.4. Select the highest supported version that is compatible with your plugins and theme, and check the current ClassicPress requirements before proceeding.
Custom installation settings
Custom Install exposes additional settings such as database naming, table prefixes, language, automatic update behavior, and backup or notification options. Their names and availability vary according to the host. Review every automatic-update checkbox: an installer setting can differ from the host’s own scheduled update system.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →When one-click installation is missing
Do not install an unrelated script and attempt to convert it by replacing files. Use the manual ZIP procedure, or ask the host whether ClassicPress can be added to its installer catalog. A missing installer does not prevent a correct manual deployment if the PHP, database, web server, and file-access requirements are met.
Point the domain at the new site and enable HTTPS
DNS must direct the domain to the server before visitors can reach the installer. Hosts typically provide an IP address for an A record and, for IPv6, an AAAA record. Use the exact records supplied by the host and allow time for DNS changes to propagate.
After DNS resolves, issue or activate an SSL certificate. Let’s Encrypt is a free certificate source listed by ClassicPress documentation, and many control panels can request and renew it automatically. Test both the homepage and administration area at the HTTPS address.
- Redirect HTTP requests to HTTPS after confirming the certificate works.
- Replace any hard-coded HTTP site URL with the HTTPS URL.
- Check images, scripts, stylesheets, feeds, and embedded content for mixed-content warnings.
- Verify that the certificate covers the exact host name, including a
wwwvariant if you use one.
Migrate an existing WordPress site
ClassicPress provides a Migration Plugin for switching an existing WordPress site. Migration changes the application files while preserving the site’s content and settings through the plugin’s process; compatibility still depends on your themes, plugins, and server environment.
Prepare before migration
- Create a tested backup of the database and all site files. A backup that has never been restored is not a recovery plan.
- Build a staging copy when the host supports it. Test the migration there first so visitors are not exposed to a broken administration area.
- Inventory active themes, plugins, custom code, scheduled tasks, and integrations. Confirm that each critical component supports ClassicPress.
- Check whether the host automatically updates WordPress. Automatic updates can replace files during or after migration.
- Ask the host to disable automatic WordPress updates for the site before migrating. ClassicPress specifically warns about this behavior and tells customers of one named hosting provider to contact support for the change.
Run and verify the migration
- Install the ClassicPress Migration Plugin in the WordPress administration area.
- Read its compatibility notices and follow its migration prompts.
- Run the migration during a maintenance window or on staging first.
- Sign in to the resulting ClassicPress administration area and update the site URL if the domain or protocol changed.
- Test the homepage, administrator login, media library, forms, search, feeds, scheduled tasks, email delivery, and every revenue or customer workflow.
- Keep the pre-migration backup until the migrated site has operated successfully through at least one normal update and backup cycle.
Backing up and staging are prudent operational practices, not a claim that every ClassicPress installation requires a particular backup product or staging service.
Composer and Bedrock-style deployments
Composer is an advanced option for teams that already manage PHP dependencies and deployments from the command line. The ClassicPress Composer guide supports installing recent releases and nightly builds and can automate repeatable steps.
Composer layouts differ from a regular ClassicPress ZIP installation. In a Bedrock-style arrangement, configure the web server to serve only the web/ subdirectory. Never expose the project root, because it may contain configuration files, dependency metadata, and other material that should remain private.
- Use a deployment script or version-controlled configuration so production and staging use the same process.
- Set environment-specific database credentials outside publicly served files.
- Make the web-root setting explicit in Apache, Nginx, or the hosting panel.
- Test Composer updates on staging before applying them to production.
Choose Composer only if you can maintain SSH access, dependency management, server configuration, and rollback procedures. For a single conventional site, the ZIP or one-click path is easier to audit and recover.
Recommended Free Tools
Backups, updates, and routine operations
Hosting ClassicPress is an ongoing operation, not a one-time upload. Establish these routines before publishing important content:
- Backups: retain database and file backups on storage separate from the live server, and periodically perform a restore test.
- Updates: read ClassicPress release notes, update on staging first when possible, and verify plugins and themes after each update.
- PHP lifecycle: track your host’s PHP support schedule and move off end-of-life versions before the ClassicPress minimum catches up with them.
- Security: use HTTPS, unique administrator credentials, least-privilege accounts, and SFTP rather than unencrypted FTP.
- Monitoring: check certificate renewal, disk space, database availability, error logs, contact forms, and scheduled jobs.
- Recovery: document the hosting-panel login, SFTP details, database credentials, DNS records, and restore sequence in a secure password manager.
Troubleshoot the common failure points
The domain shows a DNS or connection error
Confirm the domain’s A or AAAA record matches the host, check whether you are using the correct www variant, and wait for DNS propagation. Test the host’s temporary address if one is provided.
The installer reports a database connection error
Recheck the database name, user, password, and database host. On shared hosting, use the fully prefixed names shown in the panel and confirm that the user has privileges on that database.
The page is blank or returns a 500 error
Verify that the selected PHP version meets ClassicPress requirements, inspect the server’s PHP error log, and temporarily disable a recently added plugin or theme if the error appeared after activation. Check file permissions and confirm that the files were uploaded into the domain’s actual document root.
Pretty permalinks return 404 errors
On Apache, confirm that mod_rewrite is enabled and that the directory permits rewrite rules. On Nginx or LiteSpeed, use the host’s documented ClassicPress or WordPress-compatible rewrite configuration. Save the permalink settings again after correcting the server rule.
HTTPS causes redirects or mixed content
Confirm the certificate covers the requested host name, set the site URL to HTTPS, and remove hard-coded HTTP asset URLs. If redirects loop, check whether both the host and an application rule are forcing different protocols.
A WordPress migration keeps reverting or breaking
Ask the host whether an automatic WordPress updater is still enabled, disable it before retrying, and restore the backup if the migration changed production unexpectedly. Re-test incompatible plugins and custom code on staging rather than repeatedly changing the live site.
Decision checklist
Use the following short decision rule:
- Choose manual installation when you want a conventional file layout, understand basic hosting controls, and need portability between hosts.
- Choose Softaculous or Installatron when your panel offers ClassicPress, you want the database and files created for you, and you accept host-specific settings.
- Choose Composer when your team already uses SSH, dependency management, version control, staging, and scripted rollbacks.
Whichever path you choose, verify the current ClassicPress requirements, use HTTPS, keep recoverable backups, and check the host’s automatic-update behavior before putting the site into production.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
