Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOn WordPress Multisite, this message usually means WordPress cannot find a registered site whose domain-and-path pair matches the URL you requested. The registration can be missing or incorrect, but DNS and web-server routing must also send that hostname to the Multisite installation. On a single-site WordPress install, the same wording usually points instead to the wrong virtual host, document root, URL, or server.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Start with the least invasive checks: confirm the installation type, inspect Network Admin → Sites, verify DNS and the server alias, and only then investigate database tables or restore records. Back up the database and files before changing network settings or database values.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
WordPress For Dummies (For Dummies (Computer/Tech)) | $16.59 | Buy on Amazon |
| 2 |
|
WordPress All-in-One For Dummies | $25.40 | Buy on Amazon |
| 3 |
|
Wordpress for Dummies | $26.94 | Buy on Amazon |
| 4 |
|
WordPress Web Design For Dummies | $16.48 | Buy on Amazon |
| 5 |
|
WordPress Web Design For Dummies | $29.30 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What the “site does not exist” message means
The browser-facing Multisite error
WordPress Multisite keeps a registry of sites identified by a hostname and a path. When a request arrives, WordPress looks up that pair before loading the site. If no matching record exists, core follows its ms_site_not_found path and may redirect or stop according to the network configuration. The visible result is often a page saying that the site does not exist.
This is why a site can be present on the server yet appear missing in a browser: the URL may not match the domain or path stored for that site, or the request may never reach the correct WordPress installation.
#1 Best Overall
Why a new subdomain can fail immediately
A newly created subdomain needs both a site record and working hostname routing. WordPress core describes this timing explicitly: “During activation of a new subdomain, the requested site does not yet exist.” If you test the address before the site record is created or before DNS and the web server are ready, the error is expected rather than evidence of damaged content.
Administrative “site does not exist” errors
The same wording is also used by administrative functions. wp_delete_site() and wp_update_site() return a site_not_exist error when the requested site ID cannot be found. Network Administration can likewise report “The requested site does not exist” when it cannot retrieve a site’s details. These messages concern a missing site object or invalid ID, not necessarily DNS.
Before changing anything: make a safe diagnostic copy
Network settings and site records affect every site in a Multisite network. Create a verified database export and back up the WordPress files before editing domain, path, or database values. Record the current values and change one layer at a time so you can identify which change resolved the problem.
- Save the exact URL that fails, including scheme (
httporhttps), hostname, port if present, and path. - Record the network’s current domain, path, and whether it uses subdomains or subdirectories.
- Note the site’s current status in Network Admin, including whether it is archived, deleted, or inactive.
- Keep the original database and file backups separate from any copy you modify.
First determine whether this is Multisite
If it is a Multisite network
Use the Multisite checks in the rest of this guide. The critical question is whether the requested domain-and-path pair is registered and whether the request reaches that network.
If it is a single-site installation
The Multisite site registry is not involved. Check the hosting virtual host, the document root assigned to the domain, the WordPress site URL, and whether the request is reaching the intended WordPress installation. A domain pointed at a different server or an old document root can produce a similar browser result even though WordPress itself is installed correctly elsewhere.
Rank #2
Check the exact site record in Network Admin
- Sign in as a network administrator.
- Open Network Admin → Sites.
- Search for the exact hostname in the failing URL.
- Compare the stored path with the requested path, including leading or trailing slashes and any subdirectory segment.
- Check whether the site is archived, deleted, or otherwise inactive.
- Confirm that the site belongs to this network rather than another Multisite installation.
Do not rely on a visually similar address. A one-character spelling difference, an unexpected www prefix, a different top-level domain, or a missing path segment creates a different domain/path pair. Check the scheme assumptions as well: an HTTPS request can fail if the hostname is routed differently from HTTP, even when the site record itself is correct.
When the site is absent
Create the site in Network Admin with the exact domain and path, or restore the correct site record from a verified backup. Do not create a second site with an almost identical hostname until you have checked spelling, path, and network identity. A duplicate can hide the original problem and make later cleanup harder.
Identify the network URL mode
Subdomain and subdirectory Multisite installations use different URL patterns. Diagnose the pattern before changing records or generated URLs.
| Network mode | Where the site identifier appears | What must be routed | Typical mismatch |
|---|---|---|---|
| Subdomain | In the hostname, such as a site-specific subdomain | Each hostname must resolve to the Multisite server and be accepted by its virtual host or server alias | A request uses a subdomain that is not registered, or DNS points that subdomain elsewhere |
| Subdirectory | In the URL path, such as /site-name/ |
The main network hostname must reach the installation, and the requested path must match the registered site | Links or requests use subdomains even though the network expects paths |
Hosting guidance treats subdomain and subdirectory networks as separate configurations. If the network was configured for subdirectories but links now use subdomains, correct the generated URLs and network settings or plan a deliberate migration; simply adding DNS records does not convert the installation.
Verify DNS before editing WordPress
What to check
The failing domain or subdomain must resolve to the server that hosts this Multisite installation. A correct site record cannot work when DNS sends the hostname to a different host, an old server, a parking service, or a proxy that does not forward the request to WordPress.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Check the DNS record for the exact hostname, not only the parent domain.
- Confirm that the record targets the current server or the intended front-end proxy.
- Check both the bare domain and any
wwwor site-specific subdomain used in the URL. - After a change, allow caches to expire according to the record’s TTL before judging the result.
Test the exact URL again after DNS has had time to update. If DNS resolves correctly but the browser still shows the error, continue to the web-server alias check rather than repeatedly changing the site record.
Verify the web-server virtual host or alias
The web server must accept the requested hostname and route it to the same document root as the Multisite installation. Configure the appropriate virtual host or server alias for the domain or subdomain, then reload the server according to your hosting environment. The hostname should reach WordPress before WordPress can perform its domain/path lookup.
“Either add each hostname as a site in the network (and point its DNS or server alias at this install), or switch PerfLocale to subdirectory or query URL mode, which keep this site’s hostname.”
The practical sequence is to register the hostname, point DNS or the server alias at this installation, and then test the URL. If your environment uses a control panel, its domain and alias settings must still map to the Multisite document root; a DNS-only change is insufficient when the web server rejects the Host header.
Fixes organized by the failed layer
| Failure layer | Evidence | Least-invasive fix | Risk level |
|---|---|---|---|
| Site registration | The hostname/path is absent or differs in Network Admin | Create the exact site or restore its verified record | Low when adding the correct record; higher if a duplicate is created |
| DNS | The hostname resolves to the wrong server or does not resolve | Correct the DNS record and wait for its TTL | Low, but propagation delays can obscure the result |
| Web-server routing | DNS is correct but the host is rejected or reaches another document root | Add or correct the virtual host/server alias | Moderate; a wrong alias can affect other domains |
| URL mode | Subdomain requests are used on a subdirectory network, or paths are used on a subdomain network | Correct generated URLs and network configuration, or migrate deliberately | Moderate to high; network-wide links can change |
| Database/site tables | The site is listed but its blog tables or database connection are missing | Check connectivity, prefixes, table existence, and restore from backup if needed | High; database edits can affect content and every site |
| Site object or ID | Administrative code returns site_not_exist |
Verify deletion, network ownership, and the referenced ID; restore if appropriate | Moderate to high, especially without a backup |
Cause-specific repair procedures
The site is not in the Multisite site list
Use Network Admin → Sites to create the site with the exact domain and path, or restore the known-good site record from a backup. Compare the network ID and original values before restoring. If you find a near-match, correct the original record rather than creating another entry.
Rank #4
DNS or server routing is wrong
- Correct the DNS record for the hostname.
- Configure the web server’s virtual host or server alias to accept that hostname.
- Point the alias at the Multisite document root.
- Wait for DNS caches to expire according to the record’s TTL.
- Test DNS resolution and then load the exact URL.
If the URL still fails, determine whether the request reaches the expected server. A response from another application or a generic host page confirms a routing problem rather than a missing WordPress site.
The URL pattern does not match the installation mode
Compare a working site URL with the failing one. On a subdomain network, the site identifier belongs in the hostname; on a subdirectory network, it belongs in the path. Correct the generated URLs and network settings to match the existing mode. If you need to change modes, treat it as a migration: back up first, update network configuration deliberately, and test every affected site rather than changing one link.
The site is listed, but blog tables or the database are missing
WordPress has a separate ms_not_installed() path for missing blog tables. Missing tables can indicate that the database server is not running, WordPress was not installed properly, or someone deleted the tables. This is distinct from a domain/path lookup failure.
Recommended Free Tools
- Check that the database server is reachable.
- Verify the database name, credentials, and table prefix used by this installation.
- Confirm that the tables for the affected site exist.
- Compare the schema with a known-good backup before attempting repair.
- Restore from a verified backup or involve the host/database administrator when tables are absent or damaged.
Do not create replacement tables blindly. Empty or incorrectly prefixed tables can make a site appear to load while hiding the original data.
The site was deleted or the ID is invalid
If an administrative operation returns site_not_exist, verify whether the site was deleted, moved to another network, or referenced with the wrong ID. Check Network Admin and your backups. Restore the original site object only after confirming its domain, path, network identity, and associated tables.
Best Value
Retest in a controlled order
- Open the exact failing URL in a private browser window to avoid cached redirects.
- Confirm DNS resolves the hostname to the intended server.
- Confirm the server accepts the hostname and uses the Multisite document root.
- Confirm the domain/path pair appears in Network Admin → Sites with the expected status.
- Check the network’s subdomain or subdirectory mode against the URL pattern.
- If the site is registered but still fails, inspect database connectivity and the affected site’s tables.
- Test the network’s main site and one other known-working site to detect a network-wide routing problem.
Change only one layer between tests. This preserves a clear cause-and-effect record and makes rollback possible.
Common mistakes that prolong the outage
- Creating a duplicate site: A near-identical hostname can mask a spelling or path error while leaving the original record unresolved.
- Changing database rows first: Database edits are harder to reverse and cannot fix DNS or a rejected virtual host.
- Ignoring the path: Multisite matches both domain and path; the correct hostname with the wrong path is still a different site.
- Assuming DNS proves WordPress is reachable: Resolution only identifies an address. The web server must also accept the hostname and route it to the right files.
- Mixing URL modes: Subdomain and subdirectory networks require different routing and generated links.
- Testing before propagation: DNS caches can continue serving old answers until the record’s TTL expires.
- Treating every message as the same failure: A browser lookup failure, a
site_not_existadministrative error, and missing blog tables are separate paths.
When to involve your host or database administrator
Escalate after you have recorded the URL, network mode, site status, DNS result, and server target. Ask the host to confirm the virtual host/server alias and document root, and to verify that the database server and required tables are available. Provide your backup timestamp and the original values you preserved. This gives the administrator enough context to repair routing or restore data without guessing.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A database repair is warranted only after registration, DNS, and server routing have been checked. If the site record exists but tables are missing, use a known-good backup or a qualified administrator; do not improvise table names or prefixes.
What a successful fix looks like
The final test should show all layers agreeing: the hostname resolves to the intended server, that server routes the hostname to the Multisite installation, the requested domain/path pair is registered and active in Network Admin, the URL pattern matches the network mode, and the affected site’s database tables are present. Once those conditions align, WordPress can complete its normal site lookup instead of taking the “site does not exist” path.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
