If you want extra security in addition to the existing ZAP-Hosting DDoS protection, you can secure your txAdmin instance with a Cloudflare Tunnel. This way, the txAdmin web interface is no longer directly accessible through your server's public IP address, but securely through your own domain. Cloudflare filters attacks targeting the txAdmin port, while you can completely close the local port without losing access.
To use Cloudflare Tunnel on Windows, you need a Windows Dedicated Server, a working txAdmin installation, your txAdmin port, and a domain that is already connected to your Cloudflare account. If your domain isn't connected to Cloudflare yet, please follow our Cloudflare Setup guide first.
Cloudflare Tunnel works by establishing an outgoing encrypted connection from your server to Cloudflare, so no public ports need to remain open for txAdmin.
Before installing cloudflared on your Windows server, create and configure the tunnel directly in your Cloudflare dashboard.
Log in to your Cloudflare account and navigate to the Zero Trust section. There, you can create a new tunnel that will later route traffic to your txAdmin interface.
Cloudflare provides a small tool called cloudflared. Installing cloudflared on Windows is very easy. First, download the Windows Installer.
Once the file has downloaded, launch the installer and follow the instructions. After installation, open Command Prompt as an administrator. Run the following command:
cloudflared.exe service install eyJhIjoiMj...
After running the command, your server connects to Cloudflare through the tunnel. If everything works, the status in the Connectors section changes to Connected, confirming that the tunnel is active and working.
Next, configure the Route Traffic settings. Create a new subdomain entry of your choice. In this example, the subdomain txAdmin is used to access the txAdmin interface later.
Select the domain you want to use, set the service type to HTTP, and enter localhost:port as the URL. Replace port with the port you configured for your txAdmin instance. This example uses port 40500.
Security tip For security reasons, we recommend using a different port instead of the default txAdmin port 40120.
To prevent the port from being accessible outside the tunnel, configure Windows Firewall to accept connections to the port only from localhost. Restrict the rule's Remote address field to 127.0.0.1. This ensures that all traffic must come from the local system and blocks external access. As a result, the service behind cloudflared cannot be accessed from outside the tunnel.
netsh advfirewall firewall add rule name="Cloudflared Local Only" dir=in action=allow protocol=TCP localport=40500 remoteip=127.0.0.1
This setting blocks all access attempts from outside the server, so the service behind cloudflared is only accessible through the tunnel.
Once the Cloudflare Tunnel is active, your txAdmin interface is accessible only through your own domain, with all requests routed through Cloudflare, where they are filtered and secured.
Direct access to the txAdmin port through the server IP is blocked, eliminating the original attack surface entirely. This keeps txAdmin stable, secure, and reliably accessible—even if someone tries to overload or attack the interface.
If you have any further questions or need help, our support team is here for you every day! 🙂