How to Connect to Your Ultra.cc Slot via SSH
Updated
To connect to your Ultra.cc slot via SSH, open a terminal on your computer and run ssh username@hostname -p port, using the SSH username, host, and port shown in your Client Area. You'll need a terminal app, your slot credentials, and network access to the Ultra.cc host. The documentation lists "Connect to your Ultra slot via SSH" as the primary getting-started step, with connection details kept in the Client Area.
Where to Find Your Connection Details
Ultra.cc organizes its documentation around a Client Area section, which is where account- and service-level details live. Before you can connect, collect three pieces of information:
- SSH username — the account name assigned to your slot
- Hostname or IP address — the server your slot runs on
- SSH port — the port your slot listens on (shared hosting often uses a non-default port)
The documentation's "Connection Details" section covers related topics such as public key authentication, WebDAV access, and FTP/FTPS connections, so it's the place to check if your SSH details aren't where you expect.
Basic SSH Connection Steps
-
Open a terminal. On macOS or Linux, use the built-in Terminal. On Windows, use PowerShell or Windows Terminal, which include the OpenSSH client.
-
Run the SSH command with your details substituted:
ssh your_username@your_host -p your_port -
Accept the host key the first time you connect. SSH will show a fingerprint and ask you to confirm; type
yes. -
Enter your password when prompted. Characters won't appear as you type — that's normal.
-
Verify success. A successful login drops you into your slot's shell, typically with a prompt showing your username and host.
If the connection hangs or is refused, re-check the port and hostname first — a wrong port is the most common cause of a timeout.
Verify the Connection Worked
Once logged in, run a simple command such as whoami to confirm you're in the right account, or pwd to see your starting directory. The documentation's "Your Ultra Shell - A Beginner's Guide" walks through the shell environment if you're new to command-line work.
Common Connection Problems
| Symptom | Likely cause | What to check |
|---|---|---|
| Connection timed out | Wrong host or port | Re-copy details from the Client Area |
| Permission denied | Wrong username or password | Confirm username; reset password if needed |
| Host key warning | Server key changed | Verify with support before accepting |
| Connection drops immediately | Shell or account issue | Check service status; open a support ticket |
For authentication problems, the "Public Key Authentication" guide explains key-based login as an alternative to passwords. If you're troubleshooting file transfers rather than shell access, the "FTP Troubleshooting Info" page covers FTP-specific issues.
Related Guides Worth Knowing
The documentation groups several connection topics that pair with SSH setup:
- Public Key Authentication — passwordless, more secure logins
- Rsync — syncing files to and from your slot over SSH
- WebDAV — accessing files through a web-style interface
- MTR Guide — diagnosing network problems if connections are slow or unstable
If you hit a wall you can't resolve, the Client Area includes a "Submit a Support Ticket" option.