Port 8117 PURITYRPC
Port 8117 is the IANA-assigned purityrpc port for Purity replication clustering and remote management (TCP).
What is port 8117 used for?
Port 8117 is assigned to purityrpc and uses TCP. The IANA registry describes the service as “Purity replication clustering and remote management”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.
Ports are the transport-layer address a service listens on. A client that wants to reach purityrpc connects to port 8117. If nothing is listening, the connection is refused. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 8117 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Browse all RPC and service APIs ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Pure_Storage].
Check and block port 8117
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :8117'Check on Windows
Get-NetTCPConnection -LocalPort 8117 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 8117/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 8117 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 8117 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 8117 is usually used
Most traffic on port 8117 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Service-to-service calls between application components.
- API gateways and clients that use a binary RPC protocol.
- Local development of microservices that expose a fixed RPC port.
Probe the RPC listener
RPC protocols need their own client; this only confirms the socket is reachable. For gRPC with reflection enabled, use grpcurl.
nc -vz 127.0.0.1 8117Common problems with port 8117
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 8117. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :8117' or sudo lsof -i :8117. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 8117 at a glance
| Port number | 8117 |
|---|---|
| Service name | purityrpc |
| Transport protocol | TCP |
| Category | RPC and service APIs |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [Pure_Storage] |
| Registry description | Purity replication clustering and remote management |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 8117 used for?
Port 8117 (PURITYRPC) uses TCP. Purity replication clustering and remote management.
How do I check if port 8117 is open?
On Linux run `sudo ss -tlpn 'sport = :8117'`. On Windows run `Get-NetTCPConnection -LocalPort 8117 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 8117; empty output usually means nothing is bound to it.
How do I block port 8117?
With UFW run `sudo ufw deny 8117/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 8117 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 8117 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
- Port 8111 · skynetflowSkynetflow network services
- Port 8140 · puppetThe Puppet master service
- Port 5474 · apsolab-rpcThe Apsolab company's status query protocol
- Port 8710 · semi-grpcgRPC for SEMI Standards implementations
- Port 4317 · OpenTelemetry OTLP gRPCOpenTelemetry Protocol (OTLP) gRPC receiver port (community…
- Port 9339 · gnmi-gnoigRPC Network Mgmt/Operations Interface
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy