Why won’t an FTP client connect to the server?

Connection failures usually come from an incorrect hostname, username, password, port, or protocol. Copy the settings from the hosting panel instead of guessing them. FTP commonly uses port 21, SFTP commonly uses port 22, and FTPS may use port 21 with explicit TLS. The host can assign different ports, so its instructions take priority.

If the domain has recently moved, its hostname may still resolve to the old server. Try the server name supplied by the host and verify the current DNS records. A username may require an account-specific suffix, and an FTP account can be restricted to one directory. Reset the password in the panel if there is any doubt about stored credentials.

Firewalls can block the connection on the local network or server. Test from another network, disable a VPN temporarily, and check whether the hosting security system has blocked your IP after repeated failures. For FTP, switching between passive and active mode can solve data-channel problems, especially behind a router or corporate firewall.

Read the exact client log. An authentication error, timeout, refused connection, and failed TLS negotiation point to different causes. Send the timestamp, public IP, hostname, protocol, port, and sanitized log to hosting support. Never include the password in a support ticket or screenshot.