{"id":70732,"date":"2021-04-01T09:00:00","date_gmt":"2021-04-01T13:00:00","guid":{"rendered":"https:\/\/www.inmotionhosting.com\/support\/?p=70732"},"modified":"2025-11-07T17:17:22","modified_gmt":"2025-11-07T22:17:22","slug":"nginx-redirect","status":"publish","type":"post","link":"https:\/\/www.inmotionhosting.com\/support\/server\/nginx\/nginx-redirect\/","title":{"rendered":"How to Create NGINX Redirects"},"content":{"rendered":"
\"NGINX<\/figure>\n\n\n\n

NGINX<\/strong><\/a> can be used as a web server<\/a> (in lieu of Apache) or proxy server<\/a>. For those using it as a web server, creating NGINX redirects requires editing server configuration files. This is different from Apache which also checks .htaccess<\/a> files during web server requests. NGINX doesn\u2019t use .htaccess<\/a>. Need to know how to redirect HTTP to HTTPS in NGINX? Don\u2019t worry. It\u2019s a simple process, as easy as hiding your NGINX server version<\/a>.<\/p>\n\n\n\n

Create NGINX Redirects<\/h2>\n\n\n\n

SSH into your NGINX web server<\/a> as user root. Edit your NGINX configuration file using Nano<\/a>, Vim<\/a>, Emacs<\/a>, etc. We\u2019ll be editing domain configuration files in the sites-enabled<\/code> directory as it is the easiest method to create NGINX redirects. The file may state default<\/em> or take the name of the domain.<\/p>\n\n\n\n