The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Put each subdomain in its own Nginx server block, point that block’s proxy_pass at the correct application port, then use Certbot’s Nginx plugin to issue and install a certificate for the exact hostname. Keep port 80 available for the ACME challenge, test the configuration with nginx -t, and reload Nginx only after the test succeeds.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What the finished setup looks like
Assume a server hosts two applications:
app1.example.comlistens locally on port3001.app2.example.comlistens locally on port3002.
Nginx is the public entry point. It accepts HTTP and HTTPS traffic, selects a virtual server by the requested hostname, terminates TLS for that hostname, and forwards the request to the matching private application. The browser never needs to know the backend port.
As an Amazon Associate I earn from qualifying purchases.
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 minuteThe important design rule is one HTTPS server block per subdomain. Every block has its own server_name and proxy_pass, so a request for one hostname cannot accidentally reach another application’s port.
Prerequisites to verify first
DNS must point every name at this server
Create an address record for each subdomain, such as an A record for IPv4 or an AAAA record for IPv6. Before requesting a certificate, verify that the public DNS result is the address of the Nginx host. Certificate validation will fail if the name resolves somewhere else, if only an unreachable IPv6 address is published, or if DNS changes have not propagated.
#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.
Check each name from a client outside the server’s network. For example:
dig +short app1.example.com
dig +short app2.example.com
Use the resulting addresses to confirm that the request can actually reach this machine, not merely that a DNS record exists.
Recommended Free Tools
Open the required ports
- TCP 80: required for normal HTTP requests and the HTTP-01 ACME challenge.
- TCP 443: required for HTTPS clients after the certificate is installed.
Allow both ports in the host firewall and any cloud security group or edge firewall. The application ports, such as 3001 and 3002, should normally remain bound to localhost or protected from the public internet; clients should reach them through Nginx.
Confirm the software and privileges
You need Nginx, a running backend for each subdomain, a shell account with permission to use sudo, and Certbot with its Nginx plugin. Package names vary by distribution. Check the installed Certbot release before following a command exactly:
certbot --version
nginx -v
systemctl status nginx
Certbot documentation has appeared in both 5.8.0 stable and 5.9.0 development versions; options can differ between releases, so use the syntax supported by the version installed on your server.
Understand the Nginx directives involved
| Directive | Purpose | Where it belongs |
|---|---|---|
listen |
Chooses the local TCP port, normally 80 or 443. | server |
server_name |
Matches the requested hostname. | server |
ssl_certificate |
Points to the public certificate chain. | HTTPS server |
ssl_certificate_key |
Points to the private key for that certificate. | HTTPS server |
location |
Matches a URI path and holds request handling rules. | server |
proxy_pass |
Sets the protocol, destination address, optional port, and optional URI for the proxied request. | location |
proxy_set_header |
Overrides headers sent to the backend, including the original host and forwarding information. | location |
The syntax is proxy_pass URL;. The URL can use http or https, a domain name or IP address with an optional port, or a Unix-domain socket. If the URL includes a URI path, Nginx replaces the part of the incoming request URI that matched the location parameter. That trailing-path behavior is a frequent source of unexpected 404s, so decide deliberately whether the backend should receive the original path or a rewritten one.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Create a plain HTTP configuration first
Start with port 80. This gives Certbot a reachable virtual host and leaves the ACME challenge directory available while the certificate is being issued. Put the following in the site configuration for app1.example.com (the exact directory differs by distribution):
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
server {
listen 80;
server_name app1.example.com;
location /.well-known/acme-challenge/ {
root /var/www/certbot;
}
location / {
return 301 https://$host$request_uri;
}
}
Create the challenge directory and ensure the Nginx worker can read it:
sudo mkdir -p /var/www/certbot
sudo nginx -t
sudo systemctl reload nginx
Repeat the HTTP block with app2.example.com as the server_name. Do not let a catch-all virtual host intercept the challenge request for a named subdomain.
Before running Certbot, request a test file and confirm it is reachable over plain HTTP:
echo ok | sudo tee /var/www/certbot/health-check
curl -i http://app1.example.com/.well-known/acme-challenge/health-check
The response should be successful and contain ok. Remove the test file after validation if it is no longer needed.
Issue and install the certificate with Certbot
Use the Nginx plugin for an exact hostname
Run Certbot once for each exact subdomain:
sudo certbot --nginx -d app1.example.com
sudo certbot --nginx -d app2.example.com
The --nginx option performs two jobs: it proves control of the name and obtains a certificate, then it can edit the Nginx configuration to install the certificate. During the interactive run, choose the option that redirects HTTP traffic to HTTPS when prompted, unless another application intentionally needs unredirected HTTP.
Certificates and key material are normally placed below /etc/letsencrypt/live/. A successful run commonly creates a directory such as /etc/letsencrypt/live/app1.example.com/ containing fullchain.pem and privkey.pem. Confirm the actual paths and generated directives on this machine rather than assuming a filename from another distribution.
Back up before allowing automated edits
Save the current Nginx configuration before Certbot changes it:
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)
sudo cp -a /etc/nginx /etc/nginx.backup-$(date +%F)
If the plugin produces an unusable configuration, Certbot provides a rollback operation:
sudo certbot --nginx rollback
Review the resulting files after every automated change. Certbot can add the HTTPS listener and redirect, but it cannot know the correct backend port or application-specific headers unless those rules are already present.
Build the HTTPS reverse-proxy block
After the certificate exists, the HTTPS block for app1.example.com can look like this:
server {
listen 443 ssl;
server_name app1.example.com;
ssl_certificate /etc/letsencrypt/live/app1.example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/app1.example.com/privkey.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
location / {
proxy_pass http://127.0.0.1:3001;
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 options-ssl-nginx.conf include and ssl-dhparams.pem path are common Certbot-generated items, not universal filenames. Keep the paths Certbot created for the installed package, and remove or correct an include only after confirming what exists on the server.
The second subdomain uses the same structure but its own certificate path and backend:
server {
listen 443 ssl;
server_name app2.example.com;
ssl_certificate /etc/letsencrypt/live/app2.example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/app2.example.com/privkey.pem;
location / {
proxy_pass http://127.0.0.1:3002;
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;
}
}
Keep the corresponding port-80 block for each name. It should serve /.well-known/acme-challenge/ and redirect other requests to HTTPS. A certificate is tied to hostnames, so a certificate for app1.example.com does not automatically cover an unrelated subdomain unless that name is included in the certificate request.
Forward the headers applications need
Nginx changes some proxy headers by default, including Host and Connection, and drops headers whose values are empty. Explicit forwarding rules let the application reconstruct the original request:
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
Host $hostpreserves the public hostname used for routing, redirects, and virtual-host logic.X-Real-IP $remote_addrpasses the direct client address.X-Forwarded-For $proxy_add_x_forwarded_forappends the client address to an existing proxy chain.X-Forwarded-Proto $schemetells the application that the browser used HTTPS, even though the Nginx-to-app hop uses plain HTTP.
Configure the application framework to trust these headers only from your Nginx proxy. Blindly trusting client-supplied forwarding headers can allow address or scheme spoofing when the backend is reachable directly.
Free tools Windows power users keep installed
One-click scans. No signup required.
Support WebSockets and long-lived connections
Interactive dashboards, game backends, chat services, and Socket.IO-style applications may upgrade an HTTP request to a WebSocket. Add an HTTP/1.1 proxy and upgrade headers inside the relevant location:
location / {
proxy_pass http://127.0.0.1:3001;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header 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;
}
Use these headers for the location that handles the upgraded endpoint. If a normal HTTP endpoint does not need WebSockets, avoid applying upgrade behavior globally without understanding how the application treats the Connection header.
Choose the correct proxy_pass path
Preserve the incoming URI
With this pairing, a request for /players?id=4 reaches the backend with the same path and query string:
location / {
proxy_pass http://127.0.0.1:3001;
}
Because the address has no URI component, Nginx forwards the request URI as received.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesReplace a matching prefix
If the application is mounted under a different internal path, include a URI in proxy_pass:
location /api/ {
proxy_pass http://127.0.0.1:3001/v1/;
}
Here, the part matching /api/ is replaced with /v1/. A request for /api/players therefore becomes /v1/players at the backend. Slashes matter; test both the root path and nested paths after changing this form.
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.
Proxy to an HTTPS backend
The protocol in the directive controls the Nginx-to-backend connection. To use TLS on that private hop, change the destination to an https URL and configure any required upstream certificate verification separately. Public browser TLS and upstream TLS are independent: the certificate served to visitors does not automatically authenticate the backend connection.
Validate and reload safely
Always validate syntax before a reload:
sudo nginx -t
A successful test reports that the configuration syntax is valid and the test is successful. Only then apply it:
sudo systemctl reload nginx
A reload lets existing connections finish while workers adopt the new configuration. If nginx -t reports an error, do not reload. Check the referenced line, certificate path, include file, semicolon, brace, and duplicate listener, then run the test again.
Test each hostname independently:
curl -I http://app1.example.com/
curl -I https://app1.example.com/
curl -I https://app2.example.com/
The HTTP request should redirect if that is the policy you selected. The HTTPS response should come from the intended application, not from a default Nginx page or another subdomain’s backend.
Renewal and certificate lifecycle
Certbot obtains certificates with a limited lifetime and normally installs a scheduled renewal mechanism. Depending on the distribution and package, that mechanism may be a systemd timer or a cron job. Inspect what your installation provides:
systemctl list-timers | grep -i certbot
sudo crontab -l
ls -la /etc/cron.* 2>/dev/null | grep -i certbot
Run a dry run to verify that renewal, validation, and the deployment hooks work without replacing the live certificate:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
sudo certbot renew --dry-run
Schedule monitoring for failures and confirm that Nginx can reload after a renewed certificate is deployed. Keep port 80 reachable for the validation method being used.
Do not rely on automatic renewal when the certificate was issued with Certbot’s manual authentication plugin and later installed with the Nginx plugin. The manual authentication step requires human intervention, so that certificate will not renew automatically in the normal way.
Troubleshoot by symptom
Certbot cannot validate the domain
- Confirm the subdomain resolves publicly to this server.
- Check that TCP port 80 is open at every firewall layer.
- Ensure the port-80
server_namematches the requested name. - Make sure
/.well-known/acme-challenge/is not redirected to an application that hides the challenge file. - Run
nginx -tand reload after correcting the block.
HTTPS shows the wrong certificate or site
- Inspect every
server_namelistening on port 443 for duplicates or unintended wildcards. - Verify that the certificate directory contains the requested hostname.
- Check that the client is connecting to the expected DNS address, including IPv6.
- Confirm the TLS block and its certificate paths are in the configuration Nginx actually loaded.
The browser returns 502 Bad Gateway
- Check that the application is running and listening on the port in
proxy_pass. - From the Nginx host, request the backend directly:
curl -i http://127.0.0.1:3001/. - Verify the backend protocol. Using
https://for an HTTP-only service, or vice versa, prevents a successful connection. - Read the Nginx error log and the application’s log for connection refusals, timeouts, or application startup errors.
Routes or redirects contain the wrong path or scheme
- Review whether
proxy_passincludes a URI suffix; that determines prefix replacement. - Ensure the application receives
HostandX-Forwarded-Proto. - Configure the application to trust the proxy before enabling secure-cookie or HTTPS-only redirect logic.
WebSockets disconnect immediately
- Add
proxy_http_version 1.1,Upgrade, andConnection "upgrade"to the WebSocket location. - Check that the application endpoint and public path are identical after any URI replacement.
- Test the normal HTTP request and the upgraded endpoint separately.
Operational checklist for additional subdomains
- Create DNS records and verify public resolution.
- Start the application on a distinct local port or socket.
- Add a port-80 block with the exact
server_nameand reachable ACME challenge path. - Run
sudo nginx -t, reload, and confirm the challenge URL can be fetched. - Run
sudo certbot --nginx -d your-subdomain.example.com. - Review the generated certificate paths and HTTPS listener.
- Set the correct
proxy_passdestination and forwarding headers. - Add WebSocket directives only where the application requires them.
- Run
sudo nginx -tagain, then reload. - Test HTTP redirect, HTTPS content, backend routing, and renewal with
sudo certbot renew --dry-run.
This repeatable layout keeps certificate scope, hostname routing, and backend ownership clear as the number of game services or other applications grows.
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.




