Stop clicking Install repeatedly. A one-click WordPress installer only automates copying WordPress files and creating a database; it still relies on correct domain and directory mapping, a supported PHP runtime, a working database server and credentials, writable files, and HTTPS. Record the exact error and installation path, then test those layers in order. This approach fixes the underlying failure without deleting an existing site or database by mistake.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What a one-click installer actually does
Hosting control panels package several manual tasks into one form. The installer normally places WordPress files in the directory you select, creates or connects a database, writes database details to wp-config.php, and presents a URL for the new site. None of those actions removes the hosting prerequisites. The domain must resolve to the intended account, the selected directory must be the directory served for that URL, PHP must execute, the database server must accept the supplied credentials, and WordPress must be allowed to write where it needs to.
As an Amazon Associate I earn from qualifying purchases.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThat is why an installer can report success while the site is blank, show a directory listing, display PHP source code, or fail with a database message. Treat each symptom as evidence about a different layer rather than as a reason to run the same installer again.
First, capture the failure and its target
Before changing files, databases, or permissions, make a short record. It prevents a second attempt from hiding the original cause and gives hosting support something actionable.
- Copy the complete message. Include the heading, any error code, and the time it appeared. A partial phrase such as “installation failed” is not enough to distinguish a database error from a path or PHP error.
- Write down the exact domain or subdomain. Include whether you used the www or non-www form and whether the address is HTTP or HTTPS.
- Record the directory selected in the installer. An installation into a subdirectory such as
public_html/blogwill not appear at the account root unless the domain is mapped there or you open the corresponding subdirectory URL. - Check the domain’s destination. Confirm that DNS and the hosting panel point the domain to the intended hosting account and document root. A successful install on the wrong account can look like a missing installation.
- Open the same path the installer used. Do not test only the domain root if the installer was configured for a subfolder. Conversely, do not add a subfolder to the URL when the selected directory was the document root.
Do not delete a partial directory or database while you are still collecting this information. If another site already uses the domain or database, an indiscriminate retry can overwrite its data.
Confirm the hosting requirements before editing anything
WordPress’s official Before You Install guidance states: “Before installing WordPress, you need to check that your web hosting provider fulfills the necessary software and conditions.” The requirements page available on 2026-10-14 lists PHP 7.4 or greater, MySQL 5.7 or MariaDB 10.3 or greater, and HTTPS support. These numbers can change, so check the current WordPress requirements page and your host’s supported versions before treating them as a permanent checklist.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- PHP: Confirm the account is running a supported PHP version, not merely that the host offers one. A domain can inherit an older PHP setting from the account, directory, or a different virtual host.
- Database engine: Verify that the account has MySQL or MariaDB available at a supported version and that the database server is online.
- HTTPS: Confirm that the host can serve the domain over HTTPS and that the domain is covered by a valid certificate. A domain that is pointed elsewhere or has no certificate is not ready for an HTTPS WordPress address.
- Account limits: Check database quotas, disk space, and any hosting limits that could stop a database or file operation part-way through.
Changing PHP or creating a database before you know the selected domain and path can make diagnosis harder. Keep the original installer settings and error record while you verify these prerequisites.
Fix “error establishing a database connection” and related database failures
A database error means WordPress cannot establish a usable connection, not necessarily that WordPress files are missing. The installation guide recommends checking the database name, user, password, and host in wp-config.php, confirming that the user can access the database, and verifying that the database server is running. The common-errors guidance also identifies exhausted database quotas, host outages, and inadequate CREATE privileges as possible causes.
Check the four connection values
- Open the hosting file manager or SFTP connection and locate
wp-config.phpin the WordPress directory. If the installer did not create it, the installation may have stopped before configuration was written. - Compare the configured database name, database user, password, and database host with the values shown in the hosting panel. Many hosts require an account prefix in the name and user; omitting it creates a different, nonexistent account.
- Check for accidental spaces, quotation-mark changes, or a password that was reset after the installer ran. Never paste the database password into a support ticket.
- Use the control panel’s database screen to confirm that the named user is assigned to the named database and has the privileges WordPress needs. In cPanel or Plesk this generally means adding the user to the database and selecting the required privileges, but the labels differ by host.
Distinguish credentials from server or quota problems
If the values are correct, ask the host whether the database server is running and whether the account has reached a database or resource quota. A temporary host outage can produce the same front-end message as a wrong password. During installation, the control-panel account also needs permission to create the database and tables; an installer that lacks CREATE privileges may stop after creating only part of the configuration.
Do not point a new installation at an existing production database simply to make the error disappear. First identify the intended database and take a backup if any existing tables are present. A fresh database is safer for a genuinely new site.
Interpret PHP code, blank pages, and HTTP 500 errors
When the browser shows literal PHP tags
If you see text such as <?php or ?> in the browser, the web server is delivering PHP source instead of executing it. This is a server PHP configuration or handler problem, not a WordPress theme problem. Check which PHP version and handler the domain and directory use in the hosting panel, then ask the host to correct the mapping if you cannot change it yourself. Do not leave a site publicly serving source files: PHP source can expose database credentials and application logic.
When the result is a generic HTTP 500
A 500 response only says that the server failed while processing the request. On a brand-new installation, do not assume a plugin or theme caused it. If you have access to server logs, capture the timestamped entry for the failing URL. If you do not, give the host the URL, time, PHP version, and complete browser message and ask them to inspect the server error log and enabled PHP modules. The host may need to correct a PHP handler, module, memory limit, ownership setting, or another server-side condition that is invisible from WordPress.
Rank #3
Use Site Health to check filesystem permissions
WordPress can report whether its required directories are writable. In the dashboard, open Tools → Site Health → Info and expand the Filesystem Permissions section. The technical-information panels also show server and database details that help match the failing layer to the host’s configuration.
- If the required paths are reported writable, do not change permissions just because an installer stopped. Continue with database, routing, or PHP checks.
- If paths are not writable, correct ownership and permissions through the hosting panel or ask the host to do it. The correct values depend on the account’s user and group model; an arbitrary recursive
chmodcan expose files or still leave them owned by the wrong account. - Ask support to verify ownership of the WordPress directory, not only the numeric permission bits. A directory can appear permissive while PHP runs as a different user that cannot write to it.
Run Site Health after the host makes a change so you can confirm the result before attempting another update or installation.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Resolve 403 Forbidden responses, missing pages, and directory listings
403 Forbidden
The installation FAQ describes a 403 as an authorization failure: the server is refusing to let the requester view the directory or page with the supplied credentials. Recheck three things in order:
- Domain-to-document-root mapping: Make sure the domain is attached to the directory containing the WordPress files, not to a sibling or old directory.
- Directory and file access: Have the host verify ownership, permissions, and any account-level access rule for the document root.
- Security rules: Ask whether a host firewall, web-application rule, or directory restriction is blocking the request. Provide the exact URL and timestamp so the rule can be located in logs.
Do not disable every security feature as a first response. A targeted log check is safer and preserves protection for other sites on the account.
A directory listing instead of WordPress
A directory index usually means the web server is not configured to serve index.php by default, or the domain is mapped to a directory that does not contain the WordPress front controller. Confirm that index.php exists in the selected directory, that the URL maps there, and that the host’s directory-index setting includes PHP files. The WordPress installation guide identifies a missing default index configuration as a web-server issue.
A blank or apparently missing site
First open the exact installation path recorded in the first step. Then inspect the directory for WordPress files and check whether the installer created wp-config.php. If files exist in one directory but the domain serves another, fix the domain mapping rather than reinstalling. If the directory is empty, determine whether the installer failed before upload or placed files in a different path. A blank response combined with a 500 entry in the server log belongs in the PHP and server-log branch above.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check HTTPS and URL consistency
HTTPS support is one of the current WordPress hosting requirements. Confirm that the certificate covers the exact hostname you are opening and that the domain resolves to the account where WordPress was installed. Test both the address selected in the installer and its intended HTTPS form; a certificate for one hostname does not automatically cover another.
Do not edit WordPress URL values or force redirects until the domain points to the correct document root and the certificate works. Redirecting an incorrectly mapped domain can make a valid installation appear permanently unavailable and can complicate later testing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Retry safely after a partial installation
An interrupted run can leave a directory, database, or wp-config.php behind. Identify what exists before deciding whether to retry.
| What exists | Safer next action | What to avoid |
|---|---|---|
Files and wp-config.php, with a working database |
Open the recorded URL, inspect the server and database errors, and repair the failing layer. | Running a second installer over the same directory. |
| Files, but no usable database | Resolve database credentials, privileges, quota, or server status before creating a new configuration. | Deleting a database that might belong to another site. |
| A database with tables, but incomplete files | Back up the database, then complete the upload or restart only after confirming the intended directory. | Dropping tables to “start clean” without a backup. |
| Only a partial upload | Remove only the incomplete WordPress files after confirming the directory is not used by another site, then start a clean upload. | Deleting the account’s actual public_html folder. |
Learn WordPress’s manual-installation guidance advises deleting incomplete uploaded files and starting again, while explicitly warning not to delete the actual public_html folder. Treat that directory as the hosting account’s container unless the host has confirmed a different layout.
Use the manual installation route when automation is the failing layer
Manual installation is a fallback when the control-panel script is broken or cannot express the configuration you need; it does not bypass PHP, database, permission, domain, or HTTPS requirements.
- Obtain WordPress from the official WordPress distribution. Keep the archive intact until you have confirmed the destination directory.
- Create a database and a dedicated database user in the hosting control panel. Assign the user the privileges required to create and modify the WordPress tables, and record the database host, name, user, and password securely.
- Upload the files to the document root or the specific subdirectory that the domain serves. If an earlier upload was incomplete, remove only those incomplete files after checking that no other site uses the directory.
- Open the installation URL at the same domain and path. WordPress will ask for the database details and create
wp-config.phpif it can write to the directory. - Complete the site setup only after the database connection succeeds. If the manual screen fails with the same message, return to the database, PHP, permission, or routing branch instead of uploading a third copy.
Manual steps make each dependency visible, but they also increase the chance of a typo. Keep the recorded values and compare them character by character before saving.
Choose the least risky fix for your situation
| Likely failure layer | Access you have | First diagnostic | Risk to existing data | Most reversible remedy |
|---|---|---|---|---|
| Domain or path mapping | Hosting panel | Compare the domain’s document root with the install directory. | Low if you do not move files. | Correct the mapping and test the recorded URL. |
| PHP execution or HTTP 500 | Panel but no server logs | Check the account’s PHP version and request the matching log entry. | Low. | Ask the host to adjust the handler or module. |
| Database connection or privileges | Panel database tools | Verify host, name, user assignment, privileges, quota, and server status. | High if an existing database is altered. | Back up first; repair the intended user or create a separate database. |
| Filesystem ownership or writability | Site Health only | Read the Filesystem Permissions section. | Low until files are deleted. | Have the host correct ownership and permissions. |
| Incomplete upload | SFTP/FTP or file manager | List the target directory and identify which files are incomplete. | High if the directory hosts another site. | Back up, remove only the partial upload, and restart in the confirmed directory. |
| Unknown server-side cause | No logs or shell access | Package the error, path, time, versions, and Site Health results. | Usually low while diagnosing. | Escalate to managed hosting support before deleting anything. |
What to include in a hosting-support ticket
Support can investigate server logs, quotas, PHP modules, ownership, and control-panel installer logs that are unavailable in a normal dashboard. Send one concise ticket containing:
- the complete error text and the timestamp with time zone;
- the domain or subdomain, protocol, and exact installation directory;
- the PHP version selected for the account;
- the database host, database name, and database user (never the password);
- whether HTTPS loads successfully for the hostname;
- the Site Health Filesystem Permissions result;
- what files,
wp-config.php, and database objects already exist; and - the checks you want performed: database quota and server status, PHP modules and handler, filesystem ownership, domain routing, and the control-panel installer log.
Ask the host to state which layer failed and what they changed. That answer is more useful than a generic request to “reinstall WordPress,” especially when an existing database or site may be present.
Prevent the next failed installation
- Verify the current WordPress requirements and the host’s PHP, database, and HTTPS support before opening the installer.
- Decide the final domain and directory first, then use that same path in the installer and in your browser.
- Create a dedicated database and user for a new site and keep the credentials in a secure password manager.
- Confirm the domain’s document root and certificate before enabling redirects.
- Take a backup before removing partial files or touching any database that is not demonstrably empty.
- Use Site Health to confirm writability after permission changes instead of applying blanket permission commands.
Bottom line
A failed one-click installation is usually a failed prerequisite or mapping, not a mysterious WordPress defect. Capture the exact target and error, test domain routing, PHP execution, database credentials and privileges, filesystem ownership, and HTTPS in that order. Only after those checks should you remove a confirmed partial upload, switch to a manual installation, or ask the host to inspect logs and quotas.
Quick 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.
