Network & Connectivity

Everything you need to reach your Blib, put your apps online and move data quickly. Each section gives you the essentials and links to the detailed guide.

1. How Your Blib Is Reachable

Every Blib has a public hostname (e.g. connectXX.trooper.ai) and its own range of public ports. You find both in your dashboard in the details of your Blib.

Any service that listens on 0.0.0.0 and one of these ports is reachable from the internet:

Code 
http://connectXX.trooper.ai:PORT

Details: 🌍 HTTPS Access (How to access your Blib via SSL)

2. Choose the Right Access Method

Your goal Best way Guide
Work in a terminal SSH SSH Access
Upload or download files SFTP or rsync SSH Access
Use a graphical desktop RDP RDP Access
Smooth remote desktop (video, 3D) NoMachine Realtime Access
Reach your server when SSH does not work VNC console in the dashboard VNC Console
Publish a web app, UI or API Webproxy with HTTPS Web Proxy
Quickly test an app Direct public port HTTPS Access

3. Put Your Web App or API Online

  1. Start your app on 0.0.0.0 with an internal port, e.g. 8080.
  2. Install the Webproxy template and point it to that port.
  3. You get an HTTPS address with a valid certificate, ready to share.

Good to know:

  • Templates already come with their own Webproxy endpoint.
  • Ports 80 and 443 on your Blib are not reachable directly. Use the Webproxy instead.
  • For long AI answers, stream the response (e.g. SSE), so the connection stays open while the answer is generated.

Details: Web Proxy with SSL, 🌍 HTTPS Access (How to access your Blib via SSL) and About SSL Certificates

4. Use UDP (VPN, WebRTC, Streaming)

Your public ports work with TCP by default. If your app needs UDP, e.g. Tailscale, WireGuard or WebRTC, add a UDP allow rule for it in the firewall settings of your Blib.

Details: 🛡️ Trooper.AI customizable Network-Level Firewall

5. Fast Uploads and Downloads

Use rsync for large data. It shows progress and continues where it stopped after an interruption:

bash 
rsync -avP -e "ssh -p PORT" ./my-dataset/ [email protected]:/home/USERNAME/my-dataset/

Switch to BBR for faster uploads. Our network shares bandwidth fairly between all customers. Under load, some packets are dropped on purpose. Most Linux systems use the TCP algorithm CUBIC by default, which slows down sharply on every dropped packet. BBR keeps your transfer fast. Switch the sending machine to BBR. For uploads, this is your local computer (Linux, kernel 4.9 or newer):

bash 
sudo modprobe tcp_bbr
echo "net.core.default_qdisc=fq" | sudo tee -a /etc/sysctl.conf
echo "net.ipv4.tcp_congestion_control=bbr" | sudo tee -a /etc/sysctl.conf
sudo sysctl -p

Check it with sysctl net.ipv4.tcp_congestion_control. The output should end with bbr. Do the same on your Blib to speed up transfers from your server to the internet.

On macOS? BBR is not available there. Upload several files in parallel instead (multiple rsync or SFTP transfers at the same time).

Data volume: 5 TB of traffic per GPU per month are included. Details: Payment & Invoices

6. Measure Your Connection Correctly

Some loss in ping or mtr under load is normal on a shared network and does not mean that your server is broken. Loss shown on hops along the way is often not real, because many routers answer these test packets with low priority.

What counts is the speed of your real transfers. Measure it directly, e.g. with the progress output of rsync -avP while you upload a large file.

7. Keep Your Connections Stable

  • Keep SSH alive: ssh -o ServerAliveInterval=30 -o ServerAliveCountMax=4 [email protected] -p PORT
  • Avoid idle timeouts: Connections without any traffic for a few minutes are closed automatically. Send keep-alives (e.g. every 30–60 seconds) and let your app and scripts reconnect on their own.
  • Use a stable network: A wired connection or private Wi-Fi works best. Mobile, public Wi-Fi and some VPNs can cause short interruptions.
  • Avoid sleep mode: Desktop environments can put your server to sleep after inactivity. See SSH Access (incl. File Transfer), section “Server Sleeps / Suspends After Inactivity”.

8. Quick Troubleshooting

Problem What to do
My app is not reachable on its public port Start it on 0.0.0.0 (not 127.0.0.1) and use one of your assigned ports. If your Blib status is green, port forwarding works. HTTPS Access
SSH warns “REMOTE HOST IDENTIFICATION HAS CHANGED” Remove the old key with ssh-keygen -R connectXX.trooper.ai. SSH Access
SSH and VNC both stop working after a while Your server is probably sleeping. SSH Access
Nothing connects after I enabled a firewall inside the server Disable the local firewall (e.g. UFW) via the VNC console. Firewall
Uploads are slow Switch to BBR, see section 5 above.
Web requests stop after about 60 seconds Stream long responses, see section 3 above. HTTPS Access

9. Need Help?

Our support team is happy to help. To get a fast answer, please include:

  • the ID of your Blib
  • the time of the problem, including your time zone
  • what you tried and the output of the commands you ran
  • the speed of a real transfer (e.g. from rsync -avP), if your question is about speed

Contact: Support Contacts