# Tor Browser 16.0 warning fix identified for Whonix custom workstation users

> **Key takeaway:** A new error prompt in Tor Browser 16.0 regarding external Tor connections can be resolved by aligning the control port configuration with the Whonix-Gateway's onion-grater service.

**Published:** 2026-11-20T14:17:16+00:00 
**Source:** Whonix Privacy &amp; Anonymity OS Blog 
**Category:** mobile-hardened 
**Canonical URL:** https://fosswire.org/news/tor-browser-160-warning-fix-identified-for-whonix-custom-wor.html 

## Summary
Users of custom Whonix workstations have reported a new warning message appearing in Tor Browser 16.0. The error states that the browser cannot communicate with the external Tor application, which may cause certain features to malfunction. While standard Whonix-Workstation installations do not exhibit this issue, users following manual hardening guides for custom Linux setups have encountered the prompt.

The issue stems from a change in Tor Browser 16.0, which now explicitly alerts users when it cannot reach a Tor control port. In previous versions, failures to connect to the control port often occurred silently, leaving features like circuit display or onion authentication non-functional without notifying the user. The fix involves correcting the port mismatch between the browser configuration and the Whonix-Gateway's listening service.

## Technical cause and configuration fixes
- **Feature Change:** Tor Browser 16.0 introduced a new error prompt for setups using an external Tor instance that fails to provide a connection to the Tor control port.
- **Port Mismatch:** The Whonix wiki for custom workstations may still suggest setting `extensions.torlauncher.control_port` to 9052, whereas the Whonix-Gateway `onion-grater.service` listens on port 9051.
- **Mitigation via Port Alignment:** Users can resolve the warning by updating `extensions.torlauncher.control_port` to 9051 or by setting `TOR_CONTROL_PORT=9051` in `/etc/environment`.
- **Alternative Configuration:** For users who do not require control port features, setting the environment variable `TOR_PROVIDER=none` allows Tor Browser 16.0 to apply only SOCKS proxy settings and bypass the control port check entirely.

## Why it matters
This update highlights the importance of maintaining synchronized configurations between specialized privacy components like Whonix-Gateway and upstream software like Tor Browser. For security researchers and users building hardened custom Linux environments, it demonstrates how upstream feature additions can trigger warnings in non-standard, highly compartmentalized setups.