Your website is down, a client cannot submit a form, or you are seeing a blank page. The urgent question is whether the problem is with your hosting company or with WordPress itself. You can often narrow it down in a few minutes without changing anything.
Start with the fastest reversible checks: confirm what visitors see, test the site from another connection, and check your host’s status page. Do not begin by deactivating plugins, editing files, or changing database settings. Those actions can make a simple outage harder to diagnose.
This guide walks through a practical triage process, explains ping versus an HTTP test, and covers hosting health, database credentials, and the basics of wp-config.php. Keep a written record of exact error messages and timestamps as you go.
First, Record What Is Happening
Before troubleshooting, write down the time and the exact symptom. “The site is broken” is difficult to investigate; “At 10:42 a.m., the homepage returned ‘Error establishing a database connection’ on two networks” is useful evidence.
- Record the date, time, and time zone. Copy the full error message, including any error code such as 500, 502, or 503. Note which pages fail: the homepage, the WordPress login page, or the entire domain. Check whether the issue happens on another device or network, such as a phone using mobile data. Ask whether anything changed recently: a WordPress update, plugin change, password reset, DNS change, or hosting account migration.
A private browser window can help rule out a stale login session or cached page. It does not prove the server is healthy, but it is a quick, low-risk check.
Rapid Outage Triage: Check These Things First
Open the site from a second connection
Try the site on your phone with Wi-Fi turned off, or ask someone outside your office to load it. If it works on mobile data but not your office network, the problem may involve local DNS, a firewall, or network caching rather than WordPress or the web host.
Check the hosting status page
Search your hosting provider’s official status page for incidents involving your region, data center, server, or platform. This is the quickest way to check hosting status page reports for a wider outage. Look for the incident’s start time, affected services, and latest update—not just a green overall indicator.
A status page may not identify an issue isolated to one server or account. If there is no incident listed, continue the checks rather than assuming your host is clear.
Test the homepage and WordPress login page
Load both https://example.com/ and https://example.com/wp-login.php, replacing the example domain with yours. Note whether they show the same result. A failed homepage with a working login page can point toward a theme, plugin, or page-specific issue. If both fail with a server error, hosting or a site-wide configuration problem becomes more likely.
Check domain and DNS basics
Make sure the domain has not expired and that its nameservers or DNS records were not recently changed. DNS changes can take time to appear consistently. If the domain points to an old or incorrect server, WordPress may be fine but visitors may be reaching the wrong destination.
Ping vs HTTP Test: What Each One Tells You
A ping test checks whether a hostname resolves to an address and whether that address responds to basic network traffic. It is not a complete website test. Many hosting providers and security services block ping requests, so a failed ping does not prove the server is down. A successful ping does not prove that the website or database is working either.
An HTTP test asks the web server for a page, much like a browser does. It can reveal a response code and sometimes the page’s error message. You can use a browser or a reputable online HTTP status checker. If you are comfortable with a command line, this command requests the response headers:
curl -I https://example.com/
You might see a status such as 200 (request succeeded), 301 or 302 (redirect), 403 (forbidden), 404 (not found), or a 5xx server response. Redirects are not necessarily errors; follow the destination and check what the browser ultimately displays.
Result What it may suggest Next check Ping fails, HTTP works Ping may be blocked; the website is reachable. Check the page in a browser and note its HTTP result. Ping works, HTTP fails The network address responds, but the web service or site may have a problem. Record the HTTP code and check hosting logs or provider status. HTTP returns a 5xx error Possible server capacity, web server, PHP, database, or application failure. Check hosting health, error logs, and recent changes. HTTP returns 200, but the page looks wrong The server delivered a page, but the content, theme, or browser-side assets may be failing. Compare another page and inspect recent WordPress changes.The combination of tests matters. A blocked ping by itself is weak evidence; a repeated HTTP 503, a matching provider incident, and failed control-panel access are much stronger signs of a hosting problem.
Server Error Signs That Point Toward Hosting
Server error signs do not automatically mean the hosting provider is at fault. WordPress can trigger server errors too. However, these patterns are worth reporting to your host:
- 502 Bad Gateway or 503 Service Unavailable: may indicate an overloaded or unavailable upstream service, maintenance, or exhausted server resources. 504 Gateway Timeout: a server took too long to complete a request. A slow plugin or database query can cause it, but so can an unhealthy server. Connection refused or repeated timeouts: the web service may not be accepting requests, or a network or firewall rule may be blocking access. Control panel, email, and multiple hosted sites failing together: points more strongly toward an account, server, network, or provider-wide issue. Sudden resource-limit messages: disk space, memory, CPU, or process limits may have been reached. Check the hosting dashboard for usage alerts.
If only one WordPress site is affected while other sites on the same account are working, the cause may be specific to that installation, its database, or its configuration. It is still worth asking the host to check the server logs for the affected domain.
When to Suspect WordPress or Its Configuration
A site-specific failure after a known WordPress change is a useful clue. For example, if the site failed immediately after a plugin update while the hosting dashboard and other sites remain available, investigate the update before assuming a general outage.
- The WordPress login page works, but one page or the front end fails. A fatal error names a particular plugin, theme, or PHP file. The problem began directly after an update or code change. The server returns a WordPress-generated message, such as “Error establishing a database connection.” Only one installation or domain on the hosting account is affected.
These are clues, not proof. A database service outage can produce a WordPress database error, and a host-level PHP or storage issue can break just one installation. Use the error and provider logs to confirm the direction.
Database Credential Checks: Look Before You Edit
WordPress uses database details in wp-config.php to connect to its database. A credential mismatch can cause “Error establishing a database connection,” but the same message can also appear if the database server is unavailable or overloaded.
First, check whether anyone recently changed the database password, database name, database user, or hosting account configuration. In the hosting control panel, confirm that the database and user still exist and that the user is assigned to the correct database with the required permissions. Do not post credentials in a support ticket or send them in plain email.
Only compare the settings if you have authorized access and know where the current credentials were recorded. If you need to make a change, make a secure copy of the existing file first. Never replace credentials with guesses, and avoid sharing the full contents of wp-config.php, which may include secrets.
WordPress wp-config.php Basics
The wp-config.php file sits in the WordPress installation’s main directory. It contains important settings, including database connection details. The common database entries are:
- DB_NAME — the database name. DB_USER — the database username. DB_PASSWORD — the database user’s password. DB_HOST — the database server address, which is often—but not always—localhost.
Do not assume that DB_HOST is localhost. Some providers use a separate database hostname. Use the value given by the host or shown in the site’s existing configuration. Also, do not paste credentials into public forums or screenshots.
If You Need to Change the File
Make a backup before editing. Use the hosting file manager or secure file transfer, and change only the value you have confirmed is wrong. Save the file and test the site once. If the change causes a new problem, restore the original file immediately.
What changed How to roll back A confirmed database setting in wp-config.php Restore the saved original file or put back the previous value. A plugin or theme setting Reverse that exact setting or restore the relevant backup. A DNS record Restore the recorded previous value, then allow for DNS caching.Do not turn on public error display as a quick diagnostic. Detailed errors can expose file paths or other sensitive information. If logging is needed, ask your developer or host to use a protected log and disable public display.
Make One Change at a Time
During an outage, random plugin installs or multiple simultaneous edits create extra uncertainty. Before any change, confirm that a current backup exists—especially before editing files, changing database settings, or altering DNS. If you cannot confirm a backup, pause and ask the host how to create or restore one safely.
For every change, write down what changed, the exact time, and how to roll back. Make one change, test the same URLs again, and compare the result. This keeps your investigation reversible and gives support teams a reliable timeline.
What to Send Your Hosting Provider
If the evidence suggests a server-side issue, provide a specific report rather than only saying “the site is down.” Use this script:
Subject: Website availability check for fantasticlawyers.com example.com — [date and time, time zone]
Message: “At [time and time zone], https://example.com/ returned [exact error or HTTP code]. /wp-login.php returned [result]. I tested from [connection or location] and [a second connection, if available]. The provider status page shows [incident or no incident]. The hosting control panel is [available/unavailable]. Please check the web server, PHP and database service for this domain, resource limits, and the relevant error logs around [time]. I have not changed files or database credentials. Please advise before making changes, and confirm whether a backup is available.”
Include screenshots if useful, but remove passwords, database details, and other secrets. Ask for the relevant log entry and whether the issue affects your account, server, or a broader service.
A Practical Decision Guide
- Provider incident or several account services fail: likely hosting or platform trouble. Record evidence and request a server-side check. One site fails with a specific WordPress or plugin error: investigate that installation, but ask the host to confirm PHP and database health. Ping fails but HTTP loads: the site is reachable; ping may simply be blocked. HTTP times out or returns repeated 5xx responses: capture the codes and timestamps, then check status and server logs. Database error after a credential change: verify the database and user in the control panel before editing wp-config.php.
You do not need to identify the exact root cause before contacting support. Your goal is to collect clean evidence, avoid risky changes, and determine whether the failure is isolated to WordPress or part of a broader hosting problem. Fast checks, exact notes, and reversible steps usually get you to the right fix sooner—and make it much easier to explain what happened if the site is for a law firm or another business where downtime matters.
