Скачать или смотреть How to Redirect www to non-www in NGINX

Learn how to easily redirect from www to non-www in NGINX with this comprehensive guide. Effective fixes for common issues included!
---
This video is based on the question https://stackoverflow.com/q/65882532/ asked by the user 'Dinesh Udayan' ( https://stackoverflow.com/u/14468770/ ) and on the answer https://stackoverflow.com/a/65885148/ provided by the user 'jaygooby' ( https://stackoverflow.com/u/391826/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: https www to non www (NGINX)

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Redirect www to non-www in NGINX: A Step-by-Step Guide

Are you struggling with a problem of having both www and non-www versions of your website in NGINX? If you've tried multiple solutions without success, don't worry! You're not alone. This common issue can be a bit tricky for newcomers to tackle, especially when payment gateways and seamlessly integrated redirection come into play. In this guide, we will help you understand how to set up your NGINX configuration for redirecting visitors from the www version of your website to the non-www version effectively.

Understanding the Issue

When you have both www and non-www URLs, users can access your site via both addresses. This can lead to duplicate content issues, which can harm your SEO and create confusion for both users and payment gateways. The goal is to ensure that all visitors are redirected to a single version of the site, typically the non-www URL in this case.

Step-by-Step Solution to Redirect www to non-www

Let’s break down the implementation process into clear sections:

Step 1: Basic Configuration

First, make sure that DNS is set up correctly for both www.example.com and example.com. With your DNS configured properly, you can proceed with the NGINX settings.

Step 2: NGINX Configuration

Here’s a streamlined version of what your NGINX configuration should look like:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Explanation of the Configuration

First Block (Redirect www to non-www): This block listens for requests on both HTTP and HTTPS for www.example.com, then redirects them to the non-www version with a 301 status code.

Second Block (Handling Non-www HTTP requests): This block listens for HTTP requests to non-www (example.com) and enforces a redirect to the secure HTTPS version.

Third Block (The Secure Non-www Website): This serves the main non-www website at example.com over HTTPS.

Important Notes

301 Redirect: Using a 301 redirect is essential for SEO as it informs search engines that the page has moved permanently to the new address.

SSL Certificates: Ensure you have valid SSL certificates set for both www and non-www domains to serve your site securely.

Conclusion

By following these steps, you can effectively redirect all traffic from www to non-www in NGINX, preventing issues with duplicate content and improving your website's SEO. Redirection helps ensure a seamless user experience, particularly during transactions with payment gateways.

If you face any challenges, feel free to reach out and share your experiences! Happy configuring!