Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsYes. One Nginx instance can serve a PHP application through PHP-FPM and reverse-proxy a Node.js application at the same time. Nginx remains the only public listener: requests for PHP files go through FastCGI to PHP-FPM, while a separate URL path or hostname is forwarded over HTTP to Node.js.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The reliable setup is to keep the applications’ routing rules explicit, bind Node.js to a local or private port, test the configuration before every reload, and let a service manager keep the Node process alive. The example below uses PHP at example.com and Node.js under /app/, with Node listening on 127.0.0.1:3000.
As an Amazon Associate I earn from qualifying purchases.
How the combined setup works
Nginx does not execute PHP and it does not run JavaScript application code. It dispatches each request to the appropriate upstream service:
- PHP requests: Nginx matches a PHP location and sends the script name and request parameters to PHP-FPM using FastCGI. PHP-FPM executes the script and returns the generated response.
- Node.js requests: Nginx matches a Node-specific path or hostname and sends an HTTP request to the Node process with
proxy_pass. - Static files: Nginx can return CSS, JavaScript bundles, images, and downloads directly from the filesystem without involving either runtime.
This is the normal reverse-proxy model described by NGINX: it sends a request to a specified proxy server, fetches that server’s response, and sends the response back to the client. TLS termination, access logging, compression, request limits, and public firewall exposure can therefore be handled in one place.
#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.
The important distinction is between the handoff directives: fastcgi_pass is for PHP-FPM, while proxy_pass is for an HTTP-speaking Node.js server.
Choose a routing boundary before writing configuration
Decide whether the applications will be separated by URL path or by hostname. Do not let both applications compete for the same location. A clear boundary prevents a broad PHP regular expression or a catch-all location from accidentally capturing Node requests.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Path split: one hostname
With a path split, the PHP site owns the root URL and Node owns a prefix such as /app/. This keeps one domain in browser bookmarks and is convenient when the applications are part of one product.
| Request | Handler | Typical Nginx rule |
|---|---|---|
https://example.com/ |
Static files or PHP front controller | location / and location ~ .php$ |
https://example.com/index.php |
PHP-FPM | PHP regular-expression location |
https://example.com/app/ |
Node.js over HTTP | location ^~ /app/ |
A path split requires the Node application to understand its public base path, or Nginx must remove that prefix before proxying. Browser cookies, links, redirects, and WebSocket URLs also need to be compatible with the chosen prefix.
Hostname split: separate subdomains
With hostnames, the PHP application might use example.com and Node might use app.example.com. Each server block has a single owner, so application routing is easier to reason about. This arrangement is usually preferable when the applications have independent deployment cycles, cookies, security policies, or teams.
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
Separate hostnames do not require separate Nginx installations. They can share the same public IP address and TLS certificate, while each server block forwards to its own upstream.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Prerequisites and deployment layout
You need a server capable of running all three long-lived components:
- Nginx, listening publicly on ports 80 and, when TLS is enabled, 443.
- PHP-FPM, with a Unix socket or TCP listener reachable by Nginx.
- A Node.js application, listening on a local or private port such as 3000 or 8080. The official Nginx Node deployment example uses port 8080; the port itself is not special.
Install and enable the packages using your operating system’s supported method. Service names and PHP-FPM socket paths vary by distribution and PHP version, so inspect the installed service rather than copying a socket name blindly. Typical checks are:
sudo systemctl status nginx
sudo systemctl status php8.3-fpm
sudo ss -ltnp | grep -E ':3000|:8080'
The Node process should answer locally before Nginx is involved:
curl -i http://127.0.0.1:3000/Use an application directory that the Node service can read, and a document root that Nginx can read. For example, the PHP public files might be in /var/www/site/public, while the Node project might live in /var/www/node-app. Do not make the Node project or PHP source tree downloadable by placing it under a publicly served directory unless only the intended built assets are present.
Free tools Windows power users keep installed
One-click scans. No signup required.
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)
Configure PHP-FPM and Node.js in one Nginx file
The following example assumes an Nginx configuration with an http context available for the upstream definition. Put the upstream block inside http { ... }, not inside server { ... }. Replace the PHP socket with the path installed on your host.
http {
upstream nodejs {
server 127.0.0.1:3000;
}
server {
listen 80;
server_name example.com;
root /var/www/site/public;
index index.php index.html;
# Node application owns this prefix.
location ^~ /app/ {
proxy_pass http://nodejs;
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;
}
# Serve existing files and route the rest to the PHP front controller.
location / {
try_files $uri $uri/ /index.php?$query_string;
}
# Send only PHP scripts to PHP-FPM.
location ~ .php$ {
try_files $uri =404;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_pass unix:/run/php/php8.3-fpm.sock;
}
}
}
The try_files $uri =404 check in the PHP location prevents Nginx from passing a nonexistent filename to PHP-FPM. If your framework uses a front controller, the location / block sends unknown paths to index.php; a different framework may require a different fallback.
Understand the trailing slash in proxy_pass
URI handling changes depending on whether proxy_pass includes a path:
proxy_pass http://nodejs;forwards the normalized request URI as received. A request for/app/dashboardreaches Node as/app/dashboard.proxy_pass http://nodejs/;replaces the matching/app/part with/. The same request reaches Node as/dashboard.
Choose one behavior deliberately. If the Node router is mounted at /app, preserve the prefix. If it expects to run at the root of its own server, strip the prefix and configure generated links or public asset paths accordingly. Test a nested route, a redirect, a static asset, and a WebSocket endpoint rather than testing only the home page.
Use a hostname split when the applications are independent
For separate subdomains, create distinct server blocks. The PHP block can keep the normal document root, while the Node block contains only proxy directives:
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
http {
upstream nodejs {
server 127.0.0.1:3000;
}
server {
listen 80;
server_name example.com;
root /var/www/site/public;
index index.php index.html;
location / {
try_files $uri $uri/ /index.php?$query_string;
}
location ~ .php$ {
try_files $uri =404;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_pass unix:/run/php/php8.3-fpm.sock;
}
}
server {
listen 80;
server_name app.example.com;
location / {
proxy_pass http://nodejs;
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;
}
}
}
When TLS is used, terminate it at Nginx and forward the original scheme in X-Forwarded-Proto. Configure the Node framework to trust the proxy only according to its documented setting; otherwise it may generate HTTP URLs behind an HTTPS proxy or misidentify secure cookies.
PHP-FPM transport: Unix socket or TCP
Nginx can connect to PHP-FPM through a local Unix-domain socket or a TCP listener. The application behavior is the same, but the operational trade-off differs.
| Transport | Example | Best fit | Important checks |
|---|---|---|---|
| Unix socket | fastcgi_pass unix:/run/php/php8.3-fpm.sock; |
PHP-FPM and Nginx share the host or filesystem namespace | Socket path, ownership, group permissions, and service startup order |
| TCP | fastcgi_pass 127.0.0.1:9000; |
Separate process namespaces, containers, or a deliberately remote PHP-FPM service | Listener address, firewall rules, reachability, and exposure to untrusted networks |
The exact Unix socket name is distribution- and PHP-version-dependent. A “connect() failed” message usually means the path is wrong, PHP-FPM is stopped, or Nginx lacks permission to open the socket. For TCP, confirm that PHP-FPM is actually listening on the address and port configured in Nginx; do not assume port 9000 is enabled.
Recommended Free Tools
Keep Node.js alive with a service manager
Nginx proxies requests but does not supervise the Node application. If Node exits, Nginx can only return an upstream error until the application is restarted. Run Node with the host’s service manager or an established process manager, and configure startup after reboot and restart after failure.
A systemd-style service commonly needs:
- An explicit, absolute working directory.
- The exact Node executable and start command.
- Environment variables supplied through a protected environment file or service configuration.
- A non-root service account with read and write access only where required.
- A restart policy and a dependency that starts the service after networking is available.
Keep Node bound to 127.0.0.1 when Nginx is on the same host. If Node runs in a container or another private machine, bind it to the private interface and restrict the firewall so that only Nginx can reach it. A public Node port bypasses Nginx’s TLS, access controls, rate limits, and logging, and should be exposed only for a deliberate architectural reason.
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.
Forward the headers and WebSocket connection correctly
At minimum, pass the original host and client address:
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;
For WebSockets, Nginx must preserve the HTTP/1.1 upgrade handshake. Define this map once in the http context and add the two proxy headers in the Node location:
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
location ^~ /app/ {
proxy_pass http://nodejs;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
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;
}
The Node.js application server supports WebSockets without additional Node-specific configuration, but the reverse proxy still has to forward the upgrade headers. Set suitable proxy read and send timeouts for long-lived connections; very short defaults can disconnect an otherwise healthy socket.
Prevent location and filesystem mistakes
Make the Node prefix take precedence
Using location ^~ /app/ tells Nginx to prefer the prefix over regular-expression locations. This matters when a request under /app/ contains a suffix such as .php. Without an intentional precedence rule, a PHP regex could intercept a Node URL.
Do not expose source files
Serve only the PHP public directory. Keep configuration files, dependency directories, source maps, and Node project files outside the Nginx root unless they are intentionally public. The PHP location should pass only existing files and should not allow arbitrary path traversal.
Check permissions as the service accounts
Nginx needs read and directory-traverse permission for static files and the PHP document root. Nginx also needs permission to open the PHP-FPM socket. Node needs permission to read its application and write only to designated runtime directories, such as an upload or cache directory. Fix ownership and groups rather than making the entire tree world-writable.
Deploy safely: an ordered verification procedure
- Verify each backend directly. Run
curl -i http://127.0.0.1:3000/for Node and request a known PHP page through the local web root or a temporary host. Confirm that each service works without Nginx proxying. - Inspect the active Nginx configuration. Ensure the upstream block is in the
httpcontext, the server names are correct, and the PHP socket or TCP endpoint matches the running PHP-FPM service. - Test syntax. Run
sudo nginx -t. Do not reload if the test reports an error; correct the indicated file and line first. - Reload without dropping existing connections. Use
sudo systemctl reload nginxafter a successful test. A reload lets workers finish existing requests while new workers use the validated configuration. - Test both routing boundaries. Request the PHP home page, a dynamic PHP route, a missing PHP script, the Node root, a deep Node route, and a static asset. For a path split, verify whether Node receives
/app/or a stripped/prefix as intended. - Test through the real HTTPS name. Check redirects, secure cookies, absolute URLs, client IP logging, and WebSocket connections after TLS is enabled.
- Watch all three logs while testing. Review the Nginx error and access logs, the PHP-FPM log, and the Node service log. The first upstream that reports an error usually identifies the failing layer.
Troubleshoot common failures
| Symptom | Likely cause | What to check |
|---|---|---|
| 502 Bad Gateway for Node | Node is stopped, listening on another port, or unreachable | systemctl status for the Node service, ss -ltnp, and a direct curl to the upstream address |
| 502 Bad Gateway for PHP | Wrong socket path, stopped PHP-FPM, or socket permissions | PHP-FPM status, configured socket/listener, and Nginx error log |
| Node receives the wrong path | proxy_pass trailing-slash behavior does not match the app’s base path |
Compare requests with and without a URI in proxy_pass; inspect Node access logs |
| PHP source downloads or returns a file | PHP location is missing, malformed, or not reaching PHP-FPM | Confirm location ~ .php$, fastcgi_pass, and nginx -t |
| Every unknown PHP route returns 404 | Front-controller fallback is absent or incorrect | Adjust try_files in the general location for the framework in use |
| WebSocket closes immediately | Upgrade headers or timeouts are missing | Use proxy_http_version 1.1, the upgrade map, and suitable read timeouts |
| Client IP is always the proxy address | Forwarded headers are not set or the application does not trust the proxy | Pass X-Real-IP/X-Forwarded-For and configure trusted proxies carefully |
| Changes have no effect | The edited file is not included, or Nginx was not reloaded | Inspect the full loaded configuration, run nginx -t, then reload and check the reload status |
Security and operational considerations
- Expose one edge: allow public traffic to Nginx and keep Node and PHP-FPM private whenever possible.
- Limit request size and timeouts: set upload limits and upstream timeouts appropriate to the applications instead of accepting unlimited bodies or indefinitely stalled requests.
- Protect secrets: environment files, database credentials, private keys, and service tokens should not be inside the public document root or readable by the Nginx worker.
- Separate logs: include the host and upstream status in access logs so PHP and Node failures can be distinguished quickly.
- Use least privilege: run Node and PHP-FPM as dedicated non-root accounts where the distribution supports it, and grant write access only to required directories.
- Plan graceful deployments: restart or reload the Node service with a method that allows active requests to finish, and verify health before directing traffic to a new version.
If traffic grows, the same upstream abstraction can contain multiple Node servers. Nginx can distribute requests among them and mark failed upstream attempts according to its passive health behavior. That does not replace application health checks, database failover, or a deployment strategy; it only changes how Nginx selects reachable backends.
Path split or hostname split: a practical decision
| Choose a path split when… | Choose a hostname split when… |
|---|---|
| The applications should appear under one public domain. | Each application has independent ownership or release schedules. |
| The Node app can run with a known base path or you can rewrite the prefix deliberately. | The Node app assumes it owns the root path and should not be adapted for a subdirectory. |
| Shared cookies and same-origin browser behavior are useful. | Separate cookies, CSP policies, or authentication boundaries are preferable. |
| You want one URL namespace and are prepared to test location precedence. | You want simpler Nginx routing and clearer application boundaries. |
Neither option requires PHP and Node to share a process. They remain separate runtimes with separate logs and restart policies; Nginx is the coordinating entry point.
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.
