Do not expose the OpenClaw Gateway as the first step. Keep it bound to loopback, leave TCP port 18789 out of public inbound rules, and reach it through an SSH tunnel or Tailscale Serve. Secure the VPS administration path separately, then audit authentication, proxy trust, tools, secrets, logs, and trust boundaries before allowing any broader remote access.
That order matters because SSH access to the server and access to the Gateway are different security decisions. A tightly restricted SSH path can let you administer a private Gateway without publishing the Gateway itself. A reverse proxy or tailnet can be appropriate, but each creates an additional identity and exposure boundary that must be configured deliberately.
As an Amazon Associate I earn from qualifying purchases.
Choose the access model before you change the firewall
OpenClaw’s regular host installation binds the Gateway to loopback by default. Treat that default as the safest starting posture for a personal VPS: the process listens on the server itself, while remote administration travels through a separately secured channel. The official VPS guidance recommends an SSH tunnel or Tailscale Serve rather than making the Gateway directly reachable from the public internet.
First decide who needs access, from where, and whether that access is for server administration or for using the Gateway. Do not combine those questions into one firewall rule.
#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.
SSH administration is not Gateway publication
SSH is the operator’s path to the VPS. It can be restricted at the cloud-provider firewall and at the host firewall to the addresses or private network used by the administrator. Gateway access is an application-level path: it determines which identity can send requests and which OpenClaw tools or agents those requests can invoke. Opening SSH does not require opening the Gateway port.
For a single operator, the usual low-exposure design is:
- Keep the Gateway listening on loopback.
- Permit SSH only through the approved administration path.
- Forward the local Gateway port through SSH when you need it remotely.
A tailnet-based design follows the same principle: the Gateway remains private on the VPS while an authenticated private network or Serve endpoint carries the remote connection.
Compare the three practical access patterns
| Approach | Who can reach the endpoint | Is the Gateway port public? | Main controls to verify | Best fit |
|---|---|---|---|---|
| Loopback plus SSH tunnel | Operators who can authenticate to the VPS over the approved SSH path | No | Provider and host firewall rules, SSH identity controls, local tunnel handling, and OpenClaw authentication | Personal administration and occasional remote use |
| Tailnet access or Tailscale Serve | Devices and users admitted to the configured tailnet or Serve policy | No direct public inbound rule is required | Tailnet membership, device identity, Serve configuration, Gateway authentication, and the permissions available to admitted senders | Regular remote access from managed devices |
| Reverse proxy or other intentional publication | Clients that can reach the published hostname or address | The proxy is reachable; the Gateway should remain protected behind it | Gateway authentication, trusted-proxy identity handling, origin policy, TLS, proxy and host firewalls, and blocking direct access to the backend | Shared or integrated access where public reachability is an explicit requirement |
The third option is not a prerequisite for remote use. It is an architecture decision with more configuration and more opportunities for an incorrect trust assumption.
Lock down the VPS administration path
Before touching OpenClaw’s remote-access settings, ensure that you can recover the server and that the administration route is narrower than “the whole internet.” Use the VPS provider’s network firewall, the host firewall, or both, according to the controls your operating system and provider actually implement.
Allow the approved SSH path before enabling a host firewall
OpenClaw’s Hetzner example calls out an ordering rule that prevents a common lockout: create the SSH allow rule first, then enable UFW. The exact commands and interface names depend on the distribution and provider, so use the provider’s documented syntax rather than copying a generic rule to an unknown host.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated 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 match- Identify the SSH port and the source network from which you will administer the VPS.
- Add an inbound firewall rule permitting SSH from that approved source. If your provider supplies a cloud firewall, apply the rule there; if you also use UFW or another host firewall, add the corresponding host rule.
- Confirm that an existing SSH session remains usable and test a second session before enabling or tightening the host firewall.
- Enable the host firewall only after the allow rule is in place.
- Record the provider console or out-of-band recovery method in case a later rule change blocks normal SSH.
Do not assume that a rule in one layer controls every packet. A cloud firewall, the operating-system firewall, container networking, and a reverse proxy can each create a different path.
Keep an emergency route separate from normal access
Store the provider-console procedure and recovery credentials outside the VPS. If you later change SSH policy, firewall rules, proxy bindings, or container networking, keep one tested administrative session open until a new session succeeds. This is operational resilience, not a substitute for least privilege.
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.
Keep the OpenClaw Gateway private
The VPS guidance explicitly says not to add a public inbound rule for TCP port 18789. Leave the Gateway on loopback unless you have selected and configured a different access architecture. A public address such as 0.0.0.0/0 should not be used as a shortcut for remote access.
Use an SSH tunnel when the operator is the only remote user
An SSH local-forwarding tunnel carries a local connection to the loopback listener on the VPS. A typical form is:
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 →ssh -N -L 18789:127.0.0.1:18789 user@your-vps-hostReplace the account and host with values for your server, and adapt the local port if it is already occupied. Keep the SSH session running while you use the local Gateway endpoint. This forwards the connection through SSH; it does not create a public listener on the VPS. Your SSH account, key policy, and host firewall still determine who can create the tunnel.
If the Gateway uses a different local address or port in your installation, use the values shown by the current OpenClaw documentation and configuration. Do not infer that a working tunnel proves the Gateway is authenticated correctly; verify both layers.
Use a tailnet when managed devices need regular access
Tailscale Serve is the documented alternative for remote access while keeping the Gateway on loopback. The security question shifts from “which internet clients can connect?” to “which users and devices are admitted to the tailnet and what identity does the Serve path present?” Review membership, device approval, account recovery, and any policy that determines who can reach the Serve endpoint. Then verify OpenClaw’s own authentication and sender permissions rather than treating tailnet membership as the only authorization check.
Inspect Docker port publishing separately
Container deployment can create a path that is not obvious from the process configuration. Check the container’s published ports, the host’s listening sockets, the provider firewall, and the host firewall as one end-to-end route. OpenClaw’s Docker guidance points operators of public hosts to the DOCKER-USER chain for network hardening. Confirm that rules in that chain match the traffic path your Docker installation actually uses.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsA containerized Gateway is not automatically sandboxed. The default Docker sandbox backend is off, so containerizing the service should not be presented as proof that agent tools are isolated.
If you publish through a proxy, configure the complete trust boundary
A reverse proxy can provide a deliberate remote endpoint, but it should front a protected Gateway rather than replace Gateway security. The correct settings depend on the proxy, TLS termination point, identity provider, and deployment topology; there is no safe one-size-fits-all configuration.
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
Define authentication at both relevant layers
Decide how the remote client authenticates to the proxy and how the request is authenticated by OpenClaw. If the proxy injects an identity header, OpenClaw must be configured to trust that header only when it arrives from the expected proxy path. A client must not be able to reach the backend directly and supply the same identity header itself.
Review the Gateway security documentation for the authentication mode supported by your OpenClaw release. Confirm what happens when authentication is absent, malformed, expired, or forwarded from an untrusted source. Test rejection, not only the successful request.
Set trusted-proxy and origin behavior deliberately
Proxy trust is an allowlist of intermediaries, not a declaration that every upstream request is safe. Limit trusted proxies to the addresses or network path that can actually terminate and forward traffic. Configure allowed origins for the browser clients you intend to use; do not use a permissive origin setting merely to make an integration work.
Terminate TLS at a component you control, protect certificates and keys, and make sure the connection from the proxy to the Gateway cannot be reached by an unintended network peer. If the proxy and Gateway share a host, firewall the backend listener so that only the proxy path can reach it.
Block the bypass path
After the proxy works, test the backend address independently from an external network. A successful proxy configuration is incomplete if the original Gateway listener is still reachable directly. Keep the backend private, and make the cloud firewall, host firewall, container rules, and proxy bindings agree on that design.
Reduce what a remote sender can cause
Network reachability answers only who can deliver a request. OpenClaw’s security model also requires deciding what a paired or otherwise allowed sender may trigger.
Free tools Windows power users keep installed
One-click scans. No signup required.
Review pairing and allowlists
Use OpenClaw’s pairing or allowlist controls to restrict which senders can interact with the Gateway. Remove stale devices and accounts, and document why each remaining entry exists. A private tunnel or tailnet narrows network access but does not, by itself, authorize every person or device on that path.
Grant only the tools an agent needs
Audit tool and agent permissions against the job the VPS is meant to perform. Disable capabilities that are not required, especially tools that can execute commands, modify files, send messages, access network services, or alter deployment state. Review plugin and node execution paths with the same care: an installed extension or connected node can expand the consequences of a compromised prompt or account.
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.
Prompt-injection defenses are useful, but they are not an access-control boundary. A sender who can reach an agent should still face explicit authentication, allowlisting, and tool restrictions.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Understand sandboxing rather than assuming it
Check whether sandboxing is enabled and which backend it uses in your installation. OpenClaw identifies sandboxing as one part of a broader security map; it does not turn every deployment into a hostile-user isolation boundary. In particular, the default Docker sandbox backend is off. Treat an enabled sandbox as a control with a defined scope, not as permission to grant unrestricted tools.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Protect credentials, state, logs, and transcripts
OpenClaw treats credentials, persistent state, logs, and conversation transcripts as security-relevant data. Include them in the VPS protection plan, backups, access review, and incident response procedure.
Limit filesystem and operator access
Identify where the installation stores configuration, tokens, plugin data, logs, and transcripts. Restrict those paths to the service and the operators who need them. Avoid placing secrets in shell history, public web roots, world-readable bind mounts, or container volumes whose permissions have not been checked.
When collecting diagnostics, redact credentials and session material before sharing logs. A log file can contain enough context to recover an account even when the original secret is not printed verbatim.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Run the built-in security audit
After the initial setup, run:
openclaw security auditRead each finding instead of treating a clean exit status as a complete review. Resolve issues involving authentication, exposure, permissions, secrets, sandboxing, or trusted proxies according to the current OpenClaw security documentation. Run the audit again after changing firewall exposure, Docker publishing, proxy settings, authentication, tools, or sender allowlists.
Have an incident path before you need it
If you suspect that a token, credential, transcript, or administrative key was exposed, use the affected service’s documented revocation or rotation process, preserve the evidence needed to understand the event, and restrict access while you investigate. Recheck Gateway authentication, sender lists, proxy logs, shell history, container volumes, and provider firewall changes. Restore remote access only after you can explain which path was exposed and which control now blocks it.
Respect OpenClaw’s trust boundary
OpenClaw’s official Security page states: “OpenClaw is not a hostile multi-tenant security boundary for mutually adversarial users sharing one agent or gateway.” In practical terms, do not place mutually distrustful users on one Gateway and assume that a pairing list or prompt policy provides the isolation of separate tenants.
If users do not share one trust boundary, choose a stronger separation design: separate Gateways, separate operating-system users with independently controlled data and permissions, or separate hosts. The right choice depends on the sensitivity of the tools, credentials, transcripts, and network access each user receives.
Recommended Free Tools
Verify the finished configuration before opening any broader route
Use this order for a final review. Each check should produce an observable result, not merely a configuration value.
- Confirm the listener: verify that the Gateway is bound to loopback and that no unintended public interface exposes it.
- Confirm firewall intent: check provider rules, host rules, and Docker’s
DOCKER-USERpath where applicable. Ensure TCP 18789 is not a public inbound exception. - Confirm administration: open a fresh SSH session through the approved source while keeping the recovery route available.
- Confirm the chosen access method: test the SSH tunnel or tailnet/Serve endpoint from an authorized device, then test from an unauthorized network or identity and verify rejection.
- Confirm proxy boundaries: if a proxy is used, verify TLS, authentication, trusted-proxy handling, allowed origins, and that direct backend access fails.
- Confirm sender controls: review pairing or allowlists and remove entries that are no longer needed.
- Confirm tool scope: inspect agent, plugin, node, and execution permissions against the minimum required task.
- Confirm data protection: check permissions on credentials, state, logs, transcripts, backups, and container volumes.
- Run the audit: execute
openclaw security audit, remediate findings, and keep the output with the deployment record.
Troubleshoot by separating the failing layer
The tunnel connects but the Gateway does not respond
Check that the Gateway is running and listening on the expected loopback address and port on the VPS. Then check the local forwarding target and the client URL. A successful SSH login proves only the administration path; it does not prove that the application is listening or that its authentication accepts the request.
The proxy works, but direct access also works
Find which layer is publishing the backend: a cloud firewall rule, host listener, Docker port mapping, or proxy binding. Remove the unintended route and retest from outside the VPS. Do not solve this by adding another authentication prompt while leaving an unreviewed bypass path in place.
Enabling the firewall cut off administration
Use the provider console or other out-of-band route, restore the SSH allow rule for the approved source, and test a new session before closing the recovery connection. Review the order of rule creation; OpenClaw’s provider guidance specifically emphasizes allowing SSH before enabling UFW.
A remote sender can reach the Gateway but cannot perform the intended task
Check the layers in order: network route, Gateway authentication, pairing or allowlist status, agent permissions, tool permissions, and plugin or node policy. Avoid broadening all tools to fix one missing capability; grant only the permission required for the task and rerun the security audit.
Keep the configuration current
OpenClaw’s defaults and hardening guidance can change across releases, while firewall behavior varies by provider and deployment. Before upgrading, changing container networking, adding a proxy, or admitting new users, review the current official documentation:
- OpenClaw Security for authentication, trust boundaries, audits, tools, sandboxing, secrets, and incident response.
- OpenClaw VPS documentation for the loopback-first remote-access model.
- OpenClaw Hetzner guide for the provider example that places the SSH allow rule before enabling UFW.
- OpenClaw Docker documentation for container deployment and
DOCKER-USERnetwork-hardening guidance.
Recheck the actual host, provider firewall, container publishing, proxy path, and OpenClaw configuration after every material change. The secure design is not “a VPS with a port hidden once”; it is a verified set of boundaries that still matches how the system is reachable and what an admitted sender can do.
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.
