How to Install and Manage *Arr Apps and Media Automation on Ultra.cc

Ultra.cc's documentation covers *Arr-style media automation through a mix of official application guides and community-contributed installers, with storage handled by Rclone and MergerFS. To set it up, start from the relevant application page in the docs, follow its install steps on your slot, then mount and point storage using the Rclone/MergerFS guides. The exact steps depend on which app you choose, since Ultra.cc documents each one separately rather than offering a single bundled automation stack.

What the documentation actually provides

The docs are organized as a table of guides rather than a single setup wizard. For media automation, the relevant entries include:

Two things follow from this structure. First, there is no single "install all *Arr apps" page — you work app by app. Second, several of the most automation-relevant guides (2nd Instance of Mediarr, Autoscan, FileBot, File Cleaner, Remote Sync Tool) sit under Unofficial Application Installers or Unofficial SSH Utilities, meaning they are community-maintained rather than first-party. Treat those as convenience scripts: read the guide before running anything, and expect to verify results yourself.

Prerequisites before you start

• An active Ultra slot. The docs describe specialized shared app hosting starting at €6.50 EUR per month, with all-purpose plans. Your plan determines which apps are available to you.
• SSH access. The docs include "Connect to Your Ultra slot via SSH" and "Your Ultra Shell - A Beginner's Guide" — work through these first, since most installers and utilities run from the shell.
• A storage plan. Decide up front how media will be stored and mounted (see the Rclone/MergerFS section below), because *Arr apps need consistent paths to import and organize files.
• Awareness of your control panel. The "User Control Panel Tour" and Client Area guides cover service management, including upgrading or downgrading your plan if you need more resources.

Step-by-step: installing an automation app

1. Pick the app from the documentation table. For example, choose Jellyfin for playback, Seerr for requests, or Maintainerr for library cleanup. Open its dedicated page.
2. Read the whole page before executing commands. Each guide states its own requirements and expected outcome; some depend on other apps already being installed.
3. Connect via SSH using the connection details guide, then run the install steps exactly as written for your app.
4. Verify the app is running — typically by opening its web interface on your slot and confirming it loads and can see your media paths.
5. Wire apps together. Point your *Arr apps at the same download client and library paths, and connect your media server to those libraries. The torrent client guides and "Remote Torrent Adder and Torrent Control" cover the download side.
6. Add maintenance tooling as needed — for instance Maintainerr or ImageMaid for cleanup, or cross-seed for torrent matching.

Storage: Rclone and MergerFS

The "Rclone & MergerFS Explainer" is the key document here. MergerFS presents multiple storage locations as one combined mount, while Rclone handles cloud remotes. For automation, the practical rule is: mount storage first, confirm the mount is visible and writable from the shell, and only then configure *Arr apps to use those paths. If apps can't see files that exist, a missing or stale mount is the usual cause — check it before debugging the app itself.

Running a second automation stack

"2nd Instance of Mediarr" (Unofficial Application Installers) documents running a parallel set of media apps. This is useful if you want separate libraries or configurations, but it is an unofficial guide — confirm port and path conflicts against your existing setup before following it.

Troubleshooting and monitoring

The docs provide several diagnostics you can use when automation misbehaves:

• Traffic Monitor and Disk/Traffic Usage Command (Unofficial SSH Utilities) for checking whether downloads and transfers are actually happening.
• Disk Usage Monitor and File Cleaner for keeping the slot from filling up — a full disk is a common cause of failed imports.
• Application Monitor and Uptime Kuma for spotting apps that have stopped.
• MTR Guide and Ultra Network and Speedtests for connectivity problems between your slot and remote services.
• FTP Troubleshooting and the torrent client troubleshooting entries for transfer and client issues.
• "How Plex Performance is Affected" for understanding playback performance factors.

Practical cautions

• Unofficial means unofficial. Scripts under Unofficial Application Installers and Unofficial SSH Utilities are community contributions; they may assume specific configurations and are not guaranteed to fit your plan.
• Check plan fit before installing. Heavier automation stacks consume CPU, RAM, and disk; the Client Area's upgrade/downgrade guide is the documented route if you hit limits.
• Support tickets are handled through the Client Area guide if a documented step fails.
• Pricing and plan details beyond the starting figure should be confirmed on the site; the documentation does not enumerate every plan's limits.

Start with the SSH and shell guides, then the Rclone/MergerFS explainer, then install apps one at a time from their individual pages — that order avoids the most common failure, which is automation apps pointing at storage paths that were never properly mounted.