Network Requirements

On your local network, JetKVM needs no internet. For updates, the cloud and the correct time, allow these outbound connections.

Updates and cloud

Purpose	Protocol	Destinations
Updates and cloud	HTTPS, tcp/443	`api.jetkvm.com`, `update.jetkvm.com`, `app.jetkvm.com`
Checking update signatures	HTTPS, tcp/443	`keys.openpgp.org`, `keyserver.ubuntu.com`
Google sign-in for the cloud	HTTPS, tcp/443	`accounts.google.com`, `www.googleapis.com`
Remote sessions, finding a route	STUN, udp	`stun.cloudflare.com:3478`, `stun.l.google.com:19302`, `stun1.l.google.com:5349`

A remote session then sends its video over UDP, either straight to your browser or through Cloudflare's relay when a direct connection isn't possible.

Time

JetKVM sets its clock from the network. Choose the time servers, or add your own, under Settings > Network. With the defaults:

Model	Protocol	Destinations
JetKVM	NTP, udp/123	`time.apple.com`, `time.aws.com`, `time.windows.com`, `time.google.com`, `time.cloudflare.com`
JetKVM	HTTP, tcp/80	`www.gstatic.com`, `cp.cloudflare.com`, `edge-http.microsoft.com`
JetKVM Mini	NTP, udp/123	`time.apple.com`

JetKVM also reaches time.cloudflare.com and time.google.com by fixed IP address, without DNS.

Tailscale

If you use Tailscale, it needs its own connections, starting with controlplane.tailscale.com. See what Tailscale needs through a firewall.