My domain only displays a blank or white page.
Possible causes may include:
Your page was poorly or incompletely uploaded:
Ensure that all files have been correctly transferred to the web space.
A PHP script on the page causes an error and the page configuration suppresses error display:
Check your domain’s PHP settings and ensure that “error_reporting” is enabled for the domain as well as “Display errors”. For more information, see the support article “How can I display PHP errors?”.
Then revisit the page and check if script errors are displayed. If the error appears, for example, after a WordPress update, incompatible components are often the cause of this problem. Relevant error messages can then help to specifically disable scripts, plugins, or themes via FTP.
Also check your CMS settings to ensure that error display is not disabled. The method varies depending on the software used.
If you cannot resolve the problem yourself, please contact hosting.fr support at support@hosting.fr for advice on the next steps.
Quick triage checklist: identify the most likely cause in 2 minutes
A blank (white) page usually results from one of two situations: the server cannot find the expected website files (for example, missing index.php or index.html, or files uploaded to the wrong directory), or PHP encountered a fatal error but error output is hidden. Before diving into server or application settings, confirm that your domain registration is active and correctly pointing to the intended hosting environment. Once that is verified, use the checklist below to quickly narrow it down before changing multiple settings at once.
Confirm you uploaded your website files to the correct document root (typically the html directory of the package) and that the folder actually contains an index.php or index.html.
If you recently uploaded or deployed, verify the upload completed successfully and did not stop mid-transfer.
If you run a CMS (especially WordPress), consider whether the blank page started right after an update. That strongly indicates a plugin/theme or PHP compatibility issue.
Try loading a known static file (for example, a simple test.html) in the same directory. If the static file loads but the site stays blank, the issue is likely PHP or application-level.
Enable error output temporarily to reveal a fatal error message, then disable error display again after diagnosis.
This fast triage reduces downtime by pointing you to the correct branch: files/paths versus PHP/application errors.
WordPress-specific recovery steps for a white screen
If the blank page appeared after a WordPress update (core, theme, or plugin), the most likely cause is an incompatibility or a fatal error triggered by a component. The goal is to restore access without guessing.
Follow this safe sequence:
Disable plugins first (least disruptive test): Connect via FTP and rename the plugins directory, for example from wp-content/plugins to wp-content/plugins.disabled. WordPress will treat plugins as deactivated. Reload the site.
If still blank, switch the theme: Rename the active theme folder inside wp-content/themes/ (or temporarily rename the full themes directory). WordPress will fall back to a default theme if available.
Check maintenance mode: If WordPress is stuck during an update, a .maintenance file may remain in the WordPress root. Remove it and reload.
Enable WordPress debugging (short-term): If you can edit wp-config.php, enable debugging to capture the fundamental error in logs rather than showing it publicly.
This approach isolates the cause systematically and is safer than reinstalling or deleting files immediately.
Check the server and PHP error logs to find the real error
Temporarily enabling “display errors” can reveal the cause, but it is not always practical or safe, especially on a live site. Error output may also remain suppressed by CMS settings or configuration. In many cases, the most reliable way to identify the root cause of a blank page is to read the relevant logs.
Use this workflow:
Reproduce the blank page in your browser (refresh the page that triggers the issue).
Immediately check the most recent entries in the PHP error log. A blank page is often caused by a fatal error, an uncaught exception, or a memory limit being exceeded.
Look for messages indicating the failing file path, plugin/theme name, or missing dependency. These clues tell you what to disable, update, or roll back.
If the logs show memory-related errors, the fix may involve adjusting PHP memory settings or reducing the number of resource-heavy plugins.
If no log entries appear, confirm that logging is enabled and that the log location is correct for your hosting environment.
Using logs keeps troubleshooting accurate and avoids exposing sensitive error details to the public.
Rollback and recovery: restore a working state safely
If the blank page started after a change (update, deployment, configuration edit), rolling back to a previously working state is often the fastest and safest resolution. The key is to restore the correct component: sometimes only files are affected, and other times the database or configuration must be restored as well.
Recommended rollback approach:
If the issue began after updating a plugin or theme, revert that component first (restore the previous version, disable it, or reinstall a known compatible version).
If you changed files manually, restore the last known good copy of the affected files (for example, the theme directory or a custom plugin).
If a core update was involved and compatibility is unclear, restore both the website files and (if needed) the database from a backup taken before the update.
After restoring, retest the site immediately and then reapply updates one at a time to identify the exact trigger.
A controlled rollback minimizes downtime and reduces the risk of making the situation worse by repeatedly changing trial parameters.