Networking: ICMP Destination unreachable (Port unreachable) — UDP packet sent to a port where nothing is listening
A host answered a UDP packet with an ICMP message saying no program is listening on that port.
ICMP Destination unreachable (Port unreachable)Port unreachableICMP port unreachabletype 3 code 3ICMP Destination Port Unreachable Meaning
The target machine is up but the service isn't running or isn't bound to that address/port, so UDP clients (DNS, NTP, syslog, SNMP, game servers) get "port unreachable" or ECONNREFUSED on connected UDP sockets. Start the service, bind it to the right interface, and check the firewall.
Common causes
- UDP service not running
- Service bound to 127.0.0.1 only
- Wrong port number
- Firewall REJECT rule
- Container port published only for TCP
⚡ Quick fix
- Check the listener:
ss -ulnp | grep PORT - Bind the service to the right interface
- Publish UDP in containers:
-p 53:53/udp
Detailed fix by platform
Linux
- bash
ss -ulnp | grep :514 sudo tcpdump -ni any icmp
How to diagnose
- Listener — UDP port open?
- Bind address — Reachable?
- Docker — /udp published?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- dig: status: REFUSED (recursion not available) Networking: dig: status: REFUSED / recursion requested but not available — the DNS server won't resolve queries for you
- Frag needed and DF set (ICMP type 3 code 4) Networking: ping: local error: message too long, mtu=1500 / Packet needs to be fragmented but DF set
- nc/telnet hangs: firewall DROP vs REJECT Networking: nc -vz hangs then times out — firewall silently DROPs packets (REJECT would answer "Connection refused")
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026