Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Change the listen directive in the active Nginx server {} block from 8080 to 80, test the configuration, and reload Nginx. If Nginx is acting as a reverse proxy, change only the public listener; leave the WordPress or application upstream on 127.0.0.1:8080. WordPress itself cannot make this server-level change.

What changing the port actually does

A URL containing :8080 reaches a service that is listening on TCP port 8080. Standard HTTP uses port 80, so a visitor can normally use http://example.com/ instead of http://example.com:8080/ after Nginx accepts connections on port 80.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Nginx chooses the address and port for a virtual host with its listen directive. The port change is therefore an Nginx administration task, not a WordPress setting. WordPress can generate links and redirects, but it does not rewrite Nginx’s server configuration. Its Nginx guidance also requires the administrator to maintain the server-level rewrite and PHP rules.

There are two layouts to distinguish before editing:

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
  • Standalone Nginx: Nginx serves the WordPress files directly and usually passes PHP scripts to PHP-FPM. The same server block contains root, WordPress locations, and PHP handling.
  • Reverse proxy: Nginx is the public entry point and forwards requests to another process on port 8080. In this case, public Nginx moves to port 80 while the upstream process remains on 8080.

Do not change an unrelated listen 8080; block. A host can contain several sites and services, and only the block serving this WordPress hostname should be modified.

Identify the active WordPress server block

Find the configuration file that Nginx actually loads. Package layouts differ: Debian-based systems commonly use files under /etc/nginx/sites-available/ and symlinks in /etc/nginx/sites-enabled/, while other distributions often place virtual hosts under /etc/nginx/conf.d/. Containers and managed providers may use a mounted application-specific path.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Ask Nginx to print its complete, expanded configuration and search for the WordPress hostname, the document root, or port 8080:

sudo nginx -T | less
sudo nginx -T 2>/dev/null | grep -nE 'listen .*8080|server_name|root |proxy_pass'

The active block normally contains a matching server_name, such as example.com www.example.com, and either a root directive or a proxy_pass directive. Confirm that the file you edit is included by the running configuration; changing an unused template has no effect.

Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

Record the current configuration or create a dated copy before editing. This gives you a fast rollback if a syntax error, wrong virtual host, or application issue appears after the reload.

Checks to complete before moving to port 80

  • Confirm the intended address: Decide whether Nginx should listen on every local IPv4 address (listen 80;), a specific IPv4 address (listen 192.0.2.10:80;), IPv6 as well, or a combination. Keep the existing address scope unless you have a reason to change it.
  • Check port ownership: Another web server, container, control panel, or service may already occupy port 80. On a Linux host, inspect listeners with sudo ss -ltnp | grep ':80 ' or an equivalent service-monitoring command.
  • Check privileges: Ports below 1024 generally require the privileges used by Nginx’s master process. A package-managed Nginx service normally starts with the required privilege and runs worker processes with reduced permissions. A manually launched, unprivileged process may not be able to bind port 80.
  • Check firewall and cloud rules: The host firewall and any provider security group must allow inbound TCP 80. Changing Nginx alone does not open a blocked network path.
  • Preserve application directives: Keep the existing server_name, root, index, PHP-FPM settings, WordPress rewrite location, TLS blocks, and upstream definitions unless a separate migration requires them.

Change a standalone Nginx WordPress site

Use this procedure when Nginx serves files from a WordPress document root and sends PHP scripts to PHP-FPM.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  1. Open the active virtual-host file. For example, edit the file identified by nginx -T with your administrator editor. Do not assume a distribution-specific path if the expanded configuration shows a different one.
  2. Replace the public listener. Change the relevant line from listen 8080; to listen 80;. If the original is address-specific, preserve that form, changing only the port: listen 192.0.2.10:8080; becomes listen 192.0.2.10:80;.
  3. Leave WordPress processing intact. Keep the existing server_name, root, index, location / rewrite, PHP-FPM location ~ .php$, and security restrictions. Nginx does not use Apache .htaccess files for these rules.
  4. Save and test the full configuration. Run sudo nginx -t. A successful result includes a syntax check and a confirmation that the test is successful. Do not reload after a failed test.
  5. Reload the service. On a systemd installation this is commonly sudo systemctl reload nginx. Use the service manager provided by the operating system, package, container image, or hosting provider when that command differs.
  6. Test without the old suffix. Request http://example.com/ and the server’s IP address, then test the WordPress login, a post permalink, an image or stylesheet, and a page that executes PHP.

A minimal standalone block looks like this, but the production file must retain its existing WordPress locations and PHP-FPM details:

server {
    listen 80;
    server_name example.com www.example.com;
    root /var/www/wordpress;
    index index.php index.html;

    # Keep the existing WordPress rewrite and PHP-FPM locations here.
}

Change Nginx when WordPress stays behind an upstream on 8080

In a reverse-proxy deployment, the process on port 8080 is not necessarily Nginx. It might be a WordPress application server, a PHP-capable web server, or a container. The public listener and the upstream destination are separate sockets.

Rank #3
Sale
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black | LED mouse pad with 14 lighting modes, covers keyboard & mouse, anti-slip rubber base, waterproof surface, USB powered
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
  1. Find the proxy server block. Look for the WordPress server_name and a proxy_pass directive. Confirm that the upstream address and port are the process you intend to keep.
  2. Change only the public listener. Replace listen 8080; with listen 80;, preserving an address-specific form if one is present.
  3. Keep the upstream unchanged. If the application is currently at http://127.0.0.1:8080, leave that value in proxy_pass unless you are deliberately moving the application itself.
  4. Preserve forwarding headers. The upstream commonly needs the original host, client address, forwarding chain, and scheme. Keep the existing proxy_set_header directives and do not remove HTTPS-related headers during a port-only change.
  5. Test, reload, and test the application. Run sudo nginx -t, reload through the host’s service manager, and verify both the public request and the local upstream process.

For example:

server {
    listen 80;
    server_name example.com;

    location / {
        proxy_pass http://127.0.0.1:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

This arrangement lets visitors connect to port 80 while the backend continues listening privately on 8080. It avoids an unnecessary application restart and keeps the upstream port hidden from the public interface when the binding is local.

WordPress URLs, redirects, and permalinks after the change

Removing :8080 from Nginx does not automatically rewrite every URL stored in WordPress. WordPress has separate “WordPress Address (URL)” and “Site Address (URL)” values, and a reverse proxy can also affect the scheme and host that PHP sees.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

After the Nginx reload, inspect the front page source and browser network panel for links, scripts, stylesheets, images, feeds, and redirects that still point to :8080. If the site itself is configured with the old port, update the URL through the normal WordPress administration path or the deployment’s configuration method, taking a database backup before a bulk replacement.

Do not change the URL merely because the backend remains on 8080. In a reverse-proxy design, the public WordPress URL should normally use the public host and port 80 (or HTTPS), while the private upstream address remains an infrastructure detail.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.

Test a post and page permalink, because Nginx does not read Apache .htaccess files. The existing Nginx rewrite should route a missing file to WordPress’s front controller, commonly index.php. If that location was lost while editing, the home page may work while individual permalinks return 404 errors.

Validate the change safely

Syntax and service state

  1. Run sudo nginx -t before every reload.
  2. Reload rather than stop and start when the configuration test succeeds, so existing connections can finish according to the service’s normal reload behavior.
  3. Check the service status and recent logs if the reload reports an error: sudo systemctl status nginx and sudo journalctl -u nginx are common systemd diagnostics.

Socket and HTTP checks

sudo ss -ltnp | grep -E ':(80|8080)b'
curl -I http://example.com/
curl -I http://example.com/wp-login.php
curl -I http://example.com/a-known-post/

The socket check shows whether Nginx owns port 80 and whether the backend is still listening on 8080. The HTTP checks should return the expected status and host, not a connection refusal, an unrelated default site, or a redirect to the old port.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Browser checks

  • Load the home page in a private window to avoid cached redirects.
  • Sign in at /wp-login.php and open the dashboard.
  • Open an existing post, a page, a category, and a media attachment.
  • Use browser developer tools to confirm that CSS, JavaScript, images, and AJAX requests do not target the obsolete port.
  • If HTTPS is already configured, test the HTTPS virtual host separately; changing HTTP port 80 does not replace the TLS listener on port 443.

Common failures and precise fixes

Symptom Likely cause Fix
nginx -t reports “bind() … address already in use” Another process owns port 80, or two Nginx blocks conflict on the same address and port. Identify the owner with a socket-listening command, stop or reconfigure the competing service, or assign a deliberate address-specific listener. Then test again.
Permission denied while binding port 80 Nginx was started without the privileges required for a low-numbered port. Start it through the supported service manager or adjust the deployment’s privilege and capability model. Do not solve the problem by making WordPress files writable.
The old default Nginx page appears The request matches another server block, the hostname’s DNS points elsewhere, or the intended file is not included. Inspect nginx -T, verify server_name, confirm DNS and the request’s Host header, and remove or correct the competing default block.
502 Bad Gateway after the change A reverse-proxy upstream is stopped, unreachable, or still expected at a different address. Confirm the application is listening on 8080, check the exact proxy_pass address, and read the Nginx error log. A public port change should not require moving the upstream.
Home page works but post permalinks return 404 The WordPress rewrite location was removed or altered. Restore the prior Nginx front-controller rule and retest; do not add Apache .htaccess syntax to an Nginx file.
Redirects still include :8080 WordPress URL settings, proxy headers, a cache, or an application-generated canonical URL still references the old public address. Check the public URL settings and forwarded host/scheme headers, purge the relevant cache, and retest in a private browser window.
CSS or images fail while HTML loads Asset URLs contain the old port, or a firewall/security rule treats the new endpoint differently. Inspect the failed request URL, correct the canonical site URL or generated configuration, and allow TCP 80 through every network layer.
Reload fails but the old site remains available Nginx rejected the new configuration and kept its previous running configuration. Read the exact syntax error, restore the backup if necessary, correct the directive, run nginx -t again, and reload only after a successful test.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Port 80 versus port 8080: what belongs where

Deployment Public listener Where WordPress executes What changes What stays on 8080
Standalone Nginx with PHP-FPM Nginx listen 80; Files are served by Nginx; PHP runs through the existing PHP-FPM socket or upstream. Only the active server block’s public listener. Nothing unless another local service uses that port.
Nginx reverse proxy Nginx listen 80; The proxied application receives the request from Nginx. The public listener and any firewall rule needed for port 80. The upstream named by proxy_pass, such as 127.0.0.1:8080.
WP-CLI development server The process started by wp server WP-CLI’s temporary development server serves the site. The command-line port option, not an Nginx server block. 8080 is the documented default unless another port is supplied.

For a managed or production installation, the first two layouts are operationally different from WP-CLI’s development server. Nginx service configuration, log rotation, TLS integration, process supervision, and boot persistence are controlled by the host’s service setup. A development command is normally started manually for a limited session and should not be treated as a replacement for a managed Nginx deployment.

The separate WP-CLI case

If the address ending in :8080 comes from WP-CLI rather than Nginx, use WP-CLI’s port option:

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
wp server --port=80

wp server defaults to port 8080. This command starts WordPress’s built-in development server; it does not edit an Nginx configuration and does not move an Nginx reverse-proxy upstream. Port 80 still has the same privilege and port-conflict constraints, so an unprivileged shell or an existing listener may prevent the command from starting.

Use the command only when you intentionally run the WP-CLI development server. If a system service already owns the site, change the active Nginx block instead and leave the development command unrelated.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

HTTP, HTTPS, and DNS considerations

Port 80 is the conventional clear-text HTTP endpoint. If the site uses HTTPS, Nginx commonly keeps a separate listen 443 ssl; server block and redirects HTTP requests to HTTPS. Changing 8080 to 80 does not automatically create a certificate, alter the 443 block, or renew TLS credentials.

Make sure the domain’s DNS records point to the host where Nginx now listens. If a reverse proxy or load balancer sits in front of this machine, that front layer may be the component that owns public port 80; in that architecture, changing an internal Nginx listener alone may not alter the address visitors use.

When TLS terminates at a front proxy, retain the forwarding scheme information expected by WordPress and the upstream. Otherwise the application can generate HTTP URLs, issue redirect loops, or mark secure cookies incorrectly even though port 80 itself is reachable.

Rollback plan

  1. Restore the saved virtual-host file or change listen 80; back to the original 8080 form.
  2. Run sudo nginx -t to confirm the rollback is syntactically valid.
  3. Reload Nginx with the host’s service manager.
  4. Verify the old URL with :8080 and record the error that caused the rollback before attempting another change.

Keep the upstream process and WordPress files untouched during a listener-only rollback. That isolates the network change and prevents an unrelated application migration from obscuring the original problem.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Operational checklist

  • Locate the included server block that owns the WordPress hostname.
  • Confirm whether it serves files directly or proxies to an upstream.
  • Check who owns port 80 and whether the service has the required privileges.
  • Change only the intended listen directive from 8080 to 80.
  • Keep WordPress rewrite, PHP-FPM, proxy, header, TLS, and upstream settings consistent.
  • Run nginx -t; never reload a failed configuration.
  • Reload through the correct service manager.
  • Test the home page, login, permalinks, assets, redirects, and (if applicable) the unchanged 8080 upstream.
  • Correct WordPress’s public URL or proxy headers only if responses still advertise the old port.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.