{"id":2550,"date":"2018-09-30T10:23:41","date_gmt":"2018-09-30T04:53:41","guid":{"rendered":"https:\/\/pheonixsolutions.com\/blog\/?p=2550"},"modified":"2026-09-25T18:18:41","modified_gmt":"2026-09-25T12:48:41","slug":"how-to-change-ngnix-config-setup-to-another-port-8080-in-linux","status":"publish","type":"post","link":"https:\/\/pheonixsolutions.com\/blog\/how-to-change-ngnix-config-setup-to-another-port-8080-in-linux\/","title":{"rendered":"How to Configure Nginx to Listen on Port 8080 in Linux"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Post Date:<\/strong> September 25, 2026<br><strong>Last Updated:<\/strong> September 25, 2026<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Introduction<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">By default, Nginx listens for HTTP traffic on <strong>port 80<\/strong>. However, there are situations where Nginx needs to use an alternate port such as <strong>8080<\/strong>. This is common when another web server, such as Apache, is already using port 80, or when an application requires Nginx to listen on a separate port.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Changing the Nginx listening port involves more than updating the <code>listen<\/code> directive. On systems with <strong>SELinux<\/strong> enabled, the new port must also be permitted by the SELinux policy. If the server firewall or cloud security rules restrict the port, those settings must be updated as well.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before proceeding, make sure you have:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A Linux server with Nginx installed<\/li>\n\n\n\n<li>Root or sudo access<\/li>\n\n\n\n<li>Access to the Nginx configuration<\/li>\n\n\n\n<li>Port 8080 available on the server<\/li>\n\n\n\n<li>Basic Linux command-line knowledge<\/li>\n\n\n\n<li>Access to the server firewall configuration, if required<\/li>\n\n\n\n<li>Access to the cloud security group or network firewall, if applicable<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Note:<\/strong> Another service cannot use the same IP address and TCP port that Nginx is configured to use.<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">You can check whether port 8080 is already in use:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ss -ltnp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If there is no output, port 8080 is generally available.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Install Nginx<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If Nginx is not already installed, install it using your Linux distribution&#8217;s package manager.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">RHEL \/ CentOS<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On systems where EPEL is required:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo yum install epel-release\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Install Nginx:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo yum install nginx\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On newer RHEL-based systems, <code>dnf<\/code> can be used:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo dnf install nginx\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Ubuntu \/ Debian<\/h3>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo apt update\nsudo apt install nginx\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">After installation, verify the Nginx version:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">nginx -v\n<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Identify the Nginx Configuration File<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The configuration file location depends on the Linux distribution and installation method.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">RHEL \/ CentOS<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The main configuration file is generally:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">\/etc\/nginx\/nginx.conf\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Ubuntu \/ Debian<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The main configuration file is generally:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">\/etc\/nginx\/nginx.conf\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Individual virtual host configurations are commonly stored under:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">\/etc\/nginx\/sites-available\/\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">and enabled through:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">\/etc\/nginx\/sites-enabled\/\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">\/etc\/nginx\/sites-available\/default\n\/etc\/nginx\/sites-enabled\/default\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can inspect the complete active Nginx configuration with:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo nginx -T\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This is useful when you are unsure which configuration file contains the <code>listen<\/code> directive.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Back Up the Nginx Configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before making configuration changes, create a backup.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the main configuration:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo cp \/etc\/nginx\/nginx.conf \/etc\/nginx\/nginx.conf.backup\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you are modifying a specific virtual host configuration, back up that file instead.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo cp \/etc\/nginx\/sites-available\/default \/etc\/nginx\/sites-available\/default.backup\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Having a configuration backup makes it easier to revert the change if an issue occurs.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Change the Nginx Listening Port<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Open the appropriate configuration file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo nano \/etc\/nginx\/nginx.conf\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Look for a <code>listen<\/code> directive similar to:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">listen 80;\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Change it to:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">listen 8080;\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the configuration uses <code>default_server<\/code>, preserve that option:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">listen 8080 default_server;\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A basic server block may look like:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">server {\n    listen 8080;\n    server_name example.com;\n\n    root \/var\/www\/html;\n    index index.html index.htm;\n}\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you are using a separate virtual host file, make the change in that server block instead.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Test the Nginx Configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before restarting Nginx, validate the configuration:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo nginx -t\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A successful test should show output similar to:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">syntax is ok\ntest is successful\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If Nginx reports an error, fix the configuration before continuing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This validation step is important because restarting Nginx with an invalid configuration can prevent the service from starting.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Configure SELinux for Port 8080<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On RHEL\/CentOS systems with SELinux enabled and enforcing, Nginx may not be permitted to bind to port 8080 unless that port is associated with the appropriate SELinux HTTP port type.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First, check the SELinux status:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sestatus\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If SELinux is enforcing, check the ports currently associated with HTTP services:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo semanage port -l | grep http_port_t\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the <code>semanage<\/code> command is not available, install the required SELinux management package.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On many RHEL\/CentOS systems:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo yum install policycoreutils-python-utils\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On some older distributions, the package name may be different.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Add port 8080 to the HTTP port type:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo semanage port -a -t http_port_t -p tcp 8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify the configuration:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo semanage port -l | grep http_port_t\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Port 8080 should now appear in the list.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">If port 8080 is already defined<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If SELinux already has an entry for port 8080 but it is associated with another port type, modify it:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo semanage port -m -t http_port_t -p tcp 8080\n<\/pre>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> Disabling SELinux is not required just to make Nginx listen on port 8080. Configure the appropriate SELinux policy instead.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Allow Port 8080 Through the Firewall<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Nginx can listen on port 8080 while external clients are still unable to connect if the server firewall blocks the port.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your server uses <code>firewalld<\/code>, allow TCP port 8080:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo firewall-cmd --permanent --add-port=8080\/tcp\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Reload the firewall:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo firewall-cmd --reload\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify the configuration:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo firewall-cmd --list-ports\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You should see:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">8080\/tcp\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Ubuntu \/ Debian with UFW<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If UFW is enabled, allow port 8080:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ufw allow 8080\/tcp\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ufw status\n<\/pre>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Note:<\/strong> Only open port 8080 if external access is actually required. If the port is intended for internal communication, restrict access to the required source networks instead of exposing it publicly.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 8: Check Cloud Firewall or Security Group Rules<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the server is hosted on a cloud platform, the operating system firewall may not be the only network control.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, on AWS, check the EC2 <strong>Security Group<\/strong> and ensure the required inbound rule exists:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">Protocol: TCP\nPort: 8080\nSource: Required IP range\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid using <code>0.0.0.0\/0<\/code> unless public access to port 8080 is genuinely required.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same principle applies to other cloud providers and network firewalls.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 9: Restart Nginx<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After updating the configuration and firewall\/SELinux settings, restart Nginx:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo systemctl restart nginx\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Check the service status:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo systemctl status nginx\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If Nginx fails to start, check the service logs:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo journalctl -u nginx --no-pager -n 50\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also check the Nginx error log:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo tail -f \/var\/log\/nginx\/error.log\n<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 10: Verify That Nginx Is Listening on Port 8080<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Use the <code>ss<\/code> command to check the listening sockets:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ss -ltnp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You should see output similar to:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">LISTEN 0 511 0.0.0.0:8080 0.0.0.0:* users:((\"nginx\",pid=1234,fd=6))\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For IPv6, you may also see:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">LISTEN 0 511 [::]:8080 [::]:* users:((\"nginx\",pid=1234,fd=7))\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also use:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo netstat -lntp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">However, <code>ss<\/code> is generally preferred on modern Linux systems.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 11: Test the Website Locally<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before testing from another system, verify the service locally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/127.0.0.1:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A working web server should return an HTTP response such as:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">HTTP\/1.1 200 OK\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the application, you may instead receive another valid HTTP status such as <code>301<\/code>, <code>302<\/code>, <code>403<\/code>, or <code>404<\/code>. The important point is that the request reaches Nginx and receives an HTTP response.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can also test the configured server name:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/example.com:8080\n<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Step 12: Test From a Remote System<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If port 8080 is intended to be accessible externally, open:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">http:\/\/SERVER_IP:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">http:\/\/10.1.1.1:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For a public server:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">http:\/\/your-domain.com:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also test connectivity using:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/SERVER_IP:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the local test works but the remote test fails, check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Linux firewall<\/li>\n\n\n\n<li>Cloud security group<\/li>\n\n\n\n<li>Network firewall<\/li>\n\n\n\n<li>Routing<\/li>\n\n\n\n<li>Nginx listening address<\/li>\n\n\n\n<li>DNS configuration, if using a hostname<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Nginx fails to start<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">First test the configuration:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo nginx -t\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then check:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo systemctl status nginx\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">and:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo journalctl -u nginx --no-pager -n 50\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Port 8080 is already in use<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ss -ltnp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If another service is using the port, either stop or reconfigure that service, or select another available port.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SELinux blocks Nginx<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check for relevant AVC denials:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ausearch -m AVC -ts recent\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then verify that port 8080 is associated with <code>http_port_t<\/code>:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo semanage port -l | grep http_port_t\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Local access works but remote access fails<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If this works:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/127.0.0.1:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">but this fails from another machine:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/SERVER_IP:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">check the firewall and cloud security rules first.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The browser cannot connect<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Verify that Nginx is listening:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ss -ltnp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then test:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/SERVER_IP:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Also confirm that the correct IP address and port are being used.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Security Considerations<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Port 8080 is commonly used for alternate HTTP services, but changing the port does <strong>not<\/strong> make HTTP traffic secure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the application handles sensitive information, consider using HTTPS with a suitable TLS configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, the public application may use:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">https:\/\/example.com\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">while Nginx internally proxies requests to an application running on:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">http:\/\/127.0.0.1:8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This is different from exposing port 8080 directly to the public internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If port 8080 is only required for internal communication, restrict firewall access to trusted networks or hosts.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Configuration Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The basic change is:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Before<\/h3>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">server {\n    listen 80;\n    server_name example.com;\n}\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">After<\/h3>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">server {\n    listen 8080;\n    server_name example.com;\n}\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then validate and restart:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo nginx -t\nsudo systemctl restart nginx\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ss -ltnp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">And test:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/127.0.0.1:8080\n<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Configuring Nginx to use port <strong>8080<\/strong> is straightforward, but a successful configuration requires more than changing the <code>listen<\/code> directive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The complete process should include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Updating the correct Nginx server block<\/li>\n\n\n\n<li>Testing the configuration before restarting<\/li>\n\n\n\n<li>Configuring SELinux when it is enforcing<\/li>\n\n\n\n<li>Allowing the port through the appropriate firewall<\/li>\n\n\n\n<li>Checking cloud security rules when applicable<\/li>\n\n\n\n<li>Restarting Nginx<\/li>\n\n\n\n<li>Verifying the listening socket<\/li>\n\n\n\n<li>Testing the application locally and remotely<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Most importantly, <strong>do not disable SELinux simply to make Nginx work on port 8080<\/strong>. Configure the required SELinux policy and keep the server&#8217;s security controls enabled.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. What port does Nginx use by default?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Nginx normally listens for HTTP traffic on <strong>port 80<\/strong> and HTTPS traffic on <strong>port 443<\/strong>, depending on the configured server blocks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Why would I configure Nginx to use port 8080?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Port 8080 can be useful when port 80 is already occupied by another service, when running multiple web services, or when an application requires an alternate HTTP port.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. How do I check whether port 8080 is available?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Run:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ss -ltnp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If another process is listening on the port, you will need to use a different port or reconfigure the existing service.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Do I need to disable SELinux for port 8080?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. If SELinux is enforcing, associate port 8080 with the appropriate HTTP port type:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo semanage port -a -t http_port_t -p tcp 8080\n<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5. Why does Nginx work locally but not from another computer?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The most common causes include a blocked firewall port, cloud security group rules, network restrictions, or Nginx listening only on a local interface.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. How can I verify that Nginx is listening on port 8080?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Run:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sudo ss -ltnp | grep :8080\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also test the HTTP service with:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">curl -I http:\/\/127.0.0.1:8080\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Related Articles<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/pheonixsolutions.com\/blog\/how-to-setup-ssl-certificate-in-nginx-on-ubuntu-20-04\/\">How to setup SSL Certificate in Nginx on Ubuntu 20.04<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/pheonixsolutions.com\/blog\/how-to-install-and-configure-php-with-nginx-on-centos7\/\">How to install and configure PHP with Nginx on centos7<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/pheonixsolutions.com\/blog\/how-to-install-nginx-and-lets-encrypt-ssl-with-html-docker-ubuntu-20-04\/\">How to Install Nginx and Let\u2019s Encrypt SSL with HTML + Docker \u2013 Ubuntu 20.04<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Get Expert Linux &amp; Server Support<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Need help configuring Nginx, troubleshooting Linux servers, or resolving web server and networking issues? Our team can help with Linux administration, server configuration, security, and DevOps support.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/pheonixsolutions.com\/contact\"><strong>Connect with our experts.<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Post Date: September 25, 2026Last Updated: September 25, 2026 Introduction By default, Nginx listens for HTTP traffic on port 80. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1022],"tags":[420,271,424],"class_list":["post-2550","post","type-post","status-publish","format-standard","hentry","category-web-architecture","tag-change-ngnix-port-in-linux","tag-nginx","tag-port-8080","psol-cat-web-architecture"],"jetpack_publicize_connections":[],"jetpack_shortlink":"https:\/\/wp.me\/phn2x7-F8","jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/2550","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=2550"}],"version-history":[{"count":1,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/2550\/revisions"}],"predecessor-version":[{"id":11924,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/2550\/revisions\/11924"}],"wp:attachment":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=2550"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=2550"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=2550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}