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 →To hide a backend server’s IP address behind Nginx, make Nginx the only publicly reachable endpoint, proxy requests to the application over loopback or a private network, and block every direct route to the origin. A reverse-proxy configuration alone is not enough: if the application port remains open to the internet, anyone who discovers the address can bypass Nginx.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The working design has four parts: an Nginx listener for the public hostname, a private upstream address, firewall or security-group rules that admit traffic only from Nginx, and carefully controlled forwarding headers for host names and client-IP logging.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What “hiding the backend IP” actually means
Nginx terminates the public connection, receives the request for a hostname such as api.example.com, sends a new request to the application, receives the response, and returns that response to the client. The client sees Nginx’s address, not the upstream address, during the normal request path.
This is origin isolation, not merely address obfuscation. DNS history, an old certificate, an error page, a mail record, telemetry, an application-generated URL, or an open origin port can disclose the backend. If a previously public origin has been exposed, rotate or firewall it as part of the migration rather than assuming that changing DNS is sufficient.
#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.
Choose an architecture before writing the configuration
The best upstream location depends on where the application runs and how much isolation it needs. These patterns all use the same proxy_pass mechanism, but their failure and security characteristics differ.
| Pattern | Upstream example | Public route to origin | Transport and trust considerations | Operational notes |
|---|---|---|---|---|
| Same host, loopback | 127.0.0.1:8000 or ::1:8000 |
None unless another service exposes it | Traffic stays on the host; firewall the application port anyway if other interfaces or containers can reach it | Simple and fast; Nginx and the application share host resources |
| Separate private host or network | Private DNS name or RFC1918 address | None from the public internet when routing and security groups are correct | Restrict the application to Nginx’s private address; use HTTPS or another authenticated private transport when the data or threat model requires it | Supports independent scaling, but depends on private routing, health checks, and network policy |
| Upstream group | upstream app_pool with several private servers |
None when every member is private | Apply the same firewall and header rules to every member | Allows load balancing and maintenance of individual nodes |
| Unix socket | unix:/run/app/app.sock |
None over the network | Protect the socket path and permissions so only Nginx and the application can use it | Useful for a same-host service; does not solve host compromise |
For any pattern, decide in advance which component is trusted to assert a client address, whether Nginx-to-backend traffic is encrypted, how the application expects the Host and URI to look, and how logs and health checks will identify a failed node.
Prepare the public and private sides
Give Nginx the public name
Point the public DNS record at the Nginx host or at a controlled load balancer in front of Nginx. Do not publish a record that points directly at the application. If the old origin address was public, remove stale records only after the new path works and then enforce network restrictions; DNS removal by itself does not prevent direct connections.
Bind the application privately
Configure the application to listen on loopback, a private interface, a Unix socket, or a private subnet address. Avoid binding it to every interface unless a separate network policy makes that necessary. The address in proxy_pass must be reachable from Nginx but not from untrusted clients.
Install the origin firewall rule
At the host firewall, cloud security group, or network ACL, allow the application port only from the Nginx address or from the exact trusted proxy network. Deny public traffic to that port. If several Nginx nodes or a load balancer can connect, list their specific private addresses or CIDR ranges rather than opening the port broadly. Apply equivalent rules to IPv6; an overlooked IPv6 listener can defeat an otherwise correct IPv4 design.
Keep administrative access separate from the proxy rule. SSH, database, metrics, and orchestration ports should have their own restricted source ranges and should never be made reachable merely because Nginx needs the application port.
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
Build the basic Nginx reverse proxy
Minimal HTTPS edge to a loopback application
The following server block shows the essential forwarding behavior. It assumes TLS certificates are already configured for the public hostname and that the application listens on loopback port 8000.
server {
listen 443 ssl;
server_name api.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_set_header X-Forwarded-Proto $scheme;
proxy_pass http://127.0.0.1:8000;
}
}proxy_pass is the directive that sends the request upstream and returns the upstream response to the client. Replacing the loopback address with a private DNS name, private IP, upstream group, or Unix socket changes the destination without changing the public interface.
Use a private upstream group for multiple servers
Define only private members in an upstream group, then proxy to the group name. This keeps balancing and node replacement in Nginx while the firewall on each member still permits traffic only from the Nginx tier.
upstream app_pool {
server 10.20.0.11:8000;
server 10.20.0.12:8000;
}
server {
listen 443 ssl;
server_name api.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_set_header X-Forwarded-Proto $scheme;
proxy_pass http://app_pool;
}
}Health-check behavior, retry policy, connection limits, and failure handling need to match the application. A private address in an upstream block is not a substitute for a security-group rule on each backend.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Understand URI mapping
The placement of a URI in proxy_pass changes how Nginx maps the matched location to the upstream request. With location /api/ and proxy_pass http://127.0.0.1:8000;, the original URI is passed through. Adding a URI to the proxy target changes the replacement path. Test trailing slashes, redirects, static assets, and API routes explicitly so an apparently hidden origin does not leak through broken redirects or absolute URLs.
Forward the right headers without trusting forged values
Host and scheme
Nginx changes some proxy headers by default. Setting Host $host preserves the public host name for virtual-host routing and application URL generation. X-Forwarded-Proto $scheme tells the application whether the client used HTTP or HTTPS at the edge, which prevents incorrect redirect decisions when TLS terminates at Nginx.
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)
If the application must receive a non-public host name, set that deliberately instead. Do not let an arbitrary client-supplied host value determine password-reset links, redirects, tenant selection, or cache keys without application validation.
Client address headers
X-Real-IP $remote_addr carries the address Nginx sees on the client connection. X-Forwarded-For $proxy_add_x_forwarded_for appends that address to an existing chain. The chain is useful for audit logs, rate limits, and application policy only when every hop that can reach Nginx is controlled.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteA client can send its own X-Forwarded-For header. Therefore, an application must not treat the leftmost or any other value as authoritative merely because the header exists. Requests should reach the application only through the controlled proxy path, and the application or Nginx must define which proxy addresses are trusted.
Use the real-IP module at a defined trust boundary
When another load balancer or trusted proxy sits in front of Nginx, configure the real-IP module with the exact addresses that are allowed to replace the connection address. A representative configuration is:
set_real_ip_from 203.0.113.0/24;
real_ip_header X-Forwarded-For;
real_ip_recursive on;Replace the documentation range above with the actual CIDRs of the trusted proxy or load balancer. The trusted-address list identifies senders known to provide a correct replacement address. Recursive processing should be enabled only when the complete proxy chain is known; otherwise an attacker may inject an address into the chain and influence logs or access controls.
If clients connect directly to Nginx, do not configure every internet address as trusted. Keep the direct connection address as the authority and append it to the forwarding chain.
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 matchRank #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
Configure PROXY protocol consistently
PROXY protocol is a transport feature that carries connection metadata from a load balancer to Nginx. It is separate from an HTTP X-Forwarded-For header. If the load balancer sends PROXY protocol, the Nginx listener must be enabled for it and the real-IP handling must use the matching source. If the sender transmits it but Nginx expects plain HTTP, requests can fail or be parsed as invalid data. If Nginx expects it but the sender does not send it, connections likewise fail.
server {
listen 443 ssl proxy_protocol;
server_name api.example.com;
real_ip_header proxy_protocol;
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_set_header X-Forwarded-Proto $scheme;
proxy_pass http://127.0.0.1:8000;
}
}Use this pattern only when the immediate upstream device is configured to send PROXY protocol and the listener is reachable only from that device. Do not expose a PROXY-protocol listener to ordinary internet clients.
Stop bypasses after the proxy is live
Enforce network isolation
Test the application port from a network that is not the Nginx host. The connection should be refused or filtered. Test both the old public address and every current DNS address, including IPv6. A successful direct response means the origin is still reachable regardless of how correct the Nginx file looks.
Remove disclosure channels
- Search old DNS records and cached deployment documentation for the former origin address.
- Inspect TLS certificates and certificate-transparency records for hostnames that identify the origin.
- Check error pages, response headers, redirects, password-reset links, media URLs, and API payloads for an origin hostname or private address.
- Review mail, monitoring, telemetry, and webhook records that may expose a backend hostname.
- Ensure the application does not generate absolute URLs from an untrusted or internal
Hostvalue.
Disclosure does not always provide a bypass if the firewall is correct, but it gives attackers a target for scanning and configuration mistakes. Treat a formerly public origin as compromised from a network-exposure perspective and rotate credentials or certificates when the incident warrants it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Validate the path before switching all traffic
- Resolve the public hostname and confirm it returns the Nginx address, not the backend address.
- Request the public HTTPS URL and verify the expected application response, redirect behavior, cookies, and generated links.
- Inspect Nginx access logs and application logs. The application should see the Nginx connection unless its trusted-proxy configuration intentionally restores the client address.
- From an external test network, connect to the origin address and application port. Confirm that the firewall blocks the attempt.
- Send requests with a deliberately supplied
X-Forwarded-Forvalue and confirm that your logging and authorization logic do not accept it as a trusted client address when the sender is untrusted. - Exercise large requests, WebSocket or streaming endpoints if used, long-running responses, uploads, and error responses. Proxy timeouts and buffering can expose different failures than a simple homepage request.
- If a load balancer is present, test both ordinary HTTP forwarding and its PROXY-protocol listener separately. Verify that each hop records the same client address according to the documented trust chain.
Common failures and precise fixes
The application returns a redirect to an internal host
Usually the upstream is constructing URLs from the wrong host or scheme. Set Host $host and X-Forwarded-Proto $scheme, then configure the application to trust those headers only from Nginx. Check whether a URI in proxy_pass is rewriting the path unexpectedly.
Logs show only the Nginx or load-balancer address
Check which hop terminates the client connection, whether the sender uses X-Forwarded-For or PROXY protocol, and whether set_real_ip_from lists the exact trusted CIDRs. Do not enable recursive processing until the chain is known. The application may also need its own trusted-proxy setting after Nginx restores the address.
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.
The backend is still reachable directly
Inspect cloud security groups, host firewalls, container-published ports, IPv6 rules, and alternate interfaces. Binding the service to loopback does not protect a second process or container that publishes the same port. Remove public port mappings and allow only Nginx’s source addresses.
Every request fails after enabling PROXY protocol
Confirm that the device immediately upstream sends PROXY protocol on that listener and that no ordinary clients can connect to it. A mismatch must be corrected on both ends; changing only the Nginx listener will not make a plain HTTP stream valid.
Some routes work while assets or APIs return 404
Compare the incoming URI with the URI sent upstream. The presence or absence of a URI component in proxy_pass, and the trailing slash on the location, determine whether Nginx preserves or replaces the matched path. Test representative nested routes rather than only /.
Operational practices for a durable setup
Separate edge, application, and administration policies
Keep public TLS and rate limiting at the edge, application authorization in the application, and administrative access on a separate restricted path. Nginx allow and deny rules can restrict client addresses, including in proxied TCP configurations, but they complement network isolation and do not replace it.
Make logs useful and trustworthy
Record the public host, request ID, upstream status, upstream address, response time, and the client address after the trusted-proxy rules have been applied. Keep the original connection address available for incident analysis. Do not use an unvalidated forwarded header as the sole basis for bans, billing, authentication, or legal audit trails.
Plan for rotation and scaling
When replacing an origin, create the private route first, validate it through Nginx, then change DNS and close the old route. For an upstream group, remove a node from service before maintenance and verify that health checks and retry behavior do not send traffic to a withdrawn address. Keep firewall rules synchronized as Nginx nodes and backend nodes scale.
Deployment checklist
- Nginx is the only public endpoint for the application hostname.
- The application listens on loopback, a Unix socket, or a private network address.
- Origin ports accept connections only from Nginx or the explicitly trusted proxy tier.
- IPv4 and IPv6 exposure have both been checked.
proxy_passpoints to the intended private destination.Host,X-Real-IP,X-Forwarded-For, andX-Forwarded-Protomatch the application’s expectations.- Forwarded headers are trusted only from known proxy addresses.
- PROXY protocol is either disabled end to end or enabled consistently on both sides.
- Redirects, cookies, generated URLs, uploads, streaming, and error pages work through the public hostname.
- Old DNS, certificates, telemetry, and application responses do not disclose an unprotected origin.
- Logs identify the real client only after the trust boundary has been applied.
When these controls are in place, Nginx is not merely hiding an address: it is enforcing a single, auditable path to the backend while preserving the host, scheme, and client context that the application actually needs.
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.
