<\/span><\/h2>\n\n\n\nThere are several reasons why you may need to change port number of NGINX server.<\/p>\n\n\n\n
1. Improved Security<\/strong> – By default, NGINX runs on port 80. Most hackers and malicious bots target common ports like 80 for their attacks. By configuring NGINX to run on a non-standard port, you will make it difficult for automated scripts and bots to hack your server.
2. Run Multiple Services<\/strong> – If you are running other services such as Apache that also use port 80, then you may need to change NGINX port number.
3. For Testing Purposes<\/strong> – If you are running NGINX in a development or staging environment, then you can run it on a different port to avoid interfering with production server, that runs on port 80. This will allow you to run multiple NGINX instances on a single server.
4. Specific Application Requirements<\/strong> – Sometimes, you may need to run NGINX on a different port, simply to integrate with other systems. They may already be configured to read input from or send output to another port. So NGINX will need to listen to that port.
5. Firewall Rules<\/strong> – Many organizations block port 80 by default, for security purposes. They know that port 80 is a common target of online attacks and it is better to avoid using it completely. In such cases, you will need to change NGINX port number to something else.<\/p>\n\n\n\n