Reconnect your SSH or SFTP server after Codeanywhere

What to collect

You need the hostname or IP address, SSH port, username, authentication method, and the root path you want to open by default. If you used SSH keys in Codeanywhere, export the private key and confirm the matching public key still exists on the server.

Run the connection test first

A migration should not rely on guesswork. Test the connection before saving so wrong ports, key mismatches, bad usernames, blocked firewalls, and invalid root paths fail early with a clear message.

• Permission denied usually means user or credential mismatch.
• Connection refused usually means the port or SSH service is wrong.
• Timeout usually means firewall, DNS, or reachability issues.

Explorer and terminal use the same trust path

Once the connection is saved, the same working server details should unlock Explorer, editor tabs, and terminal access. If terminal works but Explorer does not, the server likely needs SFTP enabled or the root path corrected for that account.