Change the port where Node listens, restart the process that runs the application, and then verify the socket, firewall, and proxy path. The safest pattern is to read the value from process.env.PORT so the same code can run on different VPS environments.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
For an Express application, a minimal entry point is:
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsconst port = Number(process.env.PORT || 3000);
app.listen(port, '127.0.0.1', () => {
console.log(`Listening on ${port}`);
});What actually changes when you change a Node.js port?
A Node.js web server owns a TCP listening socket. Changing the port means changing the number passed to server.listen() (or Express’s equivalent app.listen()), recreating the running process with that value, and making every network component agree about the new destination.
Node documents server.listen([port[, host[, backlog]]][, callback]) as the API that starts a server listening for connections on a port and host. If the port is omitted or set to 0, the operating system selects an unused port. If the host is omitted, Node uses the unspecified IPv6 address when available or the unspecified IPv4 address otherwise. See the Node.js net documentation for the exact API behavior.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Express does not create a separate listening mechanism: its app.listen() method is identical to Node’s http.Server.listen() and accepts a port and optional host, as described in the Express application API.
A URL, DNS record, or browser bookmark does not move a listener by itself. The application must bind the new port, the supervisor must start a new process with the desired environment, and a firewall or reverse proxy must allow and forward traffic to it.
Before you edit anything: identify the current listener
Find the code or configuration that chooses the port
From the project directory, search the entry point and configuration files for the common forms:
grep -RIn --exclude-dir=node_modules -E 'app.listen(|server.listen(|process.env.PORT|NODE_PORT|PORT=' .You may find the value in server.js, app.js, a TypeScript source file, a framework configuration file, a container definition, or a service unit. The important question is which file is used by the process that is actually running. A source file that is no longer part of the production build will not change the deployed listener.
Prefer an environment variable over a hard-coded number. Node exposes environment variables through the process.env object; the Node process documentation describes that process environment interface.
Check what is listening now
On a Linux VPS, inspect TCP listeners before making the change:
sudo ss -ltnpLook for the Node process and note both the address and port. An entry such as 127.0.0.1:3000 is reachable only from the VPS itself. An entry such as 0.0.0.0:3000 listens on all IPv4 interfaces, while an IPv6 wildcard may appear as [::]:3000. The exact display depends on the operating system and Node version.
Also identify how the process is launched. Typical possibilities are a shell command, a systemd unit, a process manager, a container, or a hosting control panel. Run:
ps -ef | grep '[n]ode'
systemctl list-units --type=service | grep -i nodeDo not restart an unrelated service. The supervisor that created the existing process is the one that must receive the new environment value.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Choose the binding model: direct Node access or a reverse proxy
The port number and the bind address answer different questions. The port identifies a TCP endpoint; the host determines which interfaces can reach it.
| Deployment choice | Node bind | Public entry point | Firewall and proxy implications |
|---|---|---|---|
| Direct access to Node | An address reachable from the client, commonly an explicitly selected interface or 0.0.0.0 for all IPv4 interfaces |
The Node port itself, such as http://server-address:8080 |
Allow the chosen TCP port in the provider firewall and the VPS firewall; configure TLS and HTTP handling in the application or another front end. |
| NGINX reverse proxy | Private address such as 127.0.0.1:8080 |
NGINX on public HTTP/HTTPS ports, normally 80 and 443 | Expose the proxy ports, keep the Node port private, and update the NGINX upstream when the Node port changes. |
For a reverse-proxy design, binding Node to loopback reduces the externally reachable attack surface and leaves hostname routing, TLS termination, and public access logging at NGINX. NGINX’s official Node.js deployment guide documents this reverse-proxy and load-balancing pattern.
Direct exposure can be appropriate for a deliberately public service or a simple test endpoint, but it makes the Node port part of your public interface. Decide this first; opening a firewall rule for a loopback-only service will not make that service reachable from the internet.
Make the application read the port from the environment
Express entry point
Use a numeric conversion, a documented fallback for local development, and an explicit host:
const port = Number(process.env.PORT || 3000);
const host = process.env.HOST || '127.0.0.1';
app.listen(port, host, () => {
console.log(`Listening on ${host}:${port}`);
});The fallback is used only when PORT is absent. In production, set PORT through the supervisor rather than editing the source for every server. If you require a public direct bind, set HOST to the intended reachable address instead of assuming that loopback is suitable.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Validate invalid values early
A malformed environment value can cause a confusing startup failure or an unintended port. Add a small validation step when the service is important:
const rawPort = process.env.PORT || '3000';
const port = Number(rawPort);
if (!Number.isInteger(port) || port < 1 || port > 65535) {
throw new Error(`Invalid PORT: ${rawPort}`);
}Keep the validation close to startup so the service fails clearly instead of appearing healthy while listening somewhere unexpected.
Set a new port for a shell-launched process
For a one-time launch, assign the variable on the same command line:
PORT=8080 node server.jsThis assignment belongs to that process and its children. It does not permanently change your shell, a systemd unit, a container, or a later login session. To confirm what the application received, log the selected host and port at startup, then check the listener with ss.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
For a persistent shell-based startup script, export the value before launching:
export PORT=8080
node server.jsUse this approach only when the same script is reliably used after reboots. If the VPS must recover from crashes and host restarts, an init system or process supervisor is preferable. Express’s production guidance recommends using an init system and shows systemd units with an executable command, working directory, environment, and automatic restart; see Express production guidance.
Set PORT in systemd
Put the value directly in the unit
Open the unit that launches the application, for example:
sudo systemctl edit my-node-appAdd an override like this, adapting the user, directory, and command to your installation:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →[Service]
WorkingDirectory=/srv/my-node-app
Environment=PORT=8080
ExecStart=/usr/bin/node /srv/my-node-app/server.js
Restart=alwaysDo not blindly add a second ExecStart to an existing service; systemd generally requires the original command to be cleared before replacing it. If the vendor unit already defines ExecStart, inspect it with:
systemctl cat my-node-appThen make the smallest override needed. Keep the service user and file permissions consistent with the existing deployment.
Use an environment file
An environment file keeps deployment values out of the unit body:
sudo install -m 600 /dev/null /etc/my-node-app.env
sudoedit /etc/my-node-app.envPut this line in the file:
PORT=8080Reference it from the unit:
[Service]
EnvironmentFile=/etc/my-node-app.envEnvironment-file syntax is not a shell script. Keep the assignment in the format systemd expects, and avoid assuming that shell expansions or commands will run there.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchReload and restart the correct unit
- Ask systemd to reread unit definitions:
sudo systemctl daemon-reload. - Restart the application:
sudo systemctl restart my-node-app. - Check its state:
sudo systemctl status my-node-app --no-pager. - Read recent logs:
sudo journalctl -u my-node-app -n 100 --no-pager. - Confirm the new socket:
sudo ss -ltnp | grep ':8080'.
Editing .env or an environment file does not modify an already running process. The supervisor must stop the old process and create a new one before Node can see the new value.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Update NGINX when Node is behind a reverse proxy
If NGINX is the public endpoint, change the upstream target from the old private port to the new one. A typical server block contains a proxy destination such as:
location / {
proxy_pass http://127.0.0.1:8080;
proxy_http_version 1.1;
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;
}Use the host and port that exactly match Node’s listening socket. If Node binds to 127.0.0.1:8080 but NGINX still points at 127.0.0.1:3000, clients will receive an upstream error even though the new Node process is healthy.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Test the NGINX configuration:
sudo nginx -t. - Reload NGINX without dropping established connections:
sudo systemctl reload nginx. - Check the application locally:
curl -i http://127.0.0.1:8080/. - Check the public hostname through NGINX:
curl -i https://example.com/. - If the public request fails, inspect both NGINX’s error log and the Node service log.
The public URL normally does not change when only the private upstream port changes. Clients continue to use the hostname and HTTPS port; NGINX absorbs the internal port change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Align provider and operating-system firewalls
A direct Node deployment needs the new TCP port allowed in every filtering layer. Cloud providers commonly have a network firewall, security group, or access rule outside the VPS, while Linux may also run a guest firewall. These controls are separate unless your provider explicitly integrates them.
Direct exposure checklist
- Confirm Node listens on an externally reachable address, not only
127.0.0.1. - Allow the selected TCP port in the VPS provider’s network rules.
- Allow the same port in the guest firewall, such as a UFW rule on Ubuntu.
- Ensure any host-level security policy or routing rule permits the traffic.
- Test using the correct scheme and explicit port, for example
http://server-address:8080.
On a UFW-managed system, a rule might be added with:
sudo ufw allow 8080/tcp
sudo ufw statusReplace the number with your chosen port and follow your provider’s firewall procedure. Do not open a Node port that is meant to remain private behind NGINX.
Reverse-proxy checklist
- Allow public HTTP and HTTPS ports at the provider and guest firewall.
- Keep the private Node port closed to the internet.
- Permit NGINX to connect locally to the Node address and port.
- Update the NGINX upstream and reload it after the Node restart.
Verify the change from inside and outside the VPS
Local socket and HTTP checks
Start with evidence closest to the process:
- Read the startup log and confirm it reports the intended port.
- Run
sudo ss -ltnpand confirm the Node PID owns the new socket. - Request the application locally with
curl -i http://127.0.0.1:8080/when Node binds to loopback. - For a direct bind, request the server’s reachable address and port from the VPS itself.
A successful local response proves that Node accepted the connection on that interface. It does not prove that an external firewall, security group, route, DNS record, or reverse proxy forwards internet traffic.
External check
From a different network, test the public endpoint with the correct protocol and port. For direct HTTP access:
curl -i --connect-timeout 10 http://server-address:8080/For an HTTPS site terminated by NGINX, test the hostname without appending the private Node port:
curl -i --connect-timeout 10 https://example.com/Interpret the result together with the local checks. A refusal usually means no process is accepting the connection at that address, while a timeout commonly indicates filtering or routing. An HTTP response from NGINX proves that the proxy answered, not necessarily that it reached the intended Node process; inspect the response status and logs.
Recommended Free Tools
Troubleshoot the common failure modes
EADDRINUSE
EADDRINUSE means another server already owns the requested port or path. Node identifies this as the common error when a requested listening endpoint is occupied; the Node net documentation describes the error condition.
- Find the owner:
sudo ss -ltnp | grep ':8080'. - Determine whether it is the old Node process, another application, or a duplicate service instance.
- Stop or reconfigure the process that should not own the port.
- If both services are required, assign distinct ports and update the appropriate proxy target.
- Restart the intended supervisor and verify its logs.
Do not repeatedly restart until the conflict is understood; that can obscure which service is binding successfully.
Connection refused
A refusal generally means the destination address is reachable but no process is accepting connections there. Check, in order:
- Did the supervisor actually restart, or is the old process still running?
- Did Node crash during startup? Read the service status and logs.
- Is Node bound only to loopback while you are testing an external address?
- Are you testing the correct port and protocol?
Internet requests time out
A timeout can occur before traffic reaches Node. Verify the provider firewall, guest firewall, routing, and bind address. Compare an external test with a local curl request; if local works but external traffic times out, concentrate on network policy and reachability rather than application code.
NGINX returns 502 or 504
These statuses usually indicate that NGINX cannot obtain a timely response from its upstream. Confirm that:
- Node is running and listening on the exact host and port in
proxy_pass. - The private address is reachable from the NGINX process.
- NGINX configuration passes
sudo nginx -t. - NGINX was reloaded after the upstream edit.
- Both NGINX’s error log and the Node journal show the same timestamped request.
It works in an interactive shell but not under systemd
Interactive shells and systemd can use different users, working directories, executable paths, permissions, and environment variables. Put PORT=8080 in the unit’s Environment or referenced EnvironmentFile, use absolute paths where appropriate, and restart the unit. Inspect the effective definition with systemctl cat rather than assuming your shell configuration is inherited.
Port-change decision checklist
Use this sequence for a repeatable deployment:
- Identify the real entry point and supervisor.
- Decide whether Node is public or private behind NGINX.
- Read the port from
process.env.PORTand validate it. - Choose a free TCP port that is not already owned by another service.
- Set the value in the supervisor, not only in an interactive shell.
- Restart the supervisor that creates the Node process.
- Confirm the Node PID and listening address with
ss. - Update NGINX’s upstream if a reverse proxy is used, then test and reload NGINX.
- Align provider and guest firewall rules with the chosen exposure model.
- Test locally, then test the public hostname or address from outside the VPS.
The change is complete only when the running Node process, the bind address, the supervisor environment, the firewall policy, and any reverse-proxy upstream all describe the same endpoint.
Quick Recap
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.
