How To Redirect www to Non-www with Nginx on CentOS 7

Updated on December 16, 2022
How To Redirect www to Non-www with Nginx on CentOS 7
Not using CentOS 7?Choose a different version or distribution.
CentOS 7


Many web developers need to allow their users to access their website or application via both the www subdomain and the root (non-www) domain. That is, users should have the same experience when visiting www.my-website.com and my-website.com. While there are many ways to set this up, the most SEO-friendly solution is to choose which domain you prefer—the subdomain or the root domain—and have the web server redirect users who visit the other one to the preferred domain.

There are many kinds of HTTP redirects, but in this scenario, it’s best to use a 301 redirect, which tells clients, “The website you have requested has permanently moved to another URL. Go there instead.” Once the browser receives the HTTP 301 response code from the server, it sends a second request to the new URL given by the server and the user is presented with the website, probably never noticing they were redirected.

Why not configure your web server to just serve the same website for requests to both domain names? That may seem easier, but it does not confer the SEO advantages of the 301 redirect. A permanent redirect tells search engine crawlers that there is one canonical location for your website, and this improves the search rankings of that one URL.

In this tutorial, you will configure a 301 redirect using Nginx on CentOS 7. If you are running Apache instead of Nginx, see this tutorial instead: How To Redirect www to Non-www with Apache on CentOS 7 .


To complete this tutorial, you first need:

  • Superuser privileges (a user in the wheel group) on the server that is running Nginx. If you don’t already have that set up, follow this tutorial: Initial Server Setup with CentOS 7.
  • Nginx installed and configured to serve your website. Follow this tutorial to do that: How to Install Nginx on CentOS 7.
  • A registered domain name. If you don’t have one yet, you can get a free one from Freenom. You may use whatever DNS provider you like (including your registrar) to host your domain’s records—just make sure to point your registrar to your provider’s nameservers. If you opt to use DigitalOcean DNS, this article from our documentation shows how to do that.

Let’s get started by configuring your DNS records.

Step 1 — Configuring DNS Records

First, you need to point both www.my-website.com and my-website.com to your server running Nginx. (The rest of the tutorial assumes your domain is my-website.com. Replace that with your own domain wherever you see it below.) You will do this by creating a DNS A record for each name that points to your Nginx server’s IP address.

Open your DNS provider’s web console. This tutorial uses DigitalOcean DNS.

In the Add a domain form, enter your registered domain name in the text field and click Add Domain. This will bring up the new domain’s page, where you can view, add, and delete records for the domain.

Under Create new record, type “@” in the HOSTNAME text field. This is a special character that indicates you are adding a record for the root domain name, a record for just plain my-website.com. In the WILL DIRECT TO text field, enter the public IPv4 address of your server, and click Create Record. (No need to change the TTL.)

For your second DNS record, you could use a CNAME record instead of an A record. A CNAME record is an alias that points to another name instead of an IP address. You could create a CNAME that directs www.my-website.com to my-website.com, and any HTTP request for the www subdomain would find its way to your server since you just created the A record for the root domain. But to keep things simple, just create another A record like the first one, entering “www” in the HOSTNAME field and the server’s public IP address in the WILL DIRECT TO field.

When you have created both records, it should look something like this:

Required A records

With the two records in place, web requests for both my-website.com and www.my-website.com should reach your Nginx server. Now let’s configure the server.

Step 2 — Configuring the Redirect in Nginx

As stated in the Prerequisites, you should already have your website configured in Nginx. It does not matter whether the site’s server block appears in the main /etc/nginx/nginx.conf file or in its own file. The important thing is that you have some server block configured with the server_name directive set to my-website.com and/or www.my-website.com. Whether your server_name contains one or both names, now is the time to decide which name you would like to be the one and only name to host the site.

Open the file that contains your website configuration (e.g., /etc/nginx/conf.d/my-website.com.conf) in vi or your favorite editor (yum install nano, if you prefer) and find the server_name directive:

  1. sudo vi /etc/nginx/conf.d/my-website.com.conf
server {
    . . .
    server_name my-website.com www.my-website.com
    . . .

If you want to redirect www.my-website.com to my-website.com, remove www.my-website.com from the server_name line, and save and exit the file. (If you want to redirect my-website.com to www.my-website.com, remove my-website.com instead.)

Then, create a new Nginx configuration file called /etc/nginx/conf.d/www.my-website.com.conf (or /etc/nginx/conf.d/my-website.com.conf, if that is the name you are redirecting). Name the file whatever you like, but as with all Nginx configuration files, the file name must end in .conf:

  1. sudo vi /etc/nginx/conf.d/www.my-website.com.conf

Add the following server block to the file, replacing my-website.com with your own domain name:

server {
    server_name www.my-website.com;
    return 301 $scheme://my-website.com$request_uri;

If you are redirecting my-website.com to the www subdomain instead, put my-website.com only in the server_name, and www.my-website.com in the URL on the next line.

Save and exit when you are finished.

This configures Nginx to send a 301 redirect back to any clients requesting www.my-website.com, and directs them to visit my-website.com instead. The redirect preserves the request URI, so that a request to http://www.my-website.com/login.php will be redirected to http://my-website.com/login.php.

Note: The server block above does not contain the listen directive. This is OK, because as mentioned in this tutorial, any server block without a listen directive will listen on (port 80 on all interfaces). But if your Nginx server is home to multiple IP addresses, or if your site listens on a port other than 80, you may need to add a listen directive to spell out the specific IP address and port. Use the same value for listen that your site’s main server block uses.

Before applying the changes, check that your Nginx configuration is error free:

  1. sudo nginx -t

Unless you made a syntax error (e.g., you forgot a semicolon), the configuration should be OK.

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful

Now restart Nginx to apply the new redirect rule:

  1. sudo systemctl restart nginx

Before visiting www.my-website.com in your browser, make a request using curl on either your server or your local machine (if curl is installed locally):

  1. curl -IL http://www.my-website.com

The -I flag tells curl to show only the headers from the server response. The -L flag tells curl to obey any redirects from the server by automatically making a second request, this time to the URL given in the Location header (just as a web browser would do). Since you have configured the 301 redirect, curl should make two requests, and you should see just the headers of the two responses:

HTTP/1.1 301 Moved Permanently Server: nginx/1.20.1 Date: Thu, 08 Dec 2022 19:24:44 GMT Content-Type: text/html Content-Length: 169 Connection: keep-alive Location: http://my-website.com HTTP/1.1 200 OK Server: nginx/1.20.1 Date: Thu, 08 Dec 2022 19:24:44 GMT Content-Type: text/html Content-Length: 57 Last-Modified: Thu, 01 Dec 2022 22:10:57 GMT Connection: keep-alive ETag: "63892671-39" Accept-Ranges: bytes

In the 301 (Moved Permanently) response to the original request to http://www.my-website.com, notice the last header: Location: http://my-website.com. The second response is from curl’s followup request to http://my-website.com, and if your website is healthy, the server should have responded with 200 (OK).

Finally, visit http://www.my-website.com in your web browser. Blink, and you’ll miss the redirect. Your website should appear as usual, but look again in your address bar and notice that the “www” is missing from the URL. Most users will never notice this, and so they will have the same experience as if they had requested http://my-website.com.


In this tutorial, you added two DNS records for your website and configured Nginx to redirect a secondary domain to your preferred domain. Now your website is reachable via both domains. Maybe it already was before you read this tutorial; perhaps you were serving it directly from both domain names. But with just four more lines of Nginx configuration, you have improved your website’s standing in the eyes of the search engines—and thereby exposed it to more users across the internet.

Want some further reading on how Nginx decides which server block will handle a given request? Check out this guide: Understanding Nginx Server and Location Block Selection Algorithms.

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about us

About the authors

Default avatar

Technical Writer at DigitalOcean

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

You don’t need a new server block for this task. Just use this if statement in your existing server block.

if ( $http_host ~* "www\.(.*)") {
                 rewrite ^ http://$1$request_uri permanent;

Also there should be a A Record pointing to your VM / IP, otherwise it will not resolve. Correct me if I am wrong

Also there should be a A Record pointing to your VM / IP, otherwise it will not resolve. Correct me if I am wrong

Also there should be a A Record pointing to your VM / IP, otherwise it will not resolve. Correct me if I am wrong

How can I modify the web server config of a DigitalOcean App, serving a Hugo website? I am able to generate a .htaccess file during ‘hugo build’, but seems like your web server is not Apache so it does not work.

Hey Mitchell,

After following your directions I had to delete the cname to add the extra aname in cloudflare (now all i have is two anames)

Continuing with your directions I found that there was not a redirect.conf in the conf.d folder so I created one and added only what you specified.

But my curl doesn’t look like your curl, is this a problem?

But when i do a curl, it instead look like this:

curl -I https://www.springfield-ohio-post.com
HTTP/1.1 200 OK
Date: Thu, 05 Dec 2019 17:30:54 GMT
Content-Type: text/html
Connection: keep-alive
Set-Cookie: __cfduid=d17929c0841719a36a96f95adcf97db8e1575567054; expires=Sat, 04-Jan-20 17:30:54 GMT; path=/; domain=.springfield-ohio-post.com; HttpOnly; Secure
Last-Modified: Thu, 05 Dec 2019 16:20:58 GMT
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: no-referrer
CF-Cache-Status: DYNAMIC
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Alt-Svc: h3-23=":443"; ma=86400
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 5407c0283a42e3ce-ATL

p.s. I see up there something about httponly (but I’m https)

I need to mention you need to add listen directive to server block without it Nginx will redirect it to default host

server {   listen [::]:80;
         server_name www.example.com ; 
         return 301 $scheme://example.com$request_uri; 

Everythings seems ok but when I access home I see 404 page. And If I use the .htaccess from ubuntu the example.com is redirected to example.com/index.php I don’t want these index.php

HTTP/1.1 301 Moved Permanently … Content-Type: text/html Content-Length: 193 Connection: keep-alive Location: http://www.example.com/

server { listen 80;

    root /var/www/html/example;
    index index.php index.html index.htm;

server_name example.com; return 301 $scheme://www.example.com$request_uri; # error_page 401 403 404 /404.html;

location / {
    try_files $uri $uri/ @proxy;

location @proxy {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

location ~ \.php$ {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

     location ~ /\. {
            deny all;

location ~* .(jpg|jpeg|png|gif|ico|css|js|swf)$ {
    expires 365d;


If you are making this server config redirect for a WordPress install make sure to log into the Dashboard -> Settings -> General before you restart nginx.

Modify the WordPress Address (URL) and Site Address (URL) to match the www .example.com or example.com you configured as the default in your nginx config. Make sure you click the [Save Changes] button, then restart nginx. Do it in this order. Otherwise, you will find your server in an endless redirect loop.

As I often work with multiple domain-names and I like to keep my configs as clean and rock solid as possible I almost always use regex with nginx.

Following redirects any subdomain.domain.tld into domain.tld.

server {
    listen 80;
    server_name ~^((?<subdomain>.*)\.)(?<domain>[^.]+)\.(?<tld>[^.]+)$;
    return 301 $scheme://${domain}.${tld};

If you want to redirect a subdomain to a page this is possible as well:

server {
    listen 80;
    server_name ~^((?<subdomain>.*)\.)(?<domain>[^.]+)\.(?<tld>[^.]+)$;
    return 301 $scheme://${domain}.${tld}/${subdomain};

Now any subdomain.domain.tld gets redirected to domain.tld/subdomain.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Join the Tech Talk
Success! Thank you! Please check your email for further details.

Please complete your information!

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel