Operators using the Bitcoin payment platform BTCPay Server via its standard Docker deployment will need to explicitly enable Tor in their next configuration update to maintain access to onion services. The change removes Tor from the default set of bundled components, requiring administrators to add it manually. In version 2.4.5, released on October 6 according to the official GitHub release log, the project documented this shift in deployment behavior. The update affects all new installations and existing systems during their next rebuild or upgrade. BTCPay advises users to review the deployment modifications before proceeding. After updating, administrators can activate Tor by running the command: sudo btcpay-fragments add opt-add-tor Tor. The software confirms that existing data remains stored in current Tor volumes, preserving access to onion addresses while requiring the explicit inclusion of the Tor fragment. Configuration status can be checked with the command btcpay-fragments show, which reports saved and excluded fragments without altering the setup. Fragment-related commands require root privileges and must be followed by an immediate reapplication of the configuration. The release also introduces a security enhancement that blocks outbound HTTP requests to private network destinations by default for Lightning Network connections, LNURL requests, invoice notification URLs, and webhooks. This measure aims to reduce exposure to server-side request forgery attacks. Users relying on private services must now add those destinations to the ssrfexceptions list through configuration changes, then restart the application and test the affected integrations. The update preserves backward compatibility for existing data while shifting responsibility for Tor activation from automatic inclusion to deliberate configuration.