When should I use this default?
Use it to restore a missing default, confirm what shipped, or diff against your current NGINX config.
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# https://www.nginx.com/resources/wiki/start/
# https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
# https://wiki.debian.org/Nginx/DirectoryStructure
#
# In most cases, administrators will remove this file from sites-enabled/ and
# leave it as reference inside of sites-available where it will continue to be
# updated by the nginx packaging team.
#
# This file will automatically load configuration files provided by other
# applications, such as Drupal or Wordpress. These applications will be made
# available underneath a path with that package name, such as /drupal8.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##
# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_server;
# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}
# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}
curl https://exampleconfig.com/api/v1/config/original/9b030ecaaccde110ce6ed49d2571f5b7?hint=default
wget -O default https://exampleconfig.com/api/v1/config/original/9b030ecaaccde110ce6ed49d2571f5b7?hint=default
<prompt><role>DevOps agent</role><source url='https://exampleconfig.com/api/v1/config/original/9b030ecaaccde110ce6ed49d2571f5b7?hint=default' /><config><app>NGINX</app><os>Ubuntu 18.04 LTS (Bionic Beaver)</os><location>/etc/nginx/sites-available/default</location><lines>91</lines><md5>9b030ecaaccde110ce6ed49d2571f5b7</md5><sha256>e27fe6413217434eafda68bc95b2eacf38f8cb3d7b7f2011964ddb039ef35ebc</sha256></config></prompt>
Paste into Claude, ChatGPT, or any AI assistant.
sudo apk add nginx
sudo apt update && sudo apt install nginx
sudo yum install nginx
sudo apt update && sudo apt install nginx
When should I use this default?
Use it to restore a missing default, confirm what shipped, or diff against your current NGINX config.
How do I restore NGINX defaults?
Download the file, back up the current one in /etc/nginx/sites-available/default, replace it, then reload or restart NGINX.
Is default safe for production?
It is the vendor default for Ubuntu 18.04 LTS (Bionic Beaver). Treat it as a baseline and review security and performance settings before production use.
How does this differ from other OS versions?
Defaults vary by distro and version. This copy matches Ubuntu 18.04 LTS (Bionic Beaver).
Can I use this for NGINX troubleshooting?
Yes. Diff it against yours to find drift, then restore only the sections you need.