It works. Allegedly.

This is a default-ish test page used to confirm that your HTTP daemon is awake, caffeinated, and at least minimally cooperative.

Congratulations!

Your web server is running. That’s the good news. The other news is: now it’s your problem. 😐

HTTP status

200 OK (for now)

Probability of “works on my machine”

93.7%

Time since last config change

≈ unknown

Easter egg: Diagnostics (press gently)

Loading…

Tip: If you are seeing this in production, you have discovered either a misconfiguration or a very confident administrator.

If you are a normal user of this website

You probably expected content. Instead, you got a default page. Please notify the site administrator and describe what you were trying to do. Bonus points if you include the phrase “works on localhost”.

Next steps (choose your own adventure)

Replace this file with your actual site content.
Check your document root (often /var/www/html).
Review config (Debian/Ubuntu: /etc/apache2, RHEL-like: /etc/httpd).
Read logs before they read you: /var/log/apache2 or /var/log/httpd.

Nerd corner: The sacred incantations

# Debian/Ubuntu style:
sudo a2ensite your-site.conf
sudo a2enmod rewrite headers ssl
sudo systemctl reload apache2

# RHEL/CentOS/Fedora style:
sudo vi /etc/httpd/conf.d/your-site.conf
sudo systemctl reload httpd