Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
To hide a backend server’s IP address, 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 with host and network firewalls. Header forwarding must also be deliberate: preserve the public host, pass client-IP context, and trust forwarded values only from your controlled proxy path.
A reverse proxy by itself does not hide an origin that remains reachable on an open port. The configuration, firewall rules, DNS migration, TLS settings, and logging policy must all agree on the same trust boundary.
Free tools Windows power users keep installed
One-click scans. No signup required.
What “hiding the backend IP” actually means
In a proxied design, a browser or API client connects to the public NGINX address. NGINX accepts the request, selects an upstream, sends the request to that upstream, receives the response, and returns it to the client. The normal public request path therefore exposes the proxy endpoint rather than the backend address.
This is not an anonymity guarantee. An origin can still be discovered through historical DNS records, certificates, error pages, application-generated URLs, mail records, telemetry, leaked configuration, or an open service port. “Hidden” should mean that the origin has no usable public route and accepts traffic only from approved NGINX or load-balancer addresses.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Choose an origin layout
| Layout | NGINX-to-backend path | Origin exposure requirement | Best fit |
|---|---|---|---|
| Same host, loopback | 127.0.0.1 or a Unix socket |
The application listens only on loopback or its socket; the public interface does not accept the application port. | A single server running NGINX and the application. |
| Private network | A private IP or private DNS name | Security groups, ACLs, and the backend firewall allow the application port only from NGINX’s private address or trusted proxy ranges. | Separate web and application hosts inside one controlled network. |
| Separate origin with an upstream group | Several private servers behind an NGINX upstream definition | Every origin node blocks public access and permits only the proxy or load-balancer network. | High availability, health checks, and horizontal scaling. |
For sensitive data, encrypt and authenticate the private hop as required by your deployment. A private address reduces exposure, but it is not a substitute for transport security when the network or compliance model requires it.
Prerequisites before changing NGINX
- A DNS name such as
api.example.comthat points to the NGINX endpoint, not the application host. - An application listening on a loopback, Unix-socket, or private-network address.
- Administrative access to NGINX, the host firewall, and any cloud security group or network ACL in front of the origin.
- A plan for TLS certificates at the public edge and, when needed, authenticated encryption between NGINX and the upstream.
- A defined list of proxy or load-balancer CIDR ranges that are allowed to supply client-IP replacement headers.
During migration, treat an old public origin as compromised until it is rotated or firewalled. Changing DNS alone does not close an already known address.
Build the minimal reverse-proxy server block
The following HTTP pattern terminates TLS on NGINX and forwards requests to an application on the same host at 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;
}
}Replace the certificate directives and certificate paths with the values used by your NGINX installation. The important forwarding directive is proxy_pass; it sends the request to the specified upstream and returns the upstream response to the client.
1. Point the application at a non-public listener
On the same machine, bind the application to 127.0.0.1 or a Unix socket instead of the public interface. On a separate host, use a private IP or private DNS name. An upstream group is appropriate when several private application nodes must share traffic:
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
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;
}
}Use addresses such as 10.20.0.11 only on a network that is actually private and routed between NGINX and the application. The application nodes must still reject connections from every other source.
2. Validate and reload safely
- Check the syntax with
sudo nginx -t. Do not reload a configuration that reports an error. - Reload NGINX using your service manager, for example
sudo systemctl reload nginx. A reload applies the new workers while allowing existing connections to finish. - Request the public name over HTTPS and verify the expected application response.
- From a machine that is not an approved proxy, attempt to connect to the origin address and application port. The connection should be blocked or have no public route.
Close every direct route to the origin
This is the control that turns proxying into origin protection. The backend port must accept connections only from NGINX’s loopback address, private address, or explicitly trusted proxy network.
Host firewall example
On a Linux host using UFW, a same-host application can deny the application port on external interfaces while retaining loopback access. A separate application host can allow the port only from the NGINX private address:
sudo ufw deny 8000/tcp
sudo ufw allow from 10.20.0.5 to any port 8000 proto tcpHere, 10.20.0.5 is an example NGINX address. Adapt the rule to your actual interface, port, and firewall system. Apply equivalent restrictions in cloud security groups, network ACLs, container policies, and upstream load balancers. If an IPv6 address exists, protect the IPv6 listener as well; securing only IPv4 leaves another possible route.
Application binding and service exposure
- For loopback, bind the application to
127.0.0.1rather than0.0.0.0. - For a Unix socket, set ownership and permissions so only NGINX and the application service can use it.
- For a private host, bind to the private interface and restrict the security group to the exact NGINX or proxy CIDRs.
- Do not publish the origin port in a container, orchestration service, or cloud load balancer unless that publication is intentional and filtered.
Forward headers without creating a trust vulnerability
NGINX changes some proxy headers by default, including Host and Connection. Set the values your application actually needs and suppress a header by assigning it an empty value when that is the desired behavior.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Host and URL construction
proxy_set_header Host $host; passes the public host name to the upstream. This matters when the application selects a virtual host, builds absolute links, validates allowed hosts, or generates redirects. If you instead pass the internal backend name, clients may receive redirects or links that reveal internal naming.
Client-IP context
proxy_set_header X-Real-IP $remote_addr; carries the address NGINX observed for the immediate client. proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; appends that address to the existing forwarding chain. The application can use these values for audit logs, rate limits, and policy decisions only when requests are guaranteed to arrive through the controlled proxy path.
A client who can reach the application directly can forge X-Real-IP or X-Forwarded-For. Blocking the origin route is therefore a prerequisite for treating those headers as meaningful identity data.
Scheme and secure redirects
proxy_set_header X-Forwarded-Proto $scheme; tells the application whether the client connected to NGINX with HTTP or HTTPS. Configure the application to trust this value only from NGINX. Otherwise, an attacker who can reach the application directly may influence generated redirects, secure-cookie decisions, or URL handling.
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 →Configure the real-IP module at a clear trust boundary
Some deployments need NGINX itself to replace the address in $remote_addr using a header supplied by an upstream load balancer. The real-IP module is not a general “trust this header” switch. Define the exact addresses that are known to send correct replacement values with set_real_ip_from, select the header with real_ip_header, and use recursive processing only when the entire proxy chain is understood.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
set_real_ip_from 10.30.0.0/16;
real_ip_header X-Forwarded-For;
real_ip_recursive on;The CIDR above is an example and must be replaced with the actual load-balancer or proxy ranges. If a request arrives from outside those ranges, its forwarded header must not be accepted as authoritative. Keep application, access-control, and logging behavior consistent with the same trust definition.
Handle PROXY protocol end to end
PROXY protocol is a transport feature, separate from ordinary HTTP forwarding headers. A load balancer that sends PROXY protocol prepends connection metadata so NGINX can learn the originating client address even when the TCP source address is the balancer.
Enable it on the matching NGINX listener only when the upstream actually sends it, and configure the corresponding real-IP behavior. If one side expects PROXY protocol and the other side does not, connections can fail or be parsed incorrectly. If it is omitted where required, logs and application decisions may show the proxy address instead of the originating client.
Recommended Free Tools
Get URI mapping right
The URI portion of proxy_pass changes how NGINX maps the request path. With:
location /api/ {
proxy_pass http://127.0.0.1:8000/;
}the matching /api/ prefix is replaced by / when the request is sent upstream. Without the trailing URI in proxy_pass, NGINX forwards the request URI in a different way. Decide whether the application expects /api/orders or /orders, then test nested paths, query strings, encoded characters, redirects, and trailing slashes. Incorrect mapping commonly appears as 404 responses or redirects to an internal path.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Use proxy_bind when source selection matters
If the NGINX host has multiple network interfaces, proxy_bind can select the local source address used for upstream connections. This is useful when the backend firewall allows only one private interface or when routing policies distinguish networks. The bound address must exist on the NGINX host, be routable to the upstream, and be included in the backend’s allowlist.
Add NGINX access controls as a second layer
NGINX can allow or deny client IP addresses or ranges, including in proxied TCP configurations. Use these controls for application-specific restrictions such as an administrative path or an internal API. They complement, rather than replace, network-level origin isolation: a deny rule does not prevent a client from connecting directly to an exposed backend port.
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 errorsPrevent leaks outside the request path
- Remove or protect old DNS records that pointed to the origin. Lowering a DNS record’s TTL does not erase cached or historical data.
- Review certificates and certificate-transparency history for names that may identify the origin.
- Check error pages, debug responses, redirects, generated API URLs, and download links for private hostnames or addresses.
- Inspect mail records, monitoring agents, telemetry endpoints, and deployment files that may publish the backend address.
- Rotate a previously exposed origin address when practical, then enforce the new firewall policy before repointing traffic.
- Ensure health checks use the private route and do not create a new public listener.
Test that clients cannot bypass NGINX
- Resolve the public hostname and confirm that it returns only the NGINX or approved edge addresses.
- From an external network, connect to the old origin address on the application port. It should time out or be rejected by policy.
- Send a request through the public hostname and inspect the application log. It should show the expected client-IP metadata and public host, not an internal redirect.
- Try a direct request with forged
X-Forwarded-ForandX-Real-IPheaders. The application should not accept those values from an untrusted route. - Exercise paths with and without trailing slashes, query parameters, redirects, large request bodies, and authentication cookies.
- If a load balancer is in front of NGINX, test both healthy and failed nodes and verify that PROXY protocol and real-IP processing remain consistent.
Troubleshoot common failures
502 Bad Gateway or connection refused
Confirm that the application is listening on the address and port in proxy_pass, that a Unix-socket path exists and has usable permissions, and that the firewall allows NGINX’s source address. On a multi-interface host, verify routing and any proxy_bind address.
The application sees NGINX instead of the user
Check that the forwarding headers are set, that the application is configured to trust them only from NGINX, and that an upstream load balancer is not overwriting or omitting them. If PROXY protocol is used, verify listener settings on both ends and inspect the real-IP module configuration.
Redirects expose an internal hostname or use HTTP
Pass the public Host and X-Forwarded-Proto, then configure the application’s trusted-proxy settings. Check whether URI rewriting is sending the application a path or host it uses to construct internal redirects.
Direct origin requests still work
Look beyond the NGINX host firewall: inspect cloud security groups, IPv6 rules, container port publications, alternate interfaces, and other load balancers. A single forgotten public listener defeats the concealment goal.
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 matchEvery request fails after enabling PROXY protocol
The listener may be expecting a PROXY header from a sender that still speaks plain TLS or HTTP. Make the setting identical on the sending load balancer and receiving NGINX listener, or remove it from both sides.
Quick Recap
Deployment decision checklist
| Question | Loopback | Private network | Separate origin group |
|---|---|---|---|
| Does the origin have a public route? | No, when bound only to loopback or a socket. | No, when routing and firewalls exclude public interfaces. | No, for every node in the group. |
| Is NGINX-to-backend traffic encrypted? | Usually local; apply your security policy. | Use HTTPS or another authenticated private transport when required. | Use authenticated transport across each private hop when required. |
| How are forwarded headers trusted? | Only from the local NGINX path. | Only from the defined proxy addresses or CIDRs. | Document every proxy hop and enable recursive processing only for a known chain. |
| What needs operational attention? | Socket permissions, local service restarts, and host firewall state. | Routes, security groups, health checks, and private DNS. | Node health, balancing, failover, scaling, and consistent configuration. |
Final security checklist
- NGINX is the only public HTTP or HTTPS endpoint.
- The application listens on loopback, a Unix socket, or a private address.
- Origin ports are blocked by host firewalls, security groups, or ACLs for every untrusted source.
- Public TLS is configured at the edge, with private-hop TLS added when the deployment requires it.
Host,X-Real-IP,X-Forwarded-For, andX-Forwarded-Protomatch the application’s routing and trust model.set_real_ip_fromcontains only known proxy or load-balancer networks.- PROXY protocol is either consistently enabled end to end or consistently absent.
- DNS, certificates, redirects, errors, telemetry, and mail records do not disclose an accessible origin.
- Direct-origin, forged-header, failover, and URI-mapping tests are part of deployment checks.
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.
