Tor Access Shifted to Explicit Administrator Opt-In

Open-source Bitcoin payment processor BTCPay Server has modified how its standard deployment stack handles Tor integration. Following the release of version 2.4.5, administrators maintaining a standard BTCPay Docker setup must now intentionally opt into Tor during their next system configuration or update to retain onion address accessibility.

Previously, Tor functionality was bundled automatically within the core software components. Under the updated architecture announced on October 5 and officially released to GitHub on October 6, Tor has been separated into an optional deployment fragment named opt-add-tor.

According to official project documentation, existing data stored in current Tor volumes remains intact during the transition. However, continuous connectivity via hidden services requires administrators to actively include and execute the Tor fragment within their manifest.

Understanding BTCPay Docker Setup Requirements for Tor

To evaluate current server configurations, system administrators can execute the inspection command btcpay-fragments show. This command reports active manifest details alongside stored additional or excluded fragments without making live system changes.

Executing commands that alter fragments requires root privileges and applies the updated stack environment immediately. BTCPay Server advises operators who rely on onion routing to carefully review deployment settings before triggering their next update.

New Security Controls Restrict Outbound Private Requests

Alongside the Tor architectural adjustment, version 2.4.5 introduces a breaking security restriction on outbound HTTP traffic. To mitigate server-side request forgery risks, outbound connections directed to private-network destinations are now blocked by default.

This default blocking policy impacts several automated functions, including Lightning network connections, LNURL requests, invoice notification URLs, and webhooks. System operators who intentionally route connections to internal or private services must specify permitted destinations through a setting designated as ssrfexceptions.

Project guidelines instruct administrators to restart the application after adjusting exceptions and thoroughly test affected integrations to ensure uninterrupted payment processing.