TCP tunnels
TCP links require an active tunnel (VPN) - they cannot be created for non-tunnelled servers. A random port in the range 10000–20000 is assigned automatically. Connect using:- Target:
192.168.1.1:22(MikroTik SSH) - ProxyLink URL:
tcp.proxylink.dev:17050 - Connect:
ssh admin@tcp.proxylink.dev -p 17050
UDP tunnels (VoIP / SIP)
A UDP link is a transparent port forward. ProxyLink passes the packets through to your device and does not inspect, rewrite or terminate them, so SIP and RTP cross it unchanged. ProxyLink does not run a SIP server. There is no registrar, no proxy and no SIP ALG. Phones register to your PBX; ProxyLink only carries the traffic to it. Example - PBX behind a router tunnel:- SIP port
192.168.40.10:5060is exposed as a UDP link ontcp.proxylink.dev - Phones point at that host and port, and register against your PBX through it
- The PBX needs no static IP and no inbound ports open
Because nothing rewrites the packets, SIP carries your PBX’s own addresses inside its messages. A PBX that advertises a private LAN address will still advertise it through the link, so set its external address (or NAT settings) to the ProxyLink host and port you were given, exactly as you would behind any other NAT.
SSL termination on HTTPS ports
TCP links on ports 443, 8443, and 5001 automatically get SSL termination with a valid Let’s Encrypt certificate fortcp.proxylink.dev. This means web UIs that require HTTPS - Ubiquiti UniFi, Synology DSM, pfSense, OPNsense - show a trusted certificate in the browser with no manual cert setup.
For all other ports, connections are plain TCP (no SSL). Add HTTPS proxy links for those instead.