A blank page usually means the website is generating an error before it can render any visible content. In a hosting environment, this is often caused by a PHP fatal error, a broken plugin or theme, an exhausted memory limit, a misconfigured .htaccess file, a permission issue, or a server-side problem in the application stack. If you are managing the site through a control panel such as Plesk, you can usually isolate the cause quickly by checking logs, disabling recent changes, and testing the site with a minimal configuration.
On websites hosted in Europe, the same troubleshooting approach applies whether the site runs on WordPress, Joomla, Drupal, Laravel, custom PHP, or another CMS. The key is to determine whether the blank page is caused by the application, the web server, or the hosting configuration.
Why a website shows a blank page
A blank page is often called a “white screen of death” in CMS communities, but the real meaning is simple: the page request completes without a visible error message. That does not mean the site is healthy. In many cases, PHP stops execution because of an error that is hidden from public display for security reasons.
Common causes include:
- PHP fatal errors or parse errors in theme, plugin, or custom code
- Memory limit reached during page generation
- Broken or incompatible extension after an update
- Incorrect file permissions or ownership
- Corrupted .htaccess or rewrite rules
- Incorrect PHP version or PHP handler settings
- Database connection issues
- Timeouts caused by heavy scripts or external API calls
- Server-side security rules blocking execution
If you see a blank page only on one route or only for logged-in users, the issue is likely application-specific. If the entire site is blank, the root cause is often broader and may involve PHP or the hosting configuration.
First checks before changing anything
Before making changes, confirm the exact behavior of the site. This helps avoid unnecessary edits and makes it easier to roll back if needed.
Check whether the site is fully blank or partially broken
Open the homepage, a subpage, and the admin area if available. Note whether:
- the page is completely empty
- the page loads without styles or images
- you see a spinner, timeout, or browser error
- the issue appears only on mobile or only in one browser
A fully blank page often points to server-side execution failure. A page with missing styles or scripts usually indicates asset loading or caching issues.
Clear browser and application cache
Cache can hide the real result of your latest changes. Clear:
- browser cache
- CMS cache or performance plugin cache
- server cache if your hosting plan includes it
- CDN cache, if used
If the site is behind a CDN or reverse proxy, test the origin directly when possible. This helps determine whether the blank page is caused by the hosting platform or an external caching layer.
Check recent changes
Think about what changed just before the problem started. Common triggers include:
- CMS core update
- plugin or extension update
- theme change
- custom code deployment
- new .htaccess rules
- PHP version change in the control panel
If the issue started after an update, that update is the first place to investigate.
How to identify the error in Plesk or a control panel
In managed hosting environments, the fastest way to diagnose a blank page is to inspect logs. In Plesk, open the domain’s logs section and review recent entries around the time the issue appeared. Look for PHP errors, fatal errors, memory exhaustion messages, or failed include paths.
What to look for in logs
Typical messages may include:
- PHP Fatal error
- Allowed memory size exhausted
- Uncaught Error or Exception
- Parse error
- Permission denied
- File not found for included files
- Maximum execution time exceeded
If your hosting platform offers separate error logs and access logs, check both. Access logs confirm which requests were made, while error logs show why the request failed.
Enable error display temporarily in a safe way
On a production site, you should not leave detailed errors visible to visitors. However, for troubleshooting, you may temporarily enable error logging or display in a protected environment or during a maintenance window. The safer option is usually to log errors rather than display them publicly.
In PHP-based sites, ensure that:
- error logging is enabled
- display_errors is disabled on live sites
- the log file path is writable
If your hosting control panel provides a toggle for PHP settings, use that instead of editing global server files unless necessary.
Most common fixes for a blank page
1. Disable plugins or extensions
For WordPress and other CMS platforms, a broken plugin is one of the most common causes of a blank page. If you cannot access the admin area, disable plugins manually through the file manager or FTP by renaming the plugins folder.
Recommended steps:
- Open the file manager or connect via FTP/SFTP.
- Rename the plugins directory to something like
plugins-disabled. - Reload the website.
- If the site works again, restore the folder name and reactivate plugins one by one.
This method also works for many extension-based applications. Reactivate each component gradually until the blank page returns.
2. Switch to a default theme
A broken theme can produce a blank page, especially after a customization or update. If your CMS allows it, switch to a default theme. If not, rename the current theme folder so the application falls back to a default template.
If the site loads after the switch, the problem is likely in the theme files, template overrides, or custom functions.
3. Increase the PHP memory limit
Many blank page errors happen when a script runs out of memory. This is common with large plugins, image-heavy pages, and complex page builders.
Depending on your hosting setup, you can increase the memory limit in one of these places:
- PHP settings in Plesk or your control panel
- php.ini
- .user.ini
- application configuration file
Typical values range from 128 MB to 256 MB or more, depending on the application. If the site still fails after increasing memory, the code may have a deeper issue.
4. Check the PHP version
An incompatible PHP version can result in a blank page if the application or one of its extensions does not support it. This happens frequently after a hosting upgrade or when a site is moved between environments.
To test this:
- Review the application’s supported PHP versions
- Check the active version in your control panel
- Switch to a compatible version and test again
If a newer PHP version causes the issue, update the application code and extensions before switching back. If an older version is insecure or unsupported, plan a proper compatibility upgrade.
5. Repair .htaccess or rewrite rules
A corrupted .htaccess file can break routing and sometimes produce an empty page. This is common when custom redirects, security rules, or cache rules are added incorrectly.
To test:
- Rename
.htaccessto.htaccess-backup. - Refresh the site.
- If the site works, regenerate the file from the CMS settings or restore only the necessary rules.
For Apache-based hosting, incorrect rewrite directives can prevent pages from rendering. If your platform uses Nginx as a reverse proxy or hybrid setup, review both layers.
6. Verify file permissions and ownership
Wrong permissions can stop the web server from reading or executing files. In some cases, this leads to a blank page without a clear browser error.
Check that:
- directories are typically set to 755
- files are typically set to 644
- configuration files are readable by the web server
- ownership matches the hosting account
Avoid using overly permissive settings such as 777 unless you are testing temporarily in a controlled environment. Secure permissions are important for both stability and security.
7. Look for database problems
If the application depends on a database and cannot connect to it, the result may be a blank page. This is especially common after migrations, credential changes, or database service interruptions.
Check the following:
- database host name
- database name
- username and password
- table prefix if applicable
- whether the database service is online
If the site uses a configuration file, confirm that the credentials match what is stored in the hosting control panel. Also verify that the database user has the required privileges.
8. Disable maintenance or cache layers
Some CMS platforms create maintenance-mode files or cache artifacts during updates. If an update was interrupted, the site may remain blank or appear incomplete.
Review:
- maintenance mode files
- temporary cache directories
- compiled templates
- object cache if enabled
Clearing these files can resolve a blank page after a failed deployment or incomplete update.
Advanced checks for managed hosting environments
Test the site with a minimal configuration
If standard fixes do not help, isolate the problem by reducing the environment to the minimum required to load the application. For example:
- disable all optional extensions
- switch to the simplest supported PHP version
- temporarily disable caching
- use the default template
- remove custom rewrite rules
This approach helps separate application issues from hosting configuration issues.
Check for external service failures
Some sites depend on payment gateways, API integrations, analytics scripts, or external authentication providers. If a custom script waits for a slow external service, it can time out and leave the page blank.
To investigate:
- review custom code that calls external APIs
- test the site with those calls disabled
- check whether the blank page appears only on pages using integrations
Review server resource usage
If your hosting plan includes resource statistics, check CPU, memory, I/O, and process limits. A blank page can occur when the application is terminated because it exceeds account limits.
Watch for:
- high CPU usage during page load
- memory limit hits
- too many concurrent processes
- slow database queries
In a managed hosting environment, repeated resource exhaustion may point to inefficient plugins, unoptimized queries, or a need to adjust the plan for the application’s size.
How to isolate the issue step by step
If you need a structured method, use this order:
- Confirm whether the blank page is global or limited to a specific page.
- Clear browser, CMS, server, and CDN cache.
- Review logs for fatal errors and memory messages.
- Temporarily disable plugins or extensions.
- Switch to a default theme or template.
- Verify PHP version and PHP memory limit.
- Rename or regenerate
.htaccess. - Check file permissions and ownership.
- Test database credentials and service availability.
- Review resource usage and recent deployment changes.
If the site returns after one step, the last change likely reveals the cause. Reintroduce settings gradually so you can identify the exact trigger.
When the issue is likely hosting-related
Most blank pages are caused by the application, but sometimes the hosting environment is the source of the problem. Consider the hosting layer if:
- multiple sites on the same account are affected
- the issue started after a PHP or server update
- logs show server-level errors rather than application errors
- resource limits are being hit regularly
- file access works inconsistently
In that situation, collect the error log entries, the exact time of the issue, the affected URL, and the recent changes you made. This makes support investigation faster and more accurate.
Prevention tips
To reduce the risk of blank pages in the future, follow a few practical habits:
- Keep CMS core, themes, and plugins updated, but test major updates first
- Use staging before deploying changes to production
- Monitor error logs regularly
- Keep backups before updates or code changes
- Use only supported PHP versions for your application
- Remove unused extensions and custom code
- Set correct permissions and avoid manual server edits without a backup
In managed hosting, a staging copy and regular backups are often the fastest way to recover from a bad update without extended downtime.
FAQ
Why does my website show a blank page instead of an error message?
Most production sites hide detailed PHP errors for security. The application may be failing silently, but the actual error is usually present in the logs.
Can a blank page be caused by a plugin update?
Yes. A plugin update may introduce incompatible code, require a newer PHP version, or conflict with another extension. Disabling plugins is one of the first steps you should try.
Why does the admin area work but the public site is blank?
This often points to a theme problem, template override, or front-end hook that affects public rendering only. Check the active theme and recent custom code.
Can low memory cause a blank page?
Yes. If PHP runs out of memory while generating the page, execution may stop before anything is shown. Increasing the memory limit often helps, but you should still find the underlying cause if the issue repeats.
Should I edit server files directly?
Only if you are comfortable doing so and have a backup. In many cases, Plesk or another control panel provides safer ways to adjust PHP settings, logs, and file management.
What if none of the fixes work?
Gather the error logs, note the affected URLs, list the last changes, and contact hosting support or your developer. A blank page usually becomes diagnosable once the exact error message is available.
Conclusion
A blank page is usually a sign of a hidden server-side error rather than a complete outage. In most hosting environments, the fastest path to a fix is to check logs, disable recent changes, verify PHP settings, and test the site with a minimal configuration. If you manage the site through Plesk or another control panel, use the tools available there to review errors, adjust PHP limits, and confirm file and database settings. With a systematic approach, you can usually identify the cause and restore the site without guesswork.