Skip to content

v3.4.2 — Direct SCGI Connection for rTorrent & Diagnostic Logging

Choose a tag to compare

View all tags
@got3nks got3nks released this 18 Mar 16:47
· 45 commits to main since this release
v3.4.2
481fcd4

✨ Added

  • rTorrent SCGI connection modes — connect directly to rTorrent via SCGI TCP or Unix socket, bypassing the need for an HTTP proxy (nginx/ruTorrent). Three modes available: HTTP (default, existing behavior), SCGI (direct TCP), and SCGI Socket (Unix domain socket)
  • Connection mode selector — new dropdown in both Settings and Setup Wizard for rTorrent instances, with conditional field visibility based on the selected mode (host/port for TCP modes, socket path for Unix socket, XML-RPC path/auth/SSL for HTTP only)
  • SCGI environment variables — RTORRENT_MODE and RTORRENT_SOCKET_PATH for Docker/env-based configuration
  • Data fetch diagnostics — warnings logged when a connected client suddenly returns empty data, when an individual client fetch takes >10s, or when the full batch cycle exceeds 15s
  • aMule fetch diagnostics — warning logged when getUpdate() returns no data, indicating potential connection issues
  • Config test error logging — failed connection tests now log the error message (previously only showed pass/fail emoji)
  • aMule EC connection recovery — consecutive request timeouts now trigger automatic socket destruction and reconnection, fixing a bug where stale connections would hang indefinitely

Full Changelog: v3.4.1...v3.4.2

Assets 2
Loading