“Apache2 Ubuntu Default Page: It works!”
The web server itself is running and answering, but it has no site configured for your domain, so it serves its own test page. Your domain's DNS points at this server, yet the server doesn't know which website to show for it. Everything behind the page (your files, your database) may well be intact; the server just isn't connected to them.
Is your site showing it right now?
The free scan loads your page like a visitor and checks for this message, plus broken links, script errors and phone layout. It also walks your signup, booking or contact form, without sending anything.
Free, no signup. Usually done in about a minute.Why it happens
- A new server, a rebuild or a hosting move: Apache was installed, but your site's virtual host hasn't been set up or enabled yet
- DNS was pointed at a new server before the site was moved there
- The site's config file was disabled or lost during an upgrade (Ubuntu's package upgrade can reset sites-enabled)
- The virtual host doesn't list this hostname (the www or non-www version is missing from ServerName / ServerAlias), so Apache falls back to the default site
- The SSL (port 443) virtual host is missing while the plain http one exists, so https shows the default page
How to fix it
Confirm the DNS points where you think
Look up your domain's A record (a DNS lookup tool, or dig). If it points at a server you didn't expect, or at the new server before the migration finished, fix the record or finish the move.
Check the site's virtual host exists and is enabled
On the server: ls /etc/apache2/sites-available and sites-enabled. If your site's .conf is in available but not enabled, run a2ensite yoursite.conf, then systemctl reload apache2. If it isn't there at all, recreate it (your host's docs or your deploy notes have the template).
Make sure the hostname matches
Open the .conf and check ServerName and ServerAlias cover every name visitors use: example.com and www.example.com. A name not listed falls to the default site. Then reload Apache.
Check https separately
Load both http:// and https:// versions. If only https shows the default page, the <VirtualHost *:443> block is missing or disabled; certbot --apache or your SSL tool recreates it.
Disable the default page once the site is up
a2dissite 000-default.conf (and the default-ssl one) stops the test page showing for any name that reaches the server without a matching site.
Questions
Is my website gone?
Usually not. The default page means Apache doesn't know about your site, not that the files are deleted. Check /var/www and your database before assuming the worst.
I see "It works!" with no Ubuntu branding.
Same situation on another Linux (CentOS, Fedora, macOS Apache) or an older Apache. The fix is the same: the server has no virtual host for your domain.
Why did this appear after a system update?
Package upgrades can replace Apache's config directory layout or disable sites. Re-enable your site's .conf and reload. Keeping your site configs in version control makes this a one-minute fix next time.
Can Page Canary tell me if this comes back?
Yes. Page Canary checks your key pages every day for this message and others like it, confirms it on a second check, and emails you with the fix. One site is free.