Registered · Cross-platform

10050 Zabbix agent

TCP Yes
UDP
SCTP
DCCP

What it is

Zabbix agent passive checks.

When / why

Monitoring server polls the agent here.

Protocol status detail

TransportStatusMeaning
TCP Yes Assigned by IANA and standardized, specified, or widely used on this port.
UDP Not applicable for this transport.
SCTP Not applicable for this transport.
DCCP Not applicable for this transport.

Port range

Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.

Browse all ports →

Firewall rules for port 10050

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

ufw

sudo ufw allow proto tcp from <source> to any port 10050

Allow TCP 10050 (Zabbix agent). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="10050" protocol="tcp" accept'

Allow TCP 10050 (Zabbix agent) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> tcp dport 10050 accept

Allow TCP 10050 (Zabbix agent). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p tcp -s <source> --dport 10050 -j ACCEPT

Allow TCP 10050 (Zabbix agent). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-zabbixagent-10050 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 10050

Inbound rule for 10050 (Zabbix agent). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=10050,ToPort=10050,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 10050 (Zabbix agent). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-zabbixagent-10050 --direction=INGRESS --action=ALLOW --rules=tcp:10050 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 10050 (Zabbix agent). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Zabbix agent 10050/TCP" dir=in action=allow protocol=TCP localport=10050 remoteip=<source>

Inbound TCP 10050 (Zabbix agent). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Zabbix agent 10050/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 10050 -RemoteAddress <source>

Inbound TCP 10050 (Zabbix agent). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.