TorSentinel Monitor — Vuze Setup & Test

1) Monitor vs Armor

Monitor (this guide)

Real-time watch for announce IP leaks.
Safelist your known locations (home IP, VPN egress, seedbox, or third-party SOCKS5).
Email/Telegram alerts and optional webhooks.

Armor

Includes Monitor + first-party SOCKS5 proxy.
Enforce announce routing via Safelist.
If you already have a third-party SOCKS5, Monitor works with it — just Safelist its domain/IP.

2) Add your location to Safelist

Safelist screen adding a home/VPN IP or proxy domain — Safelist → Add IP, /24 range, or proxy domain.

Quick reference

Type:  IP or Domain
Value: 203.0.113.42   (VPN IP example)   OR   proxy.yourprovider.example
Label: My VPN IP  /  My SOCKS5

Tip: If your provider rotates egress IPs, Safelist the /24 range (e.g., 203.0.113.0/24) or Safelist the proxy domain if it maps to a pool.

3) Using a third-party SOCKS5 with Monitor

TorSentinel Monitor observes tracker announces; it does not require TorSentinel Armor. If you already use a SOCKS5 from your VPN, seedbox, or provider, keep using it:

Vuze: Tools → Options → Connection → Proxy.
Enable proxying of tracker communications, choose SOCKS, enter Host/Port and Auth.
Enable Use proxy for hostname lookups.
Add the proxy’s domain or IP to Safelist so announces are marked Covered.

Vuze proxy settings for trackers and hostname lookups — Vuze → Connection → Proxy.

Quick reference

Proxy Type:  SOCKS5 (Vuze “SOCKS”)
Apply To:    Trackers (required), Peers (optional)
Host/Port:   your.proxy.example.com : 1080
Auth:        As provided by your provider
Option:      Use proxy for hostname lookups

Important: Add your.proxy.example.com (or its IP) to Safelist so Monitor recognizes announces as Covered.

4) Vuze announce checks

1

Open Tools → Options. In Connection → Advanced Network Settings, bind Vuze to your VPN adapter if you use one.

2

In Connection → Proxy, enable tracker proxying (and hostname lookups) if you use a third-party SOCKS5. Peer proxying is optional.

3

Ensure your Safelist includes the VPN egress IP (or /24) and/or the proxy domain/IP so announces show as Covered.

Vuze network and proxy overview — Bind to VPN interface (optional) and enable SOCKS for trackers.

5) Start the Test Torrent

Go to Services → Torrents → Test Torrent in your dashboard and add the magnet link in Vuze. Wait for an announce cycle (about 1–3 minutes).

Torrents page showing Test Torrent monitoring

Click Copy magnet and add it in Vuze.
Wait for one announce cycle.
Confirm the dashboard shows a recent Last Seen.

No content is downloaded. The test torrent is metadata-only and exists to validate announce routing.

6) Alerts & notifications

Email

Add your address and click Save.
Confirm the verification email.

Telegram

Click Connect Telegram and press Start in the bot.

7) Verify coverage

Covered — announce source matches your Safelist (expected home/VPN/seedbox/proxy IP).
Uncovered — announce source is outside Safelist. Check VPN binding, proxy settings, or interface selection.

FAQ & Troubleshooting

Does Monitor require TorSentinel’s SOCKS5?

No. Monitor works with any egress path (direct, VPN, seedbox, or a third-party SOCKS5). Just add the egress domain/IP to Safelist so announces are marked Covered.

My VPN or proxy rotates IPs — how do I keep coverage?

Ask your provider for a stable /24 and add that range in Safelist (e.g., 198.51.100.0/24). If rotation spans multiple ranges, Safelist the proxy domain or all ranges you use.

Test torrent doesn’t update

Verify the torrent is added and not paused.
If on VPN, ensure Vuze is bound to the VPN interface.
Check Safelist includes your current IP/domain or /24.

Switching to Armor later

Follow the TorSentinel Armor — Vuze guide to enable TorSentinel’s SOCKS5. Your Monitor settings carry over.