Port 21 and port 22 both look like the obvious choice for file transfer — they are the standard ones — and both are closed on purpose, for two completely different reasons that both come down to the same idea: not exposing more than a server owner actually needs.
Why the obvious ports are closed
| Port | What it is | Why it is blocked |
|---|---|---|
| 21 (FTP) | Plain, unencrypted file transfer | Sends credentials and file contents in the clear — insecure by design, not by mistake |
| 22 (SSH) | Administrative access to the underlying host | Reaching it would mean reaching the hypervisor itself, far beyond what any single tenant's container should be able to touch |
| 2022 (container SFTP) | A dedicated, encrypted SFTP daemon scoped to your container alone | This is the intended door — isolated per server, with no path to the host or to any other tenant |
The password is not a separate thing to remember
It is identical to the panel login password, by design — one credential, one place it can leak from, rather than a second secret sitting in a client's saved-password list.
How to confirm it worked
An SFTP client connects successfully using the host, port 2022, and panel username/password shown under the SFTP Details tab.