PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For the current standard BTCPay Server Docker deployment, Tor is an opt-in feature. After upgrading to BTCPay Server 2.4.5 (released October 5, 2026), enable it with sudo btcpay-fragments add opt-add-tor. The deployment keeps existing Tor data in its current volumes. BTCPay’s web interface and Bitcoin Core’s peer-to-peer service then use separate v3 .onion hostnames, which you can read from the generated Tor volume.
This setup can make a home or office payment server reachable without port forwarding, public DNS, or a fixed Lightning IP. It does not make the operator anonymous, and it cannot guarantee that every BTCPay, Bitcoin, Lightning, or plugin connection avoids the clearnet. Follow the release-specific Docker workflow first; use a hand-written torrc only when you intentionally manage the onion service outside BTCPay’s supported deployment.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What you are configuring
A BTCPay installation can expose more than one onion service. The web service lets a merchant or customer reach the BTCPay payment interface over Tor. Bitcoin Core can separately publish an onion service for peer-to-peer connections. These services have different hostnames, ports, and security implications.
Onion addresses generated by current Tor v3 services are 56 characters before the .onion suffix (excluding a scheme such as http://). The hostname is public; the private key that proves control of the service must remain secret.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Current Docker behavior
BTCPay Server 2.4.5 changed the standard Docker deployment from Tor included by default to Tor available as an opt-in fragment. The dated release announcement is the authority for that behavior: BTCPay Server 2.4.5 release announcement. An older deployment FAQ still describes Docker Tor as enabled by default, so do not rely on that statement when operating 2.4.5 or a later release.
What Tor does and does not provide
- It can avoid opening several inbound firewall ports and configuring NAT redirection.
- It can remove the need for public DNS and a DNS-based HTTPS certificate for the onion address.
- It can provide reachability when a home connection has no fixed public IP, including for Lightning-related access patterns.
- It does not anonymize the operator or automatically force all application traffic through Tor.
- It does not prevent someone from reaching a separately exposed clearnet address.
BTCPay’s deployment FAQ explicitly warns that its software, plugins, and connected services are too complex to guarantee that no clearnet data leaks. Treat onion access as an additional route, not as a complete privacy boundary.
Prerequisites and deployment assumptions
The steps below assume the official BTCPay Docker deployment, which BTCPay recommends for self-hosted production. Its operator guide covers installation, environment variables, backups, updates, and troubleshooting: BTCPay Server Operator Guide. The generated stack commonly includes BTCPay Server, PostgreSQL, NBXplorer, Bitcoin Core, Nginx with automatic HTTPS certificates, and Tor; Lightning and other components are optional. See the deployment repository’s current component list and provider-specific instructions at the official Docker repository README.
Hardware baseline
BTCPay documentation accessed October 13, 2026 lists 2 GB of RAM and 80 GB of storage with pruning enabled as minimums when running Bitcoin and Lightning nodes. Those figures are minimum requirements, not capacity recommendations: a non-pruned Bitcoin chain, indexes, logs, backups, and multiple Lightning channels require more storage and memory.
Before changing the deployment
- Record the installed BTCPay version and confirm that your Docker deployment is the supported installation method.
- Back up the BTCPay data and record how you restore it before changing fragments.
- Confirm that you have shell access with
sudoand can inspect Docker volumes. - Decide whether you need only the web onion service, the Bitcoin P2P onion service, or both.
- Keep a clearnet administration route available until the onion route has been tested.
Enable Tor in the standard BTCPay Docker deployment
Use the release-specific fragment rather than adding a host-level Tor configuration by hand. The following is the enablement procedure documented for BTCPay Server 2.4.5.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
- Update the BTCPay Docker deployment using your normal, documented update procedure. Check the deployed version after the update.
- Add the optional Tor fragment:
sudo btcpay-fragments add opt-add-tor - Allow the deployment to regenerate and restart the affected services. Do not delete the existing Tor volumes; the 2.4.5 announcement says existing Tor data is preserved in the current Tor volumes.
- Inspect the resulting containers and logs. Confirm that the Tor service is running and that the generated service directory contains hostname files.
- Open the web onion address from a Tor-enabled browser or another Tor client, then sign in and verify that payment pages, wallet operations, and any Lightning functions you need behave as expected.
Do not assume that a fragment name or default remains unchanged forever. BTCPay’s configuration reference warns that options and defaults can change between releases. Match the instructions to the version actually installed: BTCPay Server Configuration Reference.
If you are upgrading an existing Tor installation
Run the fragment after the update if your previous deployment relied on Tor. The release announcement states that Tor data is preserved in the existing volumes, so the onion identity should remain stable when those volumes are retained. If the hostname changes, first verify that the deployment is using the original generated Tor volume rather than a newly created or manually renamed volume.
Find the BTCPay and Bitcoin P2P onion addresses
The official deployment FAQ gives paths inside the generated Docker volume. These paths apply to an unmodified deployment; customized volume names or data directories require you to locate the equivalent generated Tor volume.
| Service | Command | Purpose |
|---|---|---|
| BTCPay web interface | cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname |
Prints the onion hostname used to reach the payment server and administration interface. |
| Bitcoin Core P2P | cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname |
Prints the onion hostname advertised for Bitcoin peer connections. |
Copy the complete line, including the .onion suffix. An administrator can also find the P2P service in BTCPay’s Server Settings. The web and P2P names are not interchangeable: a browser request sent to the P2P hostname is not a BTCPay web request, and a Bitcoin peer cannot use the web service hostname for protocol traffic.
Protect the P2P hostname
BTCPay cautions against sharing the Bitcoin P2P onion service with untrusted parties. Bitcoin Core applies peer connection rules, but malicious peers can still create traffic that consumes resources or attempts to DDoS the node. Share the address only with peers and operators you trust, and monitor resource usage after making it available.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
BTCPay Tor settings and version-specific configuration
Some deployments expose Tor-related settings through BTCPay configuration options. Their names and defaults are version-sensitive, so use the reference matching your installed release rather than copying an old environment file.
| Setting | Command-line form | Role |
|---|---|---|
BTCPAY_TORRCFILE |
--torrcfile |
Path to a torrc file containing hidden-service directories. |
BTCPAY_TORSERVICES |
--torservices |
Associates service keys, onion hostnames, and ports for services displayed in Server Settings. |
BTCPAY_SOCKSENDPOINT |
--socksendpoint |
SOCKS endpoint used when BTCPay connects to onion URLs. |
The documented format for BTCPAY_TORSERVICES associates a service key, a .onion hostname, and a port. Do not infer a format from a different BTCPay release; consult the configuration reference and the generated environment used by your deployment.
How Bitcoin Core creates its onion service
Bitcoin Core’s P2P onion service is separate from the BTCPay web service. When Core is listening and has a working Tor connection, it can automatically create an onion service through Tor’s control socket API. This behavior is enabled by default; setting -listenonion=0 disables it.
Control authentication
Bitcoin Core can authenticate to Tor with the cookie file or with the -torpassword configuration option. Cookie authentication is the usual source of permission failures. The operating-system user running Bitcoin Core must be able to read Tor’s configured authentication cookie. Depending on how the containers or services are arranged, correcting group membership or the cookie file’s read permissions may be necessary.
When diagnosing this path:
- Check that Tor is running and that its control socket is reachable from the Bitcoin Core process.
- Verify which user runs Bitcoin Core and whether that user can read the authentication cookie.
- Review the Bitcoin Core debug log for authentication-cookie access errors.
- Enable verbose Tor messages with
-debug=tor, restart or reload as appropriate, and inspect the resulting log entries.
Confirm the address and protocol version
Bitcoin Core 22.0 and later support v3 onion services only. Tor removed v2 support beginning with Tor 0.4.6, so a v2 hostname cannot be repaired by changing a setting; it must be replaced with a v3 service. To inspect the local address, use Bitcoin Core’s getnetworkinfo RPC, the -netinfo command, or the debug log, as described in Bitcoin Core’s Tor documentation.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Manually managing a Tor onion service
A manually managed service is appropriate when you operate Tor independently of BTCPay’s Docker fragment or need a custom routing design. It increases your responsibility for directory ownership, permissions, restarts, backups, and compatibility. For a standard Docker installation, use the supported fragment workflow first.
Basic Tor configuration pattern
The Tor Project’s generic pattern defines a private service directory and maps a virtual onion port to a local listener:
Free tools Windows power users keep installed
One-click scans. No signup required.
HiddenServiceDir /var/lib/tor/btcpay_web/
HiddenServicePort 80 127.0.0.1:80HiddenServiceDir must be writable by the Tor process. The HiddenServicePort line above sends virtual port 80 to a web service listening on the local TCP address and port. Add one mapping for each service and port you intentionally expose; do not copy this example into a BTCPay container without checking how that container publishes its internal ports.
Start, inspect, and secure the service
- Place the directives in the Tor configuration used by your installation.
- Restart Tor using the service manager appropriate to your operating system.
- If Tor fails to start, read its log before changing additional settings; syntax errors and directory permissions are common causes.
- Read the generated
hostnamefile in the hidden-service directory to obtain the v3 address. - Keep the directory’s private key files readable only by the Tor process and authorized administrators.
The hostname file contains the public onion address. The other service files contain key material; anyone who obtains those keys can impersonate the onion service. Back them up securely if preserving the address matters, but do not place them in a public repository or an unencrypted shared backup.
Unix sockets and local exposure
The Tor Project notes that forwarding to a Unix socket can avoid exposing an onion service to a local network through a TCP listener. This is general Tor guidance, not a tested BTCPay Docker recipe. Confirm that the BTCPay reverse proxy and container permissions support the socket before adopting it; otherwise use the deployment’s documented network path.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Web onion versus Bitcoin P2P onion
| Characteristic | BTCPay web onion | Bitcoin Core P2P onion |
|---|---|---|
| Primary users | Merchants, administrators, and customers visiting payment pages. | Bitcoin peers communicating with the node. |
| Discovery | Generated BTCPayServer/hostname file or BTCPay settings. |
Generated BTC-P2P/hostname file, Server Settings, getnetworkinfo, or Core logs. |
| Protocol | HTTP or HTTPS application traffic through the BTCPay web stack. | Bitcoin P2P protocol. |
| Risk when widely shared | Unwanted login attempts and web-layer scanning; protect accounts and administration routes. | Untrusted peers can generate abusive traffic or attempt to DDoS the node. |
| Owner | Managed by the BTCPay deployment’s Tor configuration. | Created by Bitcoin Core through Tor’s control API when prerequisites are met. |
Home server or hosted server?
Both approaches can run BTCPay’s Docker deployment. A home or office server gives direct control of the hardware and can benefit most from onion reachability because Tor reduces dependence on inbound port forwarding and a fixed public address. A VPS or other hosted machine generally offers datacenter connectivity and remote administration, but this material does not establish provider reliability, pricing, or privacy for any particular host.
Choose based on operational requirements rather than assuming Tor removes all infrastructure concerns:
- Choose home hardware when you can maintain the machine, power, storage, backups, and local network securely.
- Choose hosted infrastructure when you need remote datacenter availability or cannot maintain hardware and connectivity yourself.
- Use either with Tor when the goal is an additional onion route; still patch the operating system, restrict administration, and monitor both onion and clearnet exposure.
Troubleshooting missing or unreachable onion services
The onion address disappeared after an update
Check whether the deployment was upgraded to 2.4.5 or later and whether the opt-in fragment is still present. Run sudo btcpay-fragments add opt-add-tor with the release’s documented procedure, then verify that the original generated Tor volume is mounted. Do not remove volumes while attempting to recreate the service.
The hostname file does not exist
Confirm that the Tor container is running and that you are using the actual generated volume name. The documented path is deployment-specific. Inspect Docker volumes and container mounts, then locate the corresponding BTCPayServer/hostname or BTC-P2P/hostname directory rather than creating a new key pair unnecessarily.
Bitcoin Core has no onion address
- Ensure Bitcoin Core is listening;
-listenonion=0explicitly disables automatic registration. - Confirm that Core can reach Tor’s control socket.
- Fix read permissions for the Tor authentication cookie, or configure the documented password method.
- Enable
-debug=torand inspect the debug log for authentication and registration errors. - Verify that the software versions support v3; Bitcoin Core 22.0 and later do not support v2.
The onion service starts but cannot reach BTCPay
Check the virtual-to-local port mapping, the reverse proxy listener, and container network connectivity. A Tor service can be healthy while forwarding to a stopped or incorrectly addressed local application. Test the BTCPay listener locally first, then test through a Tor client. If you edited a host-level torrc, compare it with the port and network arrangement generated by BTCPay before changing more directives.
The service works but leaks a clearnet link
Tor does not rewrite every URL emitted by BTCPay, plugins, wallets, Lightning services, or external integrations. Review application base URLs, callback endpoints, webhook destinations, and plugin settings. Keep the clearnet route controlled rather than assuming that an onion visit forces all subsequent requests through Tor.
Operational security and maintenance checklist
- Patch BTCPay, Bitcoin Core, Tor, the host operating system, and container images on a defined schedule.
- Keep the Tor service keys private and include them in encrypted, access-controlled backups if address continuity is required.
- Back up BTCPay data and document how to restore the Docker volumes before upgrades.
- Record which onion hostname belongs to the web service and which belongs to Bitcoin P2P; never publish the P2P address casually.
- Use strong administrator authentication and least-privilege access on the clearnet and onion interfaces.
- Monitor CPU, memory, disk, bandwidth, and connection counts for signs of abusive peer or web traffic.
- After every deployment change, test the onion hostname, payment creation, wallet access, and any required Lightning operation.
- Re-read the version-matched configuration reference before relying on a setting whose default may have changed.
Recommended configuration path
For a supported Docker installation, update to the intended BTCPay release, add the opt-in Tor fragment, retain the generated volumes, and read the two hostname files to distinguish web access from Bitcoin P2P access. Let Bitcoin Core create its own v3 onion service through Tor’s control API, correcting cookie permissions if registration fails. Only replace this workflow with a manually managed torrc when you are prepared to own the routing, permissions, key protection, and upgrade compatibility yourself.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
