Seedbox Controller

Three torrent server entries for WireNets operators.

A single WireGuard-facing switchboard for the current WireNets qBittorrent proxy, SEEDBOX-1, and the 140 storage box. Existing working links stay available, with seedbox access kept in one clean control surface.

TOR3 switchboard 3 servers
Seedbox100 GB
ClientsqBit + ruTorrent
ModeOperator
public tracker lane credentials private WireGuard ready
qBittorrent ruTorrent SSH Seedbox #5124 Storage 140 WireGuard Public Tracker

Server Options

Pick the torrent control panel you want to enter.

This page exposes launch points and non-secret access notes only. Passwords stay in the private operator notes instead of being published into the site HTML.

Existing

WireNets Current qBittorrent

1

The current WireNets torrent client that is already mounted on the live /tor/ proxy.

Client
qBittorrent
Public path
https://wirenets.ca/tor/
File access
Nextcloud C1: /TOR3 Storage140 Torrents
Backend
Hidden behind WireNets
Access
Existing WireNets torrent login

HDD / Public Tracker

SEEDBOX-1

2

Seedbox #5124 with qBittorrent, ruTorrent, SSH, and the Nextcloud /Seedbox5124 storage mount.

Seedbox
Seedbox #5124
Public path
https://wirenets.ca/tor3/seedbox1/
Backend
Hidden behind WireNets
Username
wirenets.abel
Password
private ops note

3rd Box

Storage 140 Torrent Box

3

The third torrent panel on the 140 storage server, kept separate from the current WireNets proxy.

Public path
https://wirenets.ca/tor3/storage140/
File access
Nextcloud C1: /TOR3 Storage140 Torrents
Backend
Hidden behind WireNets
Role
Storage torrent box
Access
Use existing operator credentials

Access Pattern

Keep the current proxy, add the switchboard, and leave secrets out of public code.

01

Current live client

The existing /tor/ qBittorrent proxy remains one of the server choices.

02

Seedbox route

SEEDBOX-1 links to both torrent clients and shows the SSH entry point for uploads and file access.

03

Private credentials

The username can be shown for convenience; passwords stay in private ops notes or a server-side vault.