Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Ultra.cc Documentation?
Ultra.cc Documentation is the help center for Ultra.cc's specialized application hosting—shared "slots" where users run media and automation apps rather than building servers from scratch. The documentation assumes you already have an account and focuses on operating it: connecting over SSH, using the control panel, installing applications, and troubleshooting when something breaks.
What the documentation covers
- Getting started and connections: SSH access, public key authentication, FTP/FTPS, WebDAV, and Rclone mounting, plus a beginner's guide to the Ultra shell.
- Applications: setup notes for media and automation software such as Jellyfin, Komga, Homarr, Uptime Kuma, Seerr, Byparr, Autopulse, cross-seed, and Maintainerr.
- Torrent clients: remote adding and torrent control, plus troubleshooting.
- Client area: upgrading or downgrading a service, submitting support tickets, and setting up PayPal subscription payments.
- Guides and utilities: Rclone and MergerFS explainers, crontab, network speed tests, MTR diagnostics, log rotation, backup scripts, and unofficial installers for extra apps, languages, and SSH tools.
The documentation states that shared app hosting starts at €6.50 per month; current plan details and pricing belong on the main site or client area.
Who it is for and how to use it
It suits people who want Plex, Jellyfin, the *arr apps, or similar tools running without administering a server, and who are comfortable with a terminal for occasional tasks. If you are evaluating the service, read the getting-started and shell guide first to judge whether the workflow fits you. If you already have a slot, start from the specific task—say, connecting via SSH or fixing an FTP problem—rather than reading sequentially. For context on the apps themselves, see Jellyfin and Rclone.
How do I connect to my Ultra slot via SSH?
Use SSH from a terminal on your own computer, targeting the host, port, username and password shown in your Ultra control area under Connection Details. The documentation's own entry point for this is the guide Connect to your Ultra slot via SSH, listed on the main page of Ultra.cc Documentation.
What to have ready
- The SSH hostname and non-standard port from your service's connection details — shared hosting rarely uses port 22.
- Your slot username and password (or, if you have set one up, your public key).
- A terminal: Terminal on macOS/Linux, PowerShell or Windows Terminal on Windows.
Basic command shape
ssh -p <port> <username>@<host>
Replace the three placeholders with your own values. On first connection you will be asked to accept the host fingerprint; type yes. Then enter your password — characters will not appear as you type, which is normal.
Practical notes
- If the connection hangs, check the port first; a wrong port usually times out rather than being refused.
- If you see "Permission denied", re-copy the username from the control area rather than retyping it.
- Once connected, you are in your slot's shell, where the documentation's shell beginner's guide and the Rclone, torrent client and *Arr pages become usable.
- Key-based login is worth setting up if you will connect often; the documentation covers public key authentication separately.
Next step
Open Connection Details in your Ultra control area, copy the SSH line exactly as shown, and paste it into your terminal. If it fails, the connection-details page and the shell beginner's guide are the two documents to read before filing a support ticket.
What steps should I follow to upgrade or downgrade my Ultra service?
Use the Upgrade or Downgrade your Service page in the Client Area of Ultra.cc Documentation. It is written for existing customers who want to move to a different plan, so the steps assume you already have an active service and a Client Area login.
What to expect from the process
The documentation places plan changes in the Client Area alongside billing tasks such as submitting a support ticket and setting up a PayPal subscription. In practice, a plan change is a billing-side action: you select the new plan there, and the change is applied to your existing slot rather than requiring a new account. The page also sits next to the Upgrade or Downgrade entry in the Client Area section, which confirms it covers both directions with one procedure.
Because plan changes affect your slot's resources and its monthly charge, treat it as a two-part decision: which plan fits your current usage, and when to switch so you are not paying for capacity you no longer need. If you are moving down, check that your current apps and stored data still fit the smaller plan before confirming.
A practical sequence
- Log in to the Client Area and open the upgrade/downgrade page.
- Compare the target plan against your actual usage — number of apps running, storage consumed, and traffic — rather than against the advertised tier names.
- Confirm the change and note any billing adjustment shown at checkout.
- After the change takes effect, reconnect and verify your apps still start and your data is intact.
When to ask first
If you run many applications or large media libraries, confirm the target plan's limits with support before switching rather than after. The same Client Area hosts the support ticket form, so a short question there is cheaper than an unwanted downgrade. For connection details after a change, the Connection Details section covers SSH and related access.
As a general rule, upgrade when you are consistently hitting resource limits, and downgrade only after pruning unused apps and data — that keeps the move reversible and avoids a second change in the same month.
How do I set up Rclone to mount my Ultra slot on Windows?
Use Rclone's mount command with a WebDAV or SFTP remote pointing at your Ultra slot, and run it with a drive letter so it appears in Windows Explorer. Ultra.cc's own documentation covers both the connection details and a dedicated Windows mount walkthrough, so follow those rather than improvising credentials.
Practical setup path
- Collect connection details first. In the Ultra client area, open the connection details for your slot and note the hostname, port, username and password (or SSH key). Rclone needs these exact values; a single wrong port is the usual cause of a failed mount.
- Create the remote. Run
rclone config, choose a new remote, and pick either WebDAV (simpler, works over HTTPS) or SFTP (closer to full filesystem behaviour). Enter the host, port, user and password when prompted. - Test before mounting. Run
rclone lsd remote:to list top-level folders. If this fails, fix the remote before adding mount complexity. - Mount to a drive letter. Use a command like
rclone mount remote: X: --vfs-cache-mode writes(adjust the remote name and letter).--vfs-cache-mode writesmakes ordinary file writes and edits behave far more predictably than a bare mount. - Make it persistent. Wrap the command in a
.batfile or a scheduled task set to run at logon, so the drive returns after a reboot.
Choosing between WebDAV and SFTP
| WebDAV | SFTP | |
|---|---|---|
| Setup effort | Lower; HTTPS port only | Slightly higher; SSH credentials |
| Best for | Browsing, copying media, occasional edits | Scripts and tools expecting a real filesystem |
| Trade-off | Some apps handle WebDAV paths poorly | More sensitive to latency and dropped connections |
For a Windows user who mainly wants a drive letter to drag files to and from, WebDAV with write caching is usually the least fiddly. For automation that reads and writes many small files, SFTP tends to be more compatible.
Common pitfalls
- Mounting without
--vfs-cache-modeand then wondering why saves fail or files appear truncated. - Running the mount in a window that closes; the drive vanishes with it.
- Expecting remote-mounted media to stream as smoothly as local disk — latency matters, and Ultra's own notes on Plex performance discuss this trade-off.
Start with Ultra.cc Documentation, specifically the Windows mount and connection-details pages, then test with rclone lsd before committing to a drive letter.
What troubleshooting steps can I take if FTP or torrent clients aren't working correctly?
Start with the two dedicated troubleshooting pages rather than changing settings at random. Ultra.cc's documentation separates FTP troubleshooting from Torrent Clients guidance, so match the page to the failing tool before you touch credentials or configuration. For FTP, work through connectivity first (host, port, passive mode, credentials), then client-specific settings; for torrent clients, check the client's own logs and the slot's resource usage before reinstalling anything.
A practical order of checks
- Confirm the service itself is reachable. Test SSH or the control panel. If those also fail, the problem is the slot or your network, not FTP or the torrent client.
- Re-check connection details against the documented values: hostname, port, username and password. A single wrong character in a password or the wrong port explains most FTP failures.
- Try passive mode for FTP. Many home networks and firewalls block active-mode data connections, so switching the client to passive mode resolves stalled listings and transfers.
- Inspect the torrent client's logs for tracker errors, permission problems or disk-full messages. Distinguish "cannot connect to trackers" from "cannot write files" — they point to different fixes.
- Check disk and traffic usage with the documented monitoring tools. A full disk silently breaks both FTP uploads and torrent writes.
- Test with a second client or a plain command-line FTP session to see whether the fault follows the client or the slot.
When to use each resource
| Situation | Best starting point |
|---|---|
| FTP login fails or transfers stall | FTP Troubleshooting page |
| Torrent client won't start, connect or download | Torrent Clients section |
| Both FTP and torrents fail at once | Connection details and slot status first |
| Repeated failures after changes | Support ticket with logs attached |
A concrete example: if FileZilla connects but directory listings hang, the usual cause is active-mode FTP being blocked; switching to passive mode is the first fix, not recreating the account. If qBittorrent shows "connection refused" while SSH works, the client process or its port is the likely culprit.
For deeper reference, the official Ultra.cc Documentation covers the FTP and torrent pages directly, and general client guidance is available from FileZilla and qBittorrent. If steps on those pages don't resolve it, submit a support ticket with the exact error text and timestamps — that turns a vague "it doesn't work" into something diagnosable.
How can I submit a support ticket through the Ultra client area?
Open your Ultra client area, sign in, and look for the Submit a Support Ticket option in the navigation; the documentation lists it under the Client Area section alongside billing tasks such as upgrading or downgrading your service. From there, choose the category that matches the problem (for example, connection, application, or billing), describe what you have already tried, and include the relevant details such as your slot name, the app affected, exact error text, and timestamps.
What to include for a faster answer
- Symptom and timing: what broke, when it started, and whether it is constant or intermittent.
- Scope: one app or the whole slot, and whether other users or devices are affected.
- Evidence: screenshots of errors, log excerpts, and any commands you ran with their output.
- Recent changes: new installs, configuration edits, or credential changes just before the issue appeared.
Practical next step
Before submitting, check the documentation area for your specific app; the site groups guides by application and by topic, so a troubleshooting page may already cover your error. If it does not, submit the ticket with the details above rather than a one-line "it doesn't work" message, since specific evidence usually shortens the back-and-forth.
Decision criterion
Use a ticket for account, billing, or slot-level problems that only staff can resolve. For app configuration questions, the application's own documentation and community forums are often quicker, and you can mention in the ticket what you already checked so support does not repeat those steps.
User reviews (0)