Edit the /etc/nginx/sites-available/default file
Add green section code
server {
listen 80 default_server;
listen [::]:80 default_server;
return 301 https://servername.com:443$request_uri;
}
server {
listen 443 ssl default; server_name _;
server_name _;
ssl_certificate /etc/letsencrypt/live/servername.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/servername.com/privkey.pem;
return 301 https://servername.com:443$request_uri;
}Save, then restart the nginx server
# systemctl nginx restart
How to Configure Nginx to Automatically Redirect Direct IP Access to a Domain Name: A Pre-Implementation Checklist
When creating technical tutorials, the biggest pitfall is copying commands verbatim while ignoring differences in the environment. Different system versions, web servers, plugin combinations, and permission settings can all affect the final outcome. Before proceeding, it’s recommended that you document your current configuration and, if necessary, create a snapshot or backup. That way, even if you make a mistake during the process, you can quickly roll back the changes.
We recommend confirming the following before proceeding
- System and Software Versions:Verify the versions of Windows, Debian, Nginx, Apache, WordPress, or related tools.
- Permissions:When dealing with credentials, certificates, or configuration files, first verify that the current user has sufficient permissions.
- Backup:Before modifying a configuration file, make a copy of the original file first. For WordPress sites, it’s also recommended to back up the database.
- Test Method:Validate your changes after each step; don't wait until you've finished making all the changes to troubleshoot.
Troubleshooting Approach
When you encounter an error, first determine at which layer it occurred: the browser, DNS, server, application, plugin, or permissions. Breaking the problem down into smaller parts is more effective than repeatedly searching through an entire error message. For issues involving WordPress, Nginx, certificates, and proxies, logs are usually more reliable than front-end pages.
If the paths or menus in this tutorial differ from those in your environment, refer to your system’s current display first, and then use the keywords to locate the corresponding features. This is especially true for the Windows Control Panel, the WordPress plugin menu, and cloud service consoles, as their access points are frequently updated with new versions.
Recommendations for Follow-up Maintenance
Completing a fix does not mean the problem is permanently resolved. We recommend documenting key commands, modified files, modification times, and verification results. These records can save a significant amount of troubleshooting time when you later migrate servers, upgrade plugins, or change themes.
English 
Chinese