How to Fix a Joomla Installation That Will Not Start

If a new Joomla installation will not start at all, troubleshoot what the web server is serving before changing database settings. The installer should appear when the Joomla Full Package is correctly extracted into the document root and the server can execute its PHP entry point.

Determine what “will not start” means

Browse to the exact URL where Joomla should be installed and note the result: DNS failure, certificate warning, hosting placeholder, directory listing, 403, 404, 500, blank page, raw PHP source, download prompt, or another application. Each result points to a different layer. A database problem generally occurs after Joomla's installer has loaded; if no installer page appears, begin with DNS, document root, files, and PHP.

1. Verify DNS and the final hostname

Confirm the domain or subdomain resolves to the intended hosting service. If the browser cannot reach the server, Joomla cannot start regardless of what is in the web directory. For a new hostname, allow for DNS propagation and make sure the host has also configured the domain in the web server.

2. Verify the domain's document root

Use the hosting panel or web-server configuration to identify the directory served by the URL. Joomla's index.php should be directly inside that directory. A common mistake is extracting the package one level too deep, such as:

/public_html/Joomla_6.x.x-Stable-Full_Package/index.php

when the domain actually serves /public_html/. Move the package contents to the intended document root or deliberately change the domain's document root; do not rely on an accidental extra path.

3. Confirm you used a complete installation package

For a new site, use the current stable Joomla Full Package from the official Joomla Downloads site. Verify that core directories such as administrator, components, libraries, and installation exist. If you uploaded thousands of extracted files over FTP/SFTP, inspect the transfer log for failed files. Re-upload from a clean package if completeness is uncertain.

4. Confirm the web server executes PHP

If the server displays PHP source code or downloads index.php, stop: PHP is not being executed correctly for that site. That is a hosting/web-server configuration problem and can expose sensitive application code. Correct the PHP handler before continuing.

If you receive HTTP 500 or a blank page, inspect the PHP and web-server error logs. Check that the PHP version and required modules meet the Joomla branch's technical requirements. Joomla 6.x currently requires PHP 8.3.0 or later in the supported range and required modules including json, simplexml, dom, zlib, gd, and a supported database driver.

5. Interpret common HTTP results

  • 404: the hostname/path is reaching a server, but not the Joomla entry point; check document root and file placement.
  • 403: check directory/file ownership, web-server access rules, index-file configuration, and any hosting security rule.
  • 500: read the server/PHP error log; do not guess from the generic browser page.
  • Directory listing: verify index.php exists and the server is configured to use it as an index file.
  • Old site or placeholder: the domain is probably serving a different document root or cached/proxy destination.

6. Check ownership and permissions

The web server must be able to read Joomla's files and traverse its directories. Correct ownership to the hosting provider's expected account/web-server model. Avoid blanket 777 permissions. If files uploaded through one account are unreadable by the PHP/web-server process, ask the host to correct ownership rather than weakening permissions globally.

7. Check for a leftover configuration file or mixed site

A new Full Package includes the installation application. If the directory contains a configuration.php from an old site, or files from another CMS, you may not get the clean installation flow you expect. Back up anything important, then use a clean target directory for a genuinely new installation.

8. Only troubleshoot the database after the installer opens

Once the Joomla installation interface appears and reaches Setup Database Connection, database host/name/user/password and privileges become relevant. Until then, changing database credentials cannot fix DNS, document-root, missing-file, or PHP execution failures.

Fastest recovery path

  1. Confirm the hostname reaches the correct server.
  2. Confirm the correct document root.
  3. Confirm Joomla index.php and installation exist at that level.
  4. Read the HTTP status and PHP/web-server error log.
  5. Correct PHP handler/version/modules or ownership problems.
  6. Replace incomplete files with a clean official Full Package.
  7. Reload the site; when Joomla's installer appears, continue with normal setup.

This order prevents a database-focused troubleshooting detour when the installer has not yet reached the database stage.

Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket