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 minuteA VPN-only VPS has one intentional public entry point: the VPN listener. SSH, databases, dashboards, APIs, and administration tools accept connections only through the encrypted tunnel, not from the open internet. The reliable way to build it is with two matching firewall layers: your VPS provider’s cloud firewall and a host firewall inside the server.
Antihost offers VPS plans with one-click OpenVPN, NVMe storage and a 14-day free trial.
This guide uses WireGuard, a fast, modern VPN implementation documented by Ubuntu. You will create a private tunnel subnet, expose only a WireGuard UDP port, restrict services to the wg0 interface or VPN subnet, keep a temporary recovery path during rollout, and remove that path only after testing from both inside and outside the VPN.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →What “accessible only through a VPN” actually means
A public VPS still needs one reachable port so VPN clients can establish a tunnel. “VPN-only” therefore does not mean the server has no public IP or no public port. It means that the public IP answers only on the WireGuard UDP listener; every other administrative or application service is denied on the public interface.
The design has four parts:
- Public VPS address: used only to reach the VPN endpoint.
- WireGuard tunnel: a separate interface, normally named
wg0, with its own private address range. - Provider firewall: the cloud security group or network firewall that filters traffic before it reaches the virtual machine.
- Host firewall: the Linux firewall that enforces the same policy inside the VPS.
A connection to SSH at the public address should fail. The same SSH service should work when a peer connects to the VPS’s tunnel address. The same rule applies to databases, monitoring panels, internal APIs, and any other service that is not deliberately public.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Ubuntu describes WireGuard as “a simple, fast and modern VPN implementation.”
Prepare recovery access before changing anything
Firewall changes can cut off the session you are using to make them. Before installing WireGuard or changing inbound rules, open a second administration session and verify that your provider’s out-of-band console or serial console works.
- Keep your current SSH session open.
- Open the provider console in a separate browser tab and log in successfully.
- Record the fixed public address from which you administer the server, if you have one.
- Back up the current firewall rules and the existing WireGuard or network configuration, if any.
- Have a tested client device ready to become the first VPN peer.
During rollout, allow SSH from only that fixed administration address or leave SSH reachable through the provider console. Do not remove this emergency path until the VPN handshake, tunnel routing, SSH login, and private services have all been tested.
Choose the tunnel range and exposure policy
Use a private range that does not overlap with networks where your clients will connect. The examples below use 10.80.0.0/24. If your home, office, or mobile network already uses that range, choose another unused private range instead.
| Component | Example address or port | Internet exposure | Purpose |
|---|---|---|---|
| VPS public address | Provider-assigned public IPv4 or IPv6 | Addressable, but filtered | WireGuard endpoint and temporary recovery access |
| WireGuard interface | 10.80.0.1/24 |
Private tunnel only | VPS address used by VPN clients |
| First peer | 10.80.0.2/32 |
Private tunnel only | Unique client address |
| WireGuard listener | UDP 51820 |
Only intentionally public port | Encrypted tunnel establishment |
| SSH | TCP 22 |
wg0 or VPN subnet only |
Administration over the tunnel |
| Application ports | For example TCP 443, 5432, or 8080 |
wg0 or VPN subnet only |
Private web, database, or API access |
WireGuard uses UDP. Do not open TCP 51820 expecting it to work; permit UDP on the port you actually configure. You can choose a different UDP port, but the provider firewall and the server configuration must match.
Install WireGuard on Ubuntu or Debian
On a current Ubuntu or Debian VPS, install the distribution packages while logged in through your temporary recovery path:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
sudo apt update
sudo apt install wireguardDo not paste private keys into shell history, tickets, chat messages, or public issue trackers. The key files should be readable only by root. Generate the server key pair with a restrictive umask:
sudo -i
umask 077
wg genkey | tee /etc/wireguard/server.key | wg pubkey > /etc/wireguard/server.pub
exitGenerate a separate key pair for every client. A client’s private key stays on that client; only its public key is copied to the VPS. Never reuse one private key for several people or devices.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
umask 077
wg genkey | tee client1.key | wg pubkey > client1.pubCreate the WireGuard server configuration
Create /etc/wireguard/wg0.conf as root. Replace the example key values with the contents of the files you generated. Each peer must receive a unique tunnel address and a matching AllowedIPs host route.
[Interface]
Address = 10.80.0.1/24
ListenPort = 51820
PrivateKey = SERVER_PRIVATE_KEY
[Peer]
PublicKey = CLIENT1_PUBLIC_KEY
AllowedIPs = 10.80.0.2/32Why each server setting matters
Addressassigns the VPS’s tunnel address. It is not the public VPS address.ListenPortis the UDP port that the provider and host firewalls must permit.PrivateKeyauthenticates the VPS. Keep the file and its contents secret.- The peer’s
PublicKeyidentifies one client. - The peer’s
AllowedIPssays which source addresses that peer is allowed to use and which destinations should be routed to it. For a single client, use its unique/32address.
Overly broad peer entries such as 0.0.0.0/0 can make one peer appear responsible for all IPv4 addresses and can route or authorize more traffic than intended. Use narrow host or private-network ranges unless you are deliberately building a gateway.
Create the client configuration
On the client device, create a WireGuard profile with its private key, the VPS public key, and the public endpoint. This narrow example allows the client to reach only the VPS tunnel address:
[Interface]
Address = 10.80.0.2/32
PrivateKey = CLIENT1_PRIVATE_KEY
[Peer]
PublicKey = SERVER_PUBLIC_KEY
Endpoint = VPS_PUBLIC_ADDRESS:51820
AllowedIPs = 10.80.0.1/32To reach additional private networks behind the VPS, add those specific CIDR ranges to the client’s AllowedIPs, separated by commas. A full-tunnel profile uses 0.0.0.0/0 (and, when applicable, ::/0) but that changes the VPS into an internet gateway. It requires forwarding, return-path handling, NAT, and a wider security review. Do not select full tunnel merely because you want private SSH access.
When to use PersistentKeepalive
WireGuard is UDP and does not maintain a traditional persistent connection. The WireGuard quick start describes 25 seconds as a sensible interval for a wide variety of firewalls. Set this on a client only when that client is behind NAT or a stateful firewall and must receive packets after an idle period:
PersistentKeepalive = 25Leave it off by default when the client does not need inbound reachability through a NAT device. Unnecessary keepalives create traffic without improving the access policy.
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 →Apply the provider firewall before the host firewall
Configure the cloud firewall or security group first. Start with a default-deny inbound policy and add only the rules required for the rollout.
| Traffic | Source | Destination | Rollout policy |
|---|---|---|---|
| WireGuard | Any address that must connect | UDP 51820 | Allow |
| SSH recovery | Your fixed administration address only | TCP 22 | Allow temporarily, then remove |
| Private services | None on the public interface | Database, dashboard, API ports | Deny |
| Other unsolicited inbound traffic | Any | All other ports | Deny |
Provider firewalls and host firewalls are separate enforcement layers. Keep equivalent minimum-exposure rules in both. The provider rule should not expose a port that the host firewall is expected to protect, and the host firewall should not depend on the provider firewall for correctness.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Configure the Linux host firewall
Use the firewall tooling already supported by your distribution. The following UFW example expresses the policy on Ubuntu and Debian. Adapt service ports to your actual applications.
- Set conservative defaults:
sudo ufw default deny incoming
sudo ufw default allow outgoing- Permit the WireGuard listener:
sudo ufw allow 51820/udp- During rollout, permit SSH only from your fixed recovery address:
sudo ufw allow from ADMIN_PUBLIC_IP to any port 22 proto tcp- After the interface exists, permit SSH and private applications on
wg0only:
sudo ufw allow in on wg0 to any port 22 proto tcp
sudo ufw allow in on wg0 to any port 443 proto tcp
sudo ufw allow in on wg0 to any port 5432 proto tcp- Enable UFW and inspect the resulting rules:
sudo ufw enable
sudo ufw status verboseDo not add a broad public rule such as “allow 22/tcp” after adding the interface-specific rule. Once VPN access is proven, remove the temporary recovery rule:
sudo ufw delete allow from ADMIN_PUBLIC_IP to any port 22 proto tcpIf you use nftables, firewalld, or another firewall instead of UFW, implement the same logic: default-deny unsolicited inbound traffic, allow established and related return traffic, allow the WireGuard UDP port on the public interface, and allow private service ports only when the input interface is wg0 or the source belongs to the VPN subnet.
Account for IPv6
A VPS with a public IPv6 address can remain reachable even when you secure only IPv4. Apply equivalent provider and host rules to IPv6, configure an IPv6 tunnel deliberately, or disable public IPv6 if you do not need it. Check both address families from an unrelated network before declaring the server private.
Bring up WireGuard and make it persistent
Start the interface manually so you can inspect errors before enabling it at boot:
sudo wg-quick up wg0
sudo wg show
ip address show dev wg0
ip routeWhen the interface and peer configuration are correct, enable it at startup:
sudo systemctl enable wg-quick@wg0
sudo systemctl status wg-quick@wg0Ubuntu documents the normal service operations as start, stop, reload, and restart. Reload is suitable for peer-only edits that do not change routes or interface hooks. Restart when changing addresses, routing, or PostUp/PostDown firewall commands. A restart briefly removes the interface, so keep the provider console available.
Bind private services to the VPN, not the public interface
Firewall restrictions are the primary control, but binding a service to the tunnel address provides a second boundary. Where the application supports it, configure it to listen on 10.80.0.1 or on localhost plus a reverse proxy reachable through wg0. Do not bind a database or administration panel to every address unless the host firewall explicitly blocks its public path.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
SSH
After connecting through the tunnel, use the VPN address:
Free tools Windows power users keep installed
One-click scans. No signup required.
ssh [email protected]You can also set an SSH daemon listen address deliberately, but change it only while a console session is available. A firewall rule that permits TCP 22 only on wg0 is usually easier to roll back than a daemon misconfiguration.
Web dashboards and APIs
For a private dashboard, permit its TCP port on wg0 and deny it on the public interface. If the service sits behind a reverse proxy, keep the proxy’s listener private as well unless that proxy is intentionally public. Test the application by its tunnel address, not by the VPS’s public address.
Databases
Restrict database listener and authentication rules to the VPN subnet, such as 10.80.0.0/24, and use per-user credentials and TLS where supported. A firewall does not replace database authentication; it only reduces where connection attempts can originate.
Verify from two independent networks
Do not remove recovery access after testing from the same network that administers the VPS. Perform both sides of the test.
Recommended Free Tools
From a connected WireGuard peer
- Activate the client profile.
- Ping or otherwise test the VPS tunnel address if ICMP is permitted.
- Run
ssh [email protected]. - Connect to every intended private service using its tunnel address and port.
- Confirm that the client’s route table contains only the destinations you intended.
sudo wg showLook for a recent handshake, increasing transfer counters, and the expected peer public key.
From an unrelated internet connection
- Use a mobile hotspot, another office, or a separate network.
- Confirm that UDP 51820 can reach the VPS if the client is not already connected.
- Confirm that public SSH and every private service port do not accept connections.
- Check both the public IPv4 and public IPv6 addresses when both exist.
A blocked port may appear as a timeout or as a refusal depending on the provider and host firewall behavior. What matters is that the service is not usable through the public address, while it remains usable through the tunnel.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep private-service access separate from full-tunnel internet routing
For a VPS that merely hosts private services, do not enable forwarding or masquerading. The client needs a route to the VPS’s tunnel address and any explicitly listed private networks; the VPS does not need to carry the client’s internet traffic.
A deliberate full-tunnel gateway is a different design. It needs IP forwarding, forwarding firewall rules, a return route, and NAT (often masquerading) on the public interface. It also changes logging, abuse handling, bandwidth usage, and the consequences of a compromised peer. Add it only when internet egress through the VPS is an explicit requirement.
DNS over the tunnel
Configure DNS through the tunnel only when clients need internal names or want DNS queries to leave through the VPS. Resolver-specific commands and wg-quick DNS behavior vary by distribution and resolver tooling. Verify which resolver is active before adding DNS hooks, and ensure that a DNS failure cannot prevent the tunnel from being brought down or repaired.
Troubleshoot by symptom
| Symptom | Likely causes | Checks and fixes |
|---|---|---|
| No recent handshake | Wrong endpoint, blocked UDP, incorrect keys, or client behind restrictive NAT | Check the public address and UDP port in the client profile, compare public keys, inspect provider and host firewall counters, and consider PersistentKeepalive = 25 on the NATed client. |
| Handshake exists but tunnel address is unreachable | Incorrect tunnel addresses, duplicate peer address, or missing interface route | Inspect ip address show dev wg0, ip route, and each peer’s unique AllowedIPs. |
| VPN works but SSH fails | SSH is listening only on another address, or the host firewall lacks a wg0 rule |
Check the daemon’s listen addresses and add a narrowly scoped interface rule for TCP 22. |
| Private service works publicly | A broad provider or host rule still exposes the port, or the service is intentionally public | Remove the public allow rule, verify the service bind address, and test from an unrelated network. |
| Client loses internet access after connecting | Full-tunnel AllowedIPs was selected without forwarding and NAT |
Use narrow routes for private-only access, or complete the separate gateway design deliberately. |
| Access works until reboot | wg0 was brought up manually but not enabled |
Enable wg-quick@wg0 and inspect its status and journal after reboot. |
| IPv6 services remain exposed | Only IPv4 rules were configured | Add equivalent IPv6 provider and host rules, configure IPv6 intentionally, or disable the unused public IPv6 path. |
WireGuard compared with another VPN implementation
WireGuard is a strong fit when the goal is a small, auditable tunnel with per-peer keys and narrow routes. Another implementation such as OpenVPN can also enforce VPN-only access; the choice should follow your client fleet and operational requirements.
| Decision axis | WireGuard | OpenVPN-style alternative |
|---|---|---|
| Client platforms | Native or first-party clients are available on common desktop and mobile platforms; verify support for your exact operating systems. | Broad platform support, often through a dedicated client application. |
| Identity and keys | Each peer has a private/public key pair; removing a peer means removing its public-key entry and allowed address. | Common deployments use certificates, profiles, or username/password combinations, with a different rotation workflow. |
| Narrow routing | AllowedIPs combines routing and source-address authorization, making per-peer private ranges straightforward when kept narrow. |
Selective routing is possible but may involve more profile and server directives. |
| Firewall integration | One UDP listener plus the wg0 interface maps cleanly to provider and host firewall rules. |
Usually requires a VPN listener and an equivalent virtual interface policy. |
| Recovery | Keep console access and one temporary SSH rule; validate the handshake before removing it. | The same layered recovery principle applies, although configuration and certificate failures can add more moving parts. |
| Best fit | Private-service access, small peer sets, and explicit routes. | Environments that already depend on its authentication, policy, or client-management ecosystem. |
Operate the VPN-only VPS safely over time
Adding and removing peers
Assign every new device its own key pair and unique tunnel address. Add only the required private networks to that peer’s AllowedIPs. To revoke a device, remove its peer block, reload or restart the interface as appropriate, and invalidate any application credentials that device used. Deleting a key from a client does not revoke the server-side peer entry by itself.
Protect and rotate keys
Store server private keys with root-only permissions and protect client private keys with the operating system’s credential storage where available. Rotate keys when a device is lost, a user leaves, or a key may have been copied. Keep a documented inventory that maps each public key to a person or device without recording private keys.
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 glitchesReview exposure after changes
Whenever you install a new service, check its listening addresses, provider firewall rules, host firewall rules, and IPv6 exposure. A package update can change a daemon’s default bind address or open a new socket. Re-run the two-network test after major firewall, kernel, VPN, or network changes.
Keep a recovery path documented
The goal is to remove routine public SSH access, not to eliminate recovery. Record the provider console procedure, the location of encrypted configuration backups, and the commands needed to stop or restore wg0. Test console access before an emergency; discovering that it is disabled during an outage is too late.
Quick Recap
Final verification checklist
- Only the chosen WireGuard UDP port is intentionally public.
- Provider and host firewalls both default to denying unsolicited inbound traffic.
- SSH and private application ports are allowed only on
wg0or from the VPN subnet. - Every peer has a unique key pair and tunnel address.
- Client
AllowedIPscontains only the destinations that peer needs. - No forwarding or masquerading is enabled for a private-service-only design.
- WireGuard starts automatically and shows a recent handshake for active peers.
- VPN clients can reach intended services through the tunnel.
- An unrelated internet connection cannot reach SSH or private services on either IPv4 or IPv6.
- The temporary recovery rule has been removed only after those tests succeed.
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.
