PVTKRRX / Seedbox Runbooks

PVTKRRX

Seedbox Runbooks

Provider-specific setup for PVTKRRX. Each runbook shows the exact URLs to enter on your own self-host server /configure page for that seedbox provider, covering Prowlarr, qBittorrent, file server, path mapping, and auth.

Most users need the Remote Seedbox route: open /configure on your own HTTPS server origin, pick your provider below, and save there. This public site is guide-only and does not host your private config.

Updated: April 8, 2026

Quick Jumps

Hard rule: Stremio install is HTTPS-first for remote hosts. HTTP loopback (127.0.0.1) is only for same-device local installs.

For the one-command self-host installer, use curl -fsSL https://www.pvtkrrx.cc/install-selfhost.sh | sudo bash. That launcher stays on the hosted site, installs the branch payload behind the scenes, and falls back to main if a pinned release is too old for the self-host bootstrap script.

Direct-host update: if you clone this repo onto the seedbox or VPS itself, finish with npm run server:setup instead of leaving PVTKRRX on a hand-made node index.js launch. That setup flow writes the saved Remote Seedbox config, self-host password, runtime directory, and the HTTPS install/playback origins that the current server route expects.

Sports operator note: server-route artwork is cache-only during user requests. If sports matters on that box, either let the background seeder warm the runtime automatically or set Sports Poster Package Path and run npm run cache:sports-package. Cache misses fall back to generated posters instead of blocking on live upstream artwork fetches.

Compatibility Matrix

Provider LAN Bridge Remote Seedbox Direct Addon On Box Notes
Whatbox Yes Yes Yes SSH + Node available; Managed Links can expose custom HTTP apps over HTTPS.
Ultra.cc Yes Yes Conditional No root. Custom app ports and Nginx path proxy are supported; root-path hosting depends on your routing setup.
SeedHost Shared Yes Yes Conditional No root on shared plans. SSH available on shared except HD1.
Feral Hosting Yes Yes Conditional No root/sudo/apt. User-space Node install works. HTTPS needs proxypass setup.
RapidSeedbox Lean Yes Yes No No SSH on Lean plans.
RapidSeedbox Premium Yes Yes Yes SSH is available on Premium; custom software flow supported.
Bytesized Appbox Yes Yes Conditional SSH is available. Bytesized Connect requires Docker and root on the target server.
Swizzin (self-hosted) Yes Yes Yes Best on your own VPS where you control root, Nginx, and domain routing.
HostingByDesign Yes Yes Yes SSH and box tooling available on app hosting slots.

Whatbox Runbook

No Sudo Required Best Mode: Remote Seedbox or Direct

Configure Page Fields

  1. Install or verify qBittorrent and Prowlarr from the Whatbox Manage Apps panel.
  2. On your self-host server /configure page, select Remote Seedbox and pick Whatbox from the provider dropdown.
  3. Fill in the connection fields using your Managed Links HTTPS URLs:
FieldValue
Prowlarr URLhttps://<server>.whatbox.ca/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://<server>.whatbox.ca/qbittorrent
qBit Username/PasswordYour Whatbox login credentials
File Server URLhttps://<server>.whatbox.ca/files
File Server Authuser:password (your Whatbox credentials)
Path Mapping/home// (auto-filled by preset)
  1. Click Test Connection, then Save.

All three URLs above come from Managed Links in the Whatbox panel. If the Managed Link paths differ from the defaults above, use the exact paths shown in your panel.

Advanced: Host PVTKRRX directly on Whatbox
ssh user@server.whatbox.ca
mkdir -p ~/apps && cd ~/apps
git clone https://github.com/Kepners/pvtkrrx.git
cd pvtkrrx && npm ci --omit=dev
PORT=15000 npm run server:setup

When setup asks for the HTTPS front door, use skip until the Managed Link exists if needed. Then add this app as a custom Managed Link on the same port (for example 15000) and rerun npm run server:setup or set PVTKRRX_PUBLIC_BASE_URL to that final HTTPS origin.

Ultra.cc Runbook

No Root/Sudo Best Mode: Remote Seedbox or LAN Bridge

Configure Page Fields

  1. Install qBittorrent and Prowlarr from the Ultra.cc app panel.
  2. On your self-host server /configure page, select Remote Seedbox and pick Ultra.cc from the provider dropdown.
  3. Fill in the connection fields:
FieldValue
Prowlarr URLhttps://<slot>.ultra.cc/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://<slot>.ultra.cc/qbittorrent
qBit Username/PasswordYour Ultra.cc slot credentials
File Server URLhttps://<slot>.ultra.cc
File Server Authuser:password (same slot credentials)
Path Mapping/home// (auto-filled by preset)
  1. Click Test Connection, then Save.

Check the exact app paths in your Ultra.cc panel — if the subpaths differ from the defaults above (e.g. a custom Nginx proxy path), use those instead. Run app-ports show over SSH to confirm which ports each app uses.

Advanced: Host PVTKRRX directly on Ultra.cc
ssh username@host
bash <(wget -qO- https://scripts.ultra.cc/util-v2/LanguageInstaller/Node-Installer/main.sh)
app-ports free
mkdir -p ~/apps && cd ~/apps
git clone https://github.com/Kepners/pvtkrrx.git
cd pvtkrrx && npm ci --omit=dev
PORT=<free-port> npm run server:setup

Proxy the chosen port through ~/.apps/nginx/proxy.d/ and restart app-nginx for HTTPS. If your route is path-only or Stremio cannot install cleanly from that proxy origin, prefer LAN Bridge for stable addon URLs.

SeedHost Runbook

Shared: No Root SSH: Shared Except HD1

Configure Page Fields

  1. Install qBittorrent and Prowlarr from SeedHost one-click apps.
  2. On your self-host server /configure page, select Remote Seedbox and pick SeedHost from the provider dropdown.
  3. Fill in the connection fields:
FieldValue
Prowlarr URLhttps://<box>.seedhost.eu/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://<box>.seedhost.eu/qbittorrent
qBit Username/PasswordYour SeedHost slot credentials
File Server URLhttps://<box>.seedhost.eu
File Server Authuser:password (SeedHost typically needs Basic Auth)
Path Mapping/home// (auto-filled by preset)
  1. Click Test Connection, then Save.

Check the SeedHost control panel for the exact HTTPS app paths. HD1 plans do not have SSH, so use the Remote Seedbox route with hosted PVTKRRX. If your plan cannot expose a clean HTTPS root route for custom apps, use LAN Bridge instead.

Advanced: Host PVTKRRX directly on SeedHost (SSH plans only)
if ! grep -qw "PATH=$HOME/bin" ~/.bashrc ; then mkdir -p ~/bin && echo "PATH=$HOME/bin:$PATH" >> ~/.bashrc && source ~/.bashrc ; fi
cd && wget -q https://nodejs.org/dist/v22.14.0/node-v22.14.0-linux-x64.tar.gz
tar xf ~/node-v22.14.0-linux-x64.tar.gz --strip-components=1 -C ~/
rm -f ~/node-v22.14.0-linux-x64.tar.gz
mkdir -p ~/apps && cd ~/apps
git clone https://github.com/Kepners/pvtkrrx.git
cd pvtkrrx && npm ci --omit=dev
PORT=15000 npm run server:setup

Feral Hosting Runbook

No Root/Sudo/Apt Best Mode: Remote Seedbox or LAN Bridge

Configure Page Fields

  1. Install qBittorrent and Prowlarr from the Feral manager or via user-space install.
  2. On your self-host server /configure page, select Remote Seedbox and pick Feral Hosting from the provider dropdown.
  3. Fill in the connection fields:
FieldValue
Prowlarr URLhttps://<username>.feralhosting.com/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://<username>.feralhosting.com/qbittorrent
qBit Username/PasswordYour Feral login credentials
File Server URLhttps://<username>.feralhosting.com
File Server Authuser:password (HTTP auth credentials)
Path Mapping/media// (auto-filled by preset — note: Feral uses /media/ not /home/)
  1. Click Test Connection, then Save.

Feral save paths start with /media/ instead of /home/. The preset handles this automatically. If your apps are behind proxypass subpaths, use the exact subpath shown in the Feral wiki.

Advanced: Host PVTKRRX directly on Feral
mkdir -p ~/bin && cd
wget -q https://nodejs.org/dist/v22.14.0/node-v22.14.0-linux-x64.tar.gz
tar xf ~/node-v22.14.0-linux-x64.tar.gz --strip-components=1 -C ~/
rm -f ~/node-v22.14.0-linux-x64.tar.gz
mkdir -p ~/apps && cd ~/apps
git clone https://github.com/Kepners/pvtkrrx.git
cd pvtkrrx && npm ci --omit=dev
PORT=15000 npm run server:setup

Configure proxypass for HTTPS and point setup at that final public origin. If proxypass only gives you a subpath route or a broken install URL, use LAN Bridge for stable addon URLs.

RapidSeedbox Runbook

Lean: No SSH Premium: SSH + Custom Software

Configure Page Fields

  1. Install qBittorrent and Prowlarr from the RapidSeedbox dashboard (one-click installers on Premium, pre-installed on Lean).
  2. On your self-host server /configure page, select Remote Seedbox and pick RapidSeedbox from the provider dropdown.
  3. Fill in the connection fields:
FieldValue
Prowlarr URLhttps://<box>.rapidseedbox.com/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://<box>.rapidseedbox.com/qbittorrent
qBit Username/PasswordYour RapidSeedbox dashboard credentials
File Server URLhttps://<box>.rapidseedbox.com
File Server Authuser:password (dashboard credentials)
Path Mapping/home// (auto-filled by preset)
  1. Click Test Connection, then Save.

Lean plans have no SSH — Remote Seedbox route with hosted PVTKRRX is the only option. Premium plans have SSH and can also self-host PVTKRRX directly. Lean to Premium migration keeps the same provider; switch plan when direct addon hosting becomes needed.

Advanced: Host PVTKRRX directly on RapidSeedbox (Premium only)
ssh user@<box>.rapidseedbox.com
mkdir -p ~/apps && cd ~/apps
git clone https://github.com/Kepners/pvtkrrx.git
cd pvtkrrx && npm ci --omit=dev
PORT=15000 npm run server:setup

Expose the chosen port through your HTTPS routing layer, then set that exact HTTPS origin in setup. Check RapidSeedbox docs for the custom app routing details.

Bytesized Runbook

Appbox + Connect Modes Connect Requires Docker + Root

Configure Page Fields

  1. Install qBittorrent and Prowlarr from the Bytesized app dashboard.
  2. On your self-host server /configure page, select Remote Seedbox and pick Bytesized from the provider dropdown.
  3. Fill in the connection fields:
FieldValue
Prowlarr URLhttps://<appbox>.bytesized-hosting.com/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://<appbox>.bytesized-hosting.com/qbittorrent
qBit Username/PasswordYour Bytesized appbox credentials
File Server URLhttps://<appbox>.bytesized-hosting.com
File Server Authuser:password (appbox login)
Path Mapping/home// (auto-filled by preset)
  1. Click Test Connection, then Save.

Use the Remote Seedbox route with hosted PVTKRRX first. Bytesized Connect is only needed when you control a server with Docker and root access. If your plan does not provide clean routing for custom app root paths, use LAN Bridge instead.

Swizzin Runbook (Own VPS or Swizzin Provider)

Best Direct-Host Option Requires Root/Sudo On VPS

Configure Page Fields

  1. Install qBittorrent and Prowlarr via Swizzin (box install qbittorrent prowlarr).
  2. On your self-host server /configure page, select Remote Seedbox and pick Swizzin from the provider dropdown.
  3. Fill in the connection fields using your reverse-proxy HTTPS URLs:
FieldValue
Prowlarr URLhttps://seedbox.example.com/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://seedbox.example.com/qbittorrent
qBit Username/PasswordYour Swizzin panel credentials
File Server URLhttps://seedbox.example.com/files
File Server AuthDepends on your Nginx config — set user:password if auth is required
Path Mapping/home// (auto-filled by preset)
  1. Click Test Connection, then Save.

Swizzin URL subpaths depend entirely on your Nginx reverse proxy config. Use the exact paths from your panel. This is the best option for direct hosting since you control root, Nginx, and domain routing.

Direct hosting: Run PVTKRRX on your Swizzin VPS
git clone https://github.com/Kepners/pvtkrrx.git
cd pvtkrrx && npm ci --omit=dev
PORT=7000 npm run server:setup

Reverse proxy a dedicated domain or subdomain to the local HTTP port you choose in setup (default 7000), and run npm run server:install-service later if you want systemd startup.

HostingByDesign Runbook

SSH + box Tooling Good For Direct Hosting

Configure Page Fields

  1. Install qBittorrent and Prowlarr via the box command.
  2. On your self-host server /configure page, select Remote Seedbox and pick HostingByDesign from the provider dropdown.
  3. Fill in the connection fields:
FieldValue
Prowlarr URLhttps://<slot>.hostingby.design/prowlarr
Prowlarr API KeyFound in Prowlarr → Settings → General
qBittorrent URLhttps://<slot>.hostingby.design/qbittorrent
qBit Username/PasswordYour HBD slot credentials
File Server URLhttps://<slot>.hostingby.design
File Server Authuser:password (slot login)
Path Mapping/home// (auto-filled by preset)
  1. Click Test Connection, then Save.

HBD has SSH and box tooling available on app hosting slots, making it a good option for direct PVTKRRX hosting too. If self-hosting, set PVTKRRX_ALLOWED_WEB_ORIGINS to your exact HTTPS origin.

Other Provider Runbook (Generic)

Use This If Not Listed

Configure Page Fields

  1. On your self-host server /configure page, select Remote Seedbox and leave provider as Custom / Other.
  2. Find the following from your provider's control panel and fill them in:
FieldWhere To Find It
Prowlarr URLHTTPS URL from your provider's app panel or reverse proxy config
Prowlarr API KeyProwlarr → Settings → General → API Key
qBittorrent URLHTTPS WebUI URL from your provider's app panel
qBit Username/PasswordqBittorrent WebUI login (check provider panel or qBit settings)
File Server URLThe HTTPS URL that serves your download directory as browsable files
File Server Authuser:password if file access is behind HTTP Basic Auth — leave blank if public
Path Mapping: FromqBittorrent's save path prefix (e.g. /home/user/downloads/)
Path Mapping: ToThe matching path on the file server URL (e.g. / or /files/)
  1. Click Test Connection to verify Prowlarr and qBittorrent respond, then Save.

Only use Remote Seedbox when your Prowlarr, qBittorrent, and file server endpoints are intentionally public over HTTPS and authenticated. If any endpoint is not publicly reachable, use PC Local + LAN Bridge and keep the seedbox as backend only.

Advanced: Self-host PVTKRRX on your seedbox

Requirements: SSH access, Node.js, long-running process support (screen, tmux, systemd), and an HTTPS endpoint.

git clone https://github.com/Kepners/pvtkrrx.git
cd pvtkrrx && npm ci --omit=dev
PORT=7000 npm run server:setup

Reference Links

Whatbox: Managed Links, Installing Software, SSH
Ultra.cc: Install Node.js, Generic Software, Assigned Ports
SeedHost: Node Install, Shared App FAQ, Available Apps
Feral: Generic Install, Node.js, Proxypass
RapidSeedbox: Lean FAQ, SSH Access, Premium One-Click / Custom
Bytesized: Connect, SSH, Custom App Example
Swizzin: Swizzin Docs, Swizzin GitHub
HostingByDesign: box Basics, App Example