Port 3022: Unassigned — The Alternate SSH Address

What Range This Port Belongs To

Port 3022 sits in the registered ports range (1024–49151). IANA maintains this range for services that apply for an official assignment, but not every port in it gets claimed. Port 3022 is currently unassigned — no service holds an official IANA registration for it.¹

That doesn't mean the port is quiet. Unassigned registered ports are often claimed informally by software that needs a predictable home that won't collide with the well-known ports (0–1023).

Who Actually Uses Port 3022

Two different projects have independently landed on 3022 as their default, for the same underlying reason: they both need an SSH-like channel, and port 22 is already spoken for.

Gravitational Teleport (TCP) Teleport is an open-source access platform designed to replace raw SSH with something auditable, certificate-based, and zero-trust. When a Teleport node service runs on a server, it listens on port 3022 by default — the internal equivalent of what port 22 is for OpenSSH. The Teleport proxy connects to nodes over 3022 to deliver SSH sessions.²

If you find port 3022 open on a server in your infrastructure, Teleport is the most likely explanation.

Gitea SSH in Docker (TCP) Gitea is a self-hosted Git service. When running in a Docker container, Gitea can't expose port 22 directly without conflicting with the host system's own SSH daemon. The Gitea documentation and most community configurations map the container's SSH port to port 3022 on the host: 3022:22.³

This means git clone ssh://git@yourhost:3022/repo.git is a pattern you'll encounter often in self-hosted Git setups.

Zwift (UDP) The fitness application Zwift has been observed using UDP 3022 for some of its communications.⁴

How to Check What's Listening on Port 3022

On Linux or macOS:

ss -tlnp | grep 3022
# or
lsof -i :3022

On Windows:

netstat -ano | findstr :3022

These commands show the process name and PID bound to the port. If you see teleport or gitea, you know what you're looking at.

Why Unassigned Ports Matter

The registered port space exists as a coordination mechanism. When software authors choose a port, they're supposed to register it with IANA — partly to avoid collisions, partly so that firewall administrators and network operators know what to expect. An unregistered but consistently used port creates ambiguity: you can't know from the port number alone which application is listening.

Port 3022 is a good example of how informal conventions fill the gaps. Two separate projects chose it independently for similar reasons. Neither registered it officially. That's fine in practice — until someone else's software also decides 3022 is a good idea, and two services start fighting over the same address.