Connection Errors Behind a VPN or Proxy: Captyne Network Settings

Captyne connects to the internet to sign you in, check for updates, download presets and models, and run cloud transcription. On networks that require a VPN or proxy, these requests can fail unless Captyne uses the same connection.

Symptoms

• Sign-in fails or the panel says it can't reach the server
• Managed API or cloud transcription fails or times out
• Marketplace previews or the Whisper model won't download

Choose a connection mode

Open Captyne's Settings (gear icon) → Network tab and pick a Connection Mode:

• Direct: no proxy. Use this on normal home or office internet.
• Auto Detect: Captyne looks for a running local proxy app, such as Clash on 127.0.0.1:7890, and uses it automatically.
• System Proxy: uses the proxy configured in Windows or macOS.
• Custom: enter the proxy yourself, HTTP or SOCKS5, with host and port.

Common local ports:

The setting applies to all of Captyne's connections, including sign-in.

VPN apps in TUN / "global" mode

If your VPN app captures all traffic (often called TUN or enhanced mode), choose Direct. The VPN already routes Captyne's traffic, and adding a proxy on top can break the connection.

Some VPN apps leave the system proxy switched on after you quit them. If Captyne suddenly can't connect with System Proxy, switch to Direct.

Still failing?

1. Check the VPN or proxy works in your browser by opening captyne.com.
2. Switch modes: try Auto-detect, then a custom proxy with the exact port your VPN app shows.
3. Restart the Captyne panel after changing the setting.

Offline / Local transcription needs no internet once the model is downloaded, so it's a reliable fallback on restricted networks.