Remove "www" and redirect to "https" with nginx

To remove the "www" from URLs and redirect all incoming traffic to HTTPS in Nginx, you can use a server block that handles both scenarios. Here's an example configuration:

1. Open your Nginx configuration file for your site (commonly found at /etc/nginx/sites-available/yoursite or /etc/nginx/nginx.conf).
2. Add or modify a server block to handle the redirection. Here's an example:

server {
    listen 80;
    server_name www.yourdomain.com;

    # Redirect www to non-www and to HTTPS
    return 301 https://yourdomain.com$request_uri;
}

server {
    listen 443 ssl;
    server_name www.yourdomain.com;

    # Redirect www to non-www and to HTTPS
    return 301 https://yourdomain.com$request_uri;
}

server {
    listen 443 ssl;
    server_name yourdomain.com;

    # Your regular HTTPS server block configuration goes here
    # ...

    # Rest of your SSL configuration for yourdomain.com
    # include SSL certificate, key, SSL protocols, etc.
    # ...
}

In this configuration:

• The first two server blocks handle HTTP and HTTPS requests for www.yourdomain.com and redirect to https://yourdomain.com.
• The third server block handles HTTPS requests for yourdomain.com and should contain your regular site configuration for handling HTTPS traffic.
• Save the changes and exit the configuration file.
• After making changes, reload Nginx to apply the new configuration:

sudo systemctl reload nginx

This will redirect both http://www.yourdomain.com and https://www.yourdomain.com to https://yourdomain.com.

Ensure you have the appropriate SSL configurations and certificates set up for yourdomain.com in the last server block to handle HTTPS traffic. Adjust the server_name and SSL configurations according to your specific setup.

Got an article suggestion? Let us know

Explore more

SSL Nginx

Solved: curl: (35) ssl connect error

The main course of this problem is the outdated `curl` package on your system.

Questions

What is SSL Certificate Monitoring?

Learn what is SSL certificate monitoring, how does it work, what are the benefits and drawbacks and how to set it up.

Guides

Solved: SSL_Error_rx_record_too_long

The usual cause is that the implementation of SSL on your server is not correct. The error is usually caused by a server-side problem which the server administrator will need to investigate.

Questions

Multiple domains with SSL on same IP?

Questions

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.