bitlvl
EN

Port 9117 Jackett · TCP

Jackett: the torrent-indexer proxy used with Sonarr, Radarr and friends.

Port9117
TransportTCP
ServiceJackett
CategoryMedia streaming
Rangeregistered (1024–49151)
EncryptedNo, plaintext
ExposureLoopback or the host's own network only

What runs on port 9117

Jackett: the torrent-indexer proxy used with Sonarr, Radarr and friends. Its web UI and Torznab API listen on 9117 with an API key but no login by default, and it stores credentials for every indexer you configure. Localhost or the home LAN only; Prowlarr (9696) is its successor.

Software that uses it: Jackett · Prowlarr (9696) · Sonarr (8989), Radarr (7878), Lidarr (8686)

Should port 9117 be open?

Loopback or the host's own network only. The service should listen on 127.0.0.1 (or a Unix socket) and be reached by a reverse proxy or by the application on the same host. If it answers on a public address, that is a misconfiguration.

Check port 9117

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :9117'
sudo lsof -i :9117

# from another machine: is it reachable?
nc -zv host 9117
nmap -p 9117 host
curl -v telnet://host:9117      # raw TCP connect test, Ctrl-C to leave

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 9117

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 9117 proto tcp
sudo ufw deny 9117/tcp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 9117 accept
nft add rule inet filter input tcp dport 9117 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 9117 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 9117 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=9117 protocol=tcp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 9117" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 9117 TCP or UDP?

TCP. Jackett is a connection-oriented protocol; there is no UDP service on 9117 by default (a scanner reporting UDP 9117 open is usually seeing a filtered port).

Is port 9117 encrypted?

No, plaintext. Anything sent over it can be read by whoever is on the path, so it belongs on a trusted network or inside a VPN or SSH tunnel.

How do I check whether port 9117 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 9117 and which process. From another machine, nc -zv host 9117 or nmap -p 9117 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can Jackett run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.