Browser: Welcome to nginx! If you see this page, the nginx web server is successfully installed and working
Requests are served by the default server block, not your site's block.
Welcome to nginx!Welcome to nginx! If you see this page, the nginx web server is successfully installed and workingnginx default page shows instead of my siteThank you for using nginx. Welcome to nginx!Apache2 Ubuntu Default Page: It works Meaning
Your server block isn't enabled (sites-enabled symlink missing), server_name doesn't match the Host header, the config wasn't reloaded, or the default site still takes default_server. Check nginx -T | grep server_name, enable the site, remove default, reload.
Common causes
- Site config not symlinked in
sites-enabled server_namedoesn't match the domain- Config not reloaded
- Default site marked
default_server - DNS pointing elsewhere/other host
⚡ Quick fix
sudo ln -s /etc/nginx/sites-available/app /etc/nginx/sites-enabled/- Match
server_namewith the Host header nginx -t && systemctl reload nginxand remove the default site
Detailed fix by platform
Linux
curl -sI -H "Host: example.com" http://127.0.0.1/ | head -3
How to diagnose
- Enabled — Symlink exists?
- Name — server_name matches?
- Reload — Done?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 499 Client Closed Request / client prematurely closed connection Nginx: [info] client prematurely closed connection while reading response header from upstream / access log status 499
- AH00112: DocumentRoot does not exist Apache: AH00112: Warning: DocumentRoot [/var/www/example.com/public_html] does not exist
- could not build the server_names_hash, you should increase server_names_hash_bucket_size Nginx: nginx: [emerg] could not build the server_names_hash, you should increase server_names_hash_bucket_size: 64
Most viewed in Nginx / Apache
- nginx: [emerg] unknown directive Nginx: nginx: [emerg] unknown directive "x" in /etc/nginx/sites-enabled/x:12 — configuration file test failed
- upstream timed out Nginx: upstream timed out (110: Connection timed out) while reading response header from upstream
- AH00558 Apache: AH00558: apache2: Could not reliably determine the server's fully qualified domain name
Other ways to find it
Where this error sits
Origin: Edge & web server. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026