Your website is down and visitors can’t reach it. This guide walks you through a series of checks to find the cause and get your site back online. Most issues are resolved in the first few steps, so start at the top and work your way down.
Step 1: Check for a Server Outage
Before changing any settings, find out if the problem is on your end or ours.
- Visit the Ecenica Status Page to check for scheduled maintenance or active outages.
- Go to Down For Everyone Or Just Me and enter your domain. This tells you if your site is down for everyone or just your connection.
If there’s a known outage, there’s nothing to fix on your end — wait for our team to resolve it.
Step 2: Check Your Account and Domain
An unpaid invoice or expired domain takes your site offline immediately.
- Log in to your Ecenica Dashboard.
- Click Invoices to check your hosting plan is paid and active.
- Click Domains to confirm your domain registration hasn’t expired.
If your domain has expired, renew it through the Domains section. If you have an unpaid invoice, pay it to restore your hosting.
Step 3: Fix WordPress Issues
Most downtime is caused by WordPress plugins or themes, not server problems. If your site runs on WordPress, try these fixes.
Deactivate All Plugins
A broken plugin can crash your entire site. If you can’t log in to WordPress admin:
- Log in to cPanel and open File Manager.
- Go to your website folder, usually
/public_html/wp-content/. - Rename the
pluginsfolder toplugins_old. This disables all plugins without deleting them. - If your site loads, rename the folder back to
plugins. Then go inside it and rename each plugin folder one by one to find the broken one. - See Fix the “There has been a critical error on this website” error for more help.
Turn On Debug Mode
A blank white screen (the “White Screen of Death”) hides the error. Debug mode reveals it:
- Open cPanel File Manager and find
wp-config.phpin your site’s root folder. - Edit the file and look for this line:
define( 'WP_DEBUG', false );
- Change
falsetotrueand save. - Refresh your site. The error message and file path now show on screen.
Switch to a Default Theme
If plugins aren’t the problem, your theme might be broken:
- In cPanel File Manager, open
/public_html/wp-content/themes/. - Rename your active theme’s folder (for example,
mythemetomytheme_old). - WordPress automatically switches to a default theme like Twenty Twenty-Four. Your site loads if the theme was the issue.
Step 4: Check Server and SSL Errors
If your site isn’t a WordPress problem, the error message tells you what’s wrong.
“Your connection is not private” or “SEC_ERROR_REVOKED_CERTIFICATE”
Your SSL certificate has expired or wasn’t issued properly. SSL is the security layer that makes your site show `https://` and a padlock icon.
- Log in to cPanel and open SSL/TLS Status.
- Check if your domain has a valid certificate.
- If it’s expired or missing, click Run AutoSSL. This issues a free Let’s Encrypt certificate for your domain.
“500 Internal Server Error”
A server configuration problem, usually a broken .htaccess file or wrong PHP version.
- Log in to cPanel and open Select PHP Version.
- Try switching to a different PHP version. See How to change your PHP version on cPanel hosting for steps.
“ERR_NAME_NOT_RESOLVED” or “Site Can’t Be Reached”
Your browser can’t find the server. This happens after changing nameservers or DNS records.
DNS changes take up to 24 hours to spread across the internet. Read Connecting a domain to Ecenica using DNS pointing and wait for propagation to complete.
Step 5: Restore From Backup
If your site broke right after an update, roll it back to when it worked.
- Log in to cPanel.
- Scroll to the Files section and click JetBackup 5.
- Pick a backup from a date when your site was working.
- See How to restore your website from a backup using JetBackup for a full walkthrough.
Step 6: Contact Support
If you’ve tried everything above and your site is still down, open a support ticket. Include:
- Your domain name
- What you’ve tried so far
- Any error messages you’re seeing
This helps our team resolve your issue faster.