LiveChat 
Support 
Apache Is Functioning Normally: What the Default Page Means and How to Fix It
You installed a web server, pointed your browser at the IP address or domain, and instead of your website you got a plain page reading “Apache is functioning normally.” Nothing is broken, but nothing is *yours* either. This default placeholder is one of the most common sights for anyone setting up a new server, and it almost always points to a configuration gap rather than a fault.
This guide explains exactly what the message means, why it appears, and how to replace it with your actual site content. We will cover DocumentRoot configuration, virtual hosts, DNS pointing, and the precise commands to verify Apache’s status on both Ubuntu and CentOS-style systems.
Key Takeaways
• The “Apache is functioning normally” page means Apache is installed and running correctly but has no real site content to serve yet.
• It is a default landing page, served because no virtual host or DocumentRoot is pointing to your website’s files.
• Fix it by configuring a virtual host, setting the correct DocumentRoot, deploying your site files, and confirming DNS points to the server.
• Service and package names differ: `apache2` on Ubuntu/Debian, `httpd` on CentOS/RHEL/Rocky/AlmaLinux.
• The page is a good sign — it confirms the web server layer works before your application is even deployed.
What does “Apache is functioning normally” actually mean?
The phrase is a status confirmation, not an error. When the Apache HTTP Server is freshly installed, the package places a default landing page in the server’s default web root. Until you tell Apache where your real website lives, it falls back to serving this placeholder.
In other words, three things are simultaneously true when you see this page:
- Apache is installed. The binary exists and the package configured itself.
- Apache is running. The service started and is listening, usually on port 80.
- No site content is configured. There is no custom DocumentRoot or virtual host directing requests to your files, so the default response wins.
Different distributions ship slightly different placeholder text. Debian and Ubuntu show an “Apache2 Ubuntu Default Page,” while some hosting panels and minimal builds show a terse “It works!” or “Apache is functioning normally” message. The meaning is identical across all of them: the server layer is healthy, but it has nothing of yours to display.
The reason this page is reassuring rather than alarming is that it isolates the problem to a single layer. If you can see *any* Apache response — even the default one — then networking, firewall rules on port 80, the Apache service, and the operating system are all working. That narrows your remaining work to one task: telling Apache about your content. A blank screen or a connection timeout would mean a deeper problem; the default page means you are nearly done.
Why do users see the default Apache page?
There are a handful of common reasons this placeholder shows up instead of a real website. Identifying which one applies saves time.
- Fresh installation, no site deployed. The most frequent cause. You installed Apache to prepare the server but have not yet uploaded site files or created a virtual host.
- Wrong DocumentRoot. A virtual host exists, but its DocumentRoot points to an empty directory or the default web root rather than where your files actually live.
- Default virtual host taking priority. Apache serves the first matching (or default) virtual host. If your custom host is misconfigured or not enabled, the shipped default answers instead.
- Site files in the wrong location. Your `index.html` or application entry file sits in a directory Apache is not configured to read.
- DNS not pointed correctly. The domain still resolves to a different server, or you are testing by IP where only the default host responds.
- Configuration not reloaded. You edited the config but did not reload Apache, so the old behavior persists.
How do you check whether Apache is actually running?
Before changing anything, confirm the service status. The exact command depends on your distribution’s service name.
| Task | Ubuntu / Debian | CentOS / RHEL / Rocky |
|---|---|---|
| Service / package name | `apache2` | `httpd` |
| Check status | `sudo systemctl status apache2` | `sudo systemctl status httpd` |
| Start the service | `sudo systemctl start apache2` | `sudo systemctl start httpd` |
| Enable on boot | `sudo systemctl enable apache2` | `sudo systemctl enable httpd` |
| Reload config | `sudo systemctl reload apache2` | `sudo systemctl reload httpd` |
| Test config syntax | `sudo apache2ctl configtest` | `sudo apachectl configtest` |
| Show loaded vhosts | `sudo apache2ctl -S` | `sudo apachectl -S` |
A healthy status output shows the service as `active (running)`. The `configtest` command should return `Syntax OK` before you reload. The `-S` flag is especially useful — it prints every virtual host Apache has loaded and which one answers for a given name and port, which quickly reveals when the default host is intercepting your traffic.
This is the core distinction many newcomers stumble on: Ubuntu and Debian call the service `apache2`, while CentOS, RHEL, Rocky Linux, and AlmaLinux call it `httpd`. The software is the same Apache HTTP Server; only the packaging convention differs. Using the wrong name simply returns a “unit not found” message — not a sign that Apache is missing.
How do you replace the default page with your site?
Once you have confirmed Apache is running, work through this checklist to point it at your real content.
- [ ] Deploy your site files. Upload your website (`index.html`, application files, or framework build output) to a dedicated directory such as `/var/www/yoursite`.
- [ ] Set the correct DocumentRoot. In your virtual host file, set `DocumentRoot` to the directory holding your files.
- [ ] Create or edit a virtual host. Define a `
` block specifying `ServerName`, `ServerAlias`, and the `DocumentRoot`. - [ ] Enable the virtual host (Debian/Ubuntu uses `a2ensite yoursite.conf`; CentOS-style systems load `.conf` files from the config directory automatically).
- [ ] Test the configuration with `apachectl configtest` and confirm `Syntax OK`.
- [ ] Reload Apache so the new configuration takes effect.
- [ ] Verify DNS points your domain’s A record to the server’s public IP.
- [ ] Check directory permissions so Apache’s user can read the files.
Configuring DocumentRoot and a virtual host
A minimal virtual host that replaces the default page looks like this:
“`apache
ErrorLog ${APACHE_LOG_DIR}/yoursite-error.log CustomLog ${APACHE_LOG_DIR}/yoursite-access.log combined “`
The `DocumentRoot` tells Apache the folder to serve. The `ServerName` and `ServerAlias` tell it which incoming hostnames this block should answer. Once you enable the site, test the config, and reload Apache, requests for your domain will be served from your files instead of the default page.
Making sure DNS points to the right place
Even a perfect virtual host shows the default page if the domain does not resolve to your server. Confirm the domain’s A record points to the server’s public IP address, and remember that DNS changes can take time to propagate. While waiting, you can test locally by editing your machine’s hosts file to map the domain to the server IP, which lets you confirm the virtual host works before DNS is live. For a deeper walkthrough, see .
Checking permissions and the right directory
If Apache cannot read your files, it may still fall back to default behavior or return a permissions error. Make sure the DocumentRoot directory and its files are readable by Apache’s runtime user and that your site’s entry file (commonly `index.html` or `index.php`) sits at the top of that directory. A misplaced `index` file is a surprisingly frequent cause of an unexpected default or directory-listing page. See .
Want Apache configured correctly without the manual setup?
Setting up DocumentRoot, virtual hosts, DNS, and permissions by hand is entirely doable — but it is also exactly the kind of repetitive groundwork that delays getting your site live.
DarazHost managed hosting ships with the web server stack — Apache or high-performance LiteSpeed — already correctly configured out of the box. Document roots, virtual hosts, and permissions are handled for you, so you deploy your files and your site appears, with no placeholder page to troubleshoot.
For teams that want full control, DarazHost VPS plans provide root access so you can build custom Apache configurations, run multiple virtual hosts, and tune the server exactly to your application’s needs. Whichever path you choose, 24/7 support is available to help with virtual host configuration, DNS pointing, and any server-level question — so a default page never becomes a blocker. Explore or to get started.
How do you confirm the fix worked?
After reloading Apache, request your domain in a fresh browser tab or use a command-line tool to fetch the page. You should see your own content instead of the placeholder. If the default page persists:
- Run `apachectl -S` to confirm your virtual host is loaded and answering for your hostname.
- Re-check the DocumentRoot path for typos.
- Clear your browser cache or test in a private window.
- Confirm DNS has propagated and resolves to the correct IP.
Working methodically through the status checks, configuration, and DNS verification almost always resolves the issue, because the default page tells you the hardest part — a running web server — is already done.
Frequently Asked Questions
Is “Apache is functioning normally” an error? No. It is a status message confirming Apache is installed and running. It appears only because no website content or virtual host has been configured to serve in its place, so Apache falls back to its default page.
Why do I see the default page instead of my website? The most common reasons are that no site files have been deployed, the DocumentRoot points to the wrong directory, the virtual host is not enabled, or DNS for your domain does not yet resolve to the server. Configuring a correct virtual host and confirming DNS resolves the issue.
What is the difference between apache2 and httpd? They are the same Apache HTTP Server software under different package and service names. Debian and Ubuntu use `apache2`; CentOS, RHEL, Rocky Linux, and AlmaLinux use `httpd`. Commands like `systemctl status` must reference the correct name for your distribution.
How do I check if Apache is running? Use `sudo systemctl status apache2` on Ubuntu/Debian or `sudo systemctl status httpd` on CentOS-family systems. A status of `active (running)` confirms the service is up. You can also run `apachectl configtest` to validate your configuration syntax.
Do I need to restart Apache after editing the configuration? Yes. Configuration changes do not take effect until you reload or restart the service. Run `apachectl configtest` first to confirm `Syntax OK`, then reload with `systemctl reload apache2` (or `httpd`) to apply changes without dropping active connections.
