Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRun each Node.js application on its own private localhost port, then let NGINX accept public HTTP and HTTPS traffic and reverse-proxy each request to the correct port. Use URL prefixes such as example.com/app1/ when one hostname should expose several services, or separate subdomains such as app1.example.com when each application should behave as if it owns the root path. NGINX handles TLS, routing, client headers and WebSocket upgrades while a process supervisor keeps the Node services running.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The architecture: one public listener, many private Node.js services
A domain does not need a separate public port for every application. NGINX can listen on ports 80 and 443, while the applications listen only on loopback addresses such as 127.0.0.1:3001, 127.0.0.1:3002 and 127.0.0.1:3003. A request arrives at NGINX, NGINX selects a server block and location, then proxies the request to the matching local service.
As an Amazon Associate I earn from qualifying purchases.
This arrangement gives you one place for certificates, HTTP-to-HTTPS redirects, access logging and firewall exposure. The Node processes remain unreachable from the public internet unless you deliberately bind them to another interface or publish their ports.
Request flow
- A browser resolves your domain or subdomain through DNS to the server running NGINX.
- NGINX accepts the connection on port 80 or 443. For HTTPS, it decrypts TLS using the certificate configured in the relevant
serverblock. - NGINX matches the hostname and URL path. NGINX documentation describes
proxy_passas the directive used inside alocationto pass a request to an HTTP proxied server. - NGINX forwards the request to a local Node.js port, preserving the headers your application needs.
- The Node application returns a response, and NGINX sends it back to the client.
Choose URL paths or subdomains before configuring NGINX
Both designs can run several applications on one domain, but they impose different requirements on routing, cookies, assets and operations. Decide first; changing later can require changes in application-generated URLs and client-side storage.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
| Criterion | Path prefixes | Subdomains |
|---|---|---|
| Example | example.com/app1/ and example.com/app2/ |
app1.example.com and app2.example.com |
| NGINX structure | One server_name with multiple location blocks |
Separate server blocks, each with its own server_name |
| Application base path | Each app must generate links, scripts and redirects that work below its prefix | Each app can normally assume it runs at / |
| Cookie scope | Cookies can be limited to an application path, reducing overlap | Cookies are naturally separated by host unless deliberately shared across subdomains |
| URL clarity | Compact single-host URLs; useful when services are part of one site | Clear ownership and simpler links for independent products |
| DNS and certificates | One DNS name and certificate coverage for that host | DNS records and certificate coverage are needed for every hostname, or a suitable wildcard certificate |
| Local development | Requires testing the prefix behavior, not just localhost/ |
Requires local hostnames or equivalent development routing |
| Root-path assumptions | Problematic for apps that hard-code absolute URLs beginning with / |
Best when an app safely owns the root path |
Choose prefixes when the applications are components of one hostname and can be configured with a base path. Choose subdomains when services are independently developed, use their own root-relative assets, or need separate cookie and security boundaries.
Prepare each Node.js application
Give every app a distinct local port
Configure the first service to listen on 127.0.0.1:3001 and the second on 127.0.0.1:3002. The exact environment-variable names depend on your code, but the important properties are that ports do not collide and listeners are private.
# Example process environment values
PORT=3001 node app1.js
PORT=3002 node app2.jsDo not make both applications listen on the same port. If a process fails with an address-in-use error, identify the conflicting listener, stop or reconfigure it, and start the service again. Keep each app’s environment configuration, logs and working directory distinct so a deployment or restart cannot accidentally affect another service.
Make prefix-based apps aware of their public path
With /app1/, the browser receives URLs containing that prefix. Your application must therefore generate links, redirects, API endpoints and static-asset URLs that include /app1/, or use relative URLs that remain valid below it. Client-side routers often have a configurable base or basename; set it to the public prefix.
Test the built application at the real prefix, not only by opening the backend directly on port 3001. A page that loads at http://127.0.0.1:3001/ can still fail at https://example.com/app1/ if its JavaScript bundle is requested from /assets/main.js instead of /app1/assets/main.js.
Configure path-based routing on one hostname
The following configuration sends /app1/ to port 3001 and /app2/ to port 3002. The upstream names keep backend details separate from routing rules and make later scaling easier.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
http {
upstream app1_backend {
server 127.0.0.1:3001;
}
upstream app2_backend {
server 127.0.0.1:3002;
}
server {
listen 80;
server_name example.com;
location /app1/ {
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_pass http://app1_backend/;
}
location /app2/ {
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_pass http://app2_backend/;
}
}
}Place the upstream definitions in the HTTP context and adapt the configuration layout to your distribution’s NGINX include files. Replace example.com with the hostname that resolves to this server. In production, the same locations normally appear in an HTTPS server block after you configure certificates and an HTTP redirect.
Why the trailing slash in proxy_pass matters
When proxy_pass includes a URI, NGINX replaces the part of the original request URI that matched the location. In the example, a request for /app1/login is sent upstream as /login, because the matching /app1/ portion is replaced by the slash in http://app1_backend/.
If you omit the URI and write proxy_pass http://app1_backend;, NGINX forwards the full request URI, so the backend receives /app1/login. Use the form that matches your application’s router. An app configured to run at its own root generally needs the trailing slash form; an app explicitly expecting the prefix may need the full URI instead.
Also account for the prefix without a trailing slash. A request to /app1 may not match location /app1/ exactly. Add a deliberate redirect or exact location if you want /app1 to become /app1/, rather than relying on accidental behavior.
Recommended Free Tools
Location matching and overlaps
NGINX selects the longest matching prefix when several prefix locations apply. Keep application prefixes distinct, such as /app1/ and /app2/, and avoid a broad catch-all location that unintentionally captures an application’s traffic. If you add locations for health checks, assets or APIs, verify which block wins for every URL.
Configure subdomains when each app owns the root path
Subdomains remove most prefix-related application work. Create DNS records for each hostname and configure a separate NGINX server block for each one. Both blocks can listen on the same public ports because the hostname selects the block.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
http {
upstream app1_backend {
server 127.0.0.1:3001;
}
upstream app2_backend {
server 127.0.0.1:3002;
}
server {
listen 80;
server_name app1.example.com;
location / {
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_pass http://app1_backend;
}
}
server {
listen 80;
server_name app2.example.com;
location / {
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_pass http://app2_backend;
}
}
}Here the upstream URL has no trailing URI, so NGINX forwards the complete request URI. Because each application receives requests beginning at /, this is usually the least surprising arrangement for frameworks and static-file servers.
Forward the headers applications actually need
The sample sets three headers deliberately. Host lets the app know which public hostname the client requested. X-Real-IP carries the immediate client address, and X-Forwarded-For preserves the proxy chain for logs and request policies. Without these values, an application may create links for an internal hostname, record NGINX’s address as every client, or apply incorrect host-based logic.
Ensure your framework is configured to trust forwarded headers only from your NGINX proxy or trusted network. Blindly trusting client-supplied forwarding headers can allow forged addresses and host information.
WebSocket support
WebSockets require an HTTP/1.1 connection and the upgrade headers to pass through NGINX. Add the following directives to the location that serves the WebSocket endpoint (or to each proxied location if the app upgrades connections on arbitrary paths):
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";Use the same original-host and client-address headers shown earlier. Test an actual WebSocket handshake after deployment; a normal page request can succeed even when upgrades are being rejected. Increase read timeouts only for applications that maintain long-lived connections, and choose a value based on the app’s heartbeat and idle behavior rather than applying an unnecessarily large timeout everywhere.
Terminate TLS and redirect HTTP at NGINX
Keep certificates at the reverse-proxy layer so the public interface has one consistent HTTPS policy. A common arrangement is a port-80 block that redirects to HTTPS and a port-443 block containing the proxy locations and certificate directives.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
server {
listen 80;
server_name example.com;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl;
server_name example.com;
ssl_certificate /path/to/fullchain.pem;
ssl_certificate_key /path/to/private-key.pem;
location /app1/ {
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_pass http://app1_backend/;
}
location /app2/ {
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_pass http://app2_backend/;
}
}For subdomains, provide certificate coverage for each hostname and put the corresponding server_name and proxy rules in each HTTPS block. Do not expose the Node ports merely because NGINX has TLS; bind the applications to localhost and allow only the intended public ports through the firewall.
Keep multiple Node processes running with a supervisor
NGINX only routes traffic; it does not restart a crashed Node process. Run each application under a supervisor such as PM2, with separate names, environment values and logs. A basic single-instance start might look like:
pm2 start app1.js --name app1
pm2 start app2.js --name app2Persist the process list according to your operating system’s PM2 setup so services return after a reboot. Confirm that the supervisor starts each app in the correct working directory and supplies the intended port.
Use PM2 cluster mode only when the app is suitable
PM2 can distribute a networked Node.js application across available CPUs without code changes:
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 →Clear out junk files and repair common Windows errorsFree Scan →pm2 start app.js -i maxCluster mode creates multiple instances behind one logical application. PM2’s load-balancing guidance requires the application to be suitable for stateless scaling. Do not keep sessions, upload state, caches or other user-specific data only in one process’s memory. Use an external store or another persistence strategy, and make sure every instance can access shared files and configuration when necessary.
| Deployment choice | Benefits | Costs and risks |
|---|---|---|
| One process per app | Simpler debugging, isolated restarts and straightforward per-app logs | One process uses one event loop; a crash or blocked process affects that app until restarted |
| PM2 cluster mode | Uses multiple CPUs and can improve throughput without changing the public NGINX route | Requires stateless behavior, shared session/state handling and more complex observability |
Scale an app behind a named upstream
A named upstream can contain several backend instances. NGINX’s default upstream algorithm is round robin, so successive requests are distributed among the listed servers.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
upstream app1_backend {
server 127.0.0.1:3001;
server 127.0.0.1:3002;
}
server {
listen 80;
server_name example.com;
location /app1/ {
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_pass http://app1_backend/;
}
}Only place independent instances in the same upstream when they serve the same application and can handle any request. If sessions remain in memory, a user may be sent to a different instance on the next request and appear logged out. Solve that state problem before enabling multiple backends; NGINX routing alone does not make an application horizontally scalable.
Validate configuration and deploy safely
- Check that DNS for the domain or subdomains resolves to the NGINX host.
- Confirm each Node process is listening on the expected localhost port and is healthy when queried locally.
- Run NGINX’s configuration test before applying a change:
nginx -t. - Reload NGINX only after the test succeeds, for example with your operating system’s service manager:
systemctl reload nginx. - Request every public path and hostname over HTTPS. Test the prefix with and without its trailing slash, ordinary pages, redirects, static assets and API calls.
- If an app uses WebSockets, test the upgrade path separately and observe whether the connection stays open for the expected period.
- Review NGINX error and access logs together with the relevant application’s logs. A 502 usually means NGINX cannot connect to the configured backend; an application-level 404 or asset error often means the URI prefix or router base is wrong.
Troubleshoot the failures that occur most often
502 Bad Gateway
- Verify the Node process is running and listening on the exact address and port in the
upstream. - Check that the process did not bind only to a different interface or exit because of a missing environment variable.
- Read the NGINX error log for connection-refused, timeout or name-resolution details.
Every app displays the same service
- For paths, check that each
locationpoints to a different upstream and that a broader location is not winning. - For subdomains, confirm the request’s Host header reaches the intended
server_nameblock and that DNS records are correct.
HTML loads but JavaScript or CSS returns 404
The app is probably generating root-relative asset URLs while it is published below a prefix. Configure the framework’s public base path, adjust the static asset base URL, or move the app to a subdomain where it can own /. Also inspect whether the trailing slash in proxy_pass is stripping a prefix the backend expects.
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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRedirects point to localhost or HTTP
Ensure the original Host header is forwarded and that the application understands it is behind an HTTPS proxy. The TLS connection ends at NGINX, so the app must use the forwarded scheme information supported by its framework when deciding whether a request was secure.
WebSocket connection closes immediately
Check proxy_http_version 1.1, the Upgrade and Connection headers, and the location that handles the upgrade. Then inspect timeout values and both logs for handshake or authentication errors.
Users lose sessions after enabling multiple instances
In-memory sessions are tied to one process. Move session data to an external shared store or use another persistence design before placing those instances in one upstream. Do not treat sticky routing as a substitute for shared state unless you have evaluated its failure and deployment behavior.
Operational checklist for several apps on one domain
- Each app has a documented localhost port, working directory, environment and supervisor name.
- Node listeners are private; only NGINX’s intended public ports are exposed.
- Path-based apps know their public prefix, including redirects, API calls, static assets and client-side routing.
- Subdomain DNS and certificate coverage match every
server_name. - Every proxied request forwards the original host and client-address headers.
- WebSocket locations pass HTTP/1.1 upgrade headers and use timeouts appropriate to the connection pattern.
- Named upstreams contain only interchangeable instances, with shared session and application state handled externally.
- Configuration changes are tested with
nginx -t, reloaded gracefully, and verified through public requests. - NGINX and application logs are separate enough to identify whether a failure occurred at routing, connection, or application level.
With this design, one NGINX listener can safely front many Node.js applications. URL prefixes centralize several services under one hostname but require prefix-aware applications; subdomains provide cleaner root-path behavior at the cost of additional DNS and certificate management.
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.
