BTCPay Docker users must opt into Tor at next update to keep onion access
Existing Docker-based BTCPay Server deployments must explicitly select Tor during their next setup or update, though stored Tor data is retained.
Operators running Docker-based BTCPay Server deployments will need to explicitly select Tor when they next go through setup or apply an update, according to a notice from CryptoSlate. Without that opt-in step, existing installations stand to lose their onion service access.
What operators need to know
- The Tor option must be selected manually at the next setup or update.
- Previously stored Tor data is preserved and does not need to be regenerated.
- The requirement applies to existing installations, not only new ones.
The practical effect is that an installation could keep running while quietly dropping its .onion reachability if the operator accepts defaults during an upgrade rather than checking the Tor box.
BTCPay Server is an open-source, self-hosted bitcoin payment processor that merchants and individuals run on their own infrastructure. Tor support lets those deployments expose an onion address, which can be useful for users who prefer not to route payment traffic over the public internet.