Fix SWG bypass Recovering, Paused & connection errors on Mac

Troubleshoot Bypassing, Recovering, and Paused states in SWG bar 2.4.12—check macOS network extension approvals, hardware IPv4 interfaces, and HTTP/3 fallback.

SWG bar · Updated

When you enable Bypass SWG on a domain in SWG bar 2.4.12, the status row transitions through states such as Bypassing, Recovering, or Paused. Understanding what each state checks—and what network conditions are required—lets you resolve bypass issues quickly without leaving broken rules active.

Understand Bypassing, Recovering, and Paused

State What it means What to check first
Bypassing The native network extension rule is active for new connections to this hostname while SWG bar stays running. Check the verification message underneath: if it warns "No connection through the native extension has been observed yet", reload the page or restart the app making the request.
Recovering SWG bar is re-applying saved domain rules or waiting for the local network extension worker to settle. Wait a few seconds, ensure your trial or license is active under Settings → Trial & Activation, and keep SWG bar open.
Paused Bypass is not active—typically after quitting SWG bar, pausing due to an expired trial/license, or an extension/network error. Approve any pending macOS system extension prompts in System Settings, verify your physical network connection, and inspect the inline error beside the control.

Verify macOS System Extension and license requirements

SWG bar uses a signed macOS Network Extension (SWGBar system extension + network filter/proxy configuration) to route selected hostnames directly over a physical interface without changing global system proxy settings:

  1. Check macOS System Settings → Privacy & Security (and Network → Filters) to ensure the SWGBar system extension and network configuration are allowed. If macOS requested a restart during initial approval, complete it.
  2. Confirm you have an active 14-use-day free trial or paid license in Settings → Trial & Activation.
  3. Keep SWG bar running in your menu bar—quitting the app immediately stops active bypass and sets saved rules to paused until the app reopens.

Check hardware IPv4 egress and HTTP/3 fallback

Per-domain SWG bypass in SWG bar 2.4.12 requires a connected physical (Hardware) network interface with an available IPv4 gateway (such as built-in Wi-Fi or Ethernet). Two common network behaviors explain most verification warnings:

  • VPN or virtual-only egress: If your Mac forces all outbound routes solely through a Virtual VPN tunnel with no reachable physical IPv4 path, bypass verification can fail with "No connected physical interface with an IPv4 gateway". Read macOS VPN virtual interfaces vs. SWG inspection.
  • Browser HTTP/3 (QUIC) and existing connections: Chrome and other browsers may hold open HTTP/3 UDP streams or pooled TLS sockets established before you enabled bypass. SWG bar’s native bypass falls back HTTP/3 connections to HTTPS over TCP on new connections, so refresh or restart the browser/tool after seeing Bypassing.

Clear or verify rules via CLI

If a rule becomes stuck or an inline error appears when toggling bypass off, keep SWG bar open and inspect or clear rules from Terminal using the CLI:

swgbar bypass status
swgbar bypass disable <domain>
swgbar bypass clear
swgbar probe <domain>

Never assume a rule is removed if the app reports a restore error—keep SWG bar running until swgbar bypass status confirms the rule is cleared, or review How to bypass SWG on a Mac for full lifecycle behavior.