macOS app 4.1.3 (2456), connecting to surf.eduvpn.nl. Profile is OpenVPN.
First connect attempt after launching the app always fails.
It goes Configuring → Connecting, sits for ~7s, then disconnects with cannotStartTunnel.
Immediately hitting connect again works — connects in under a second. I think I can reproduce this on every launch.
I checked the following:
- Not firewall-related (block-all is off, both eduVPN entries are Allow in socketfilterfw)
- Survives an app reset and a reinstall.
- No TCP-only option in 4.1.x to test whether forcing TCP avoids it (see #595).
Relevant app log lines from a failing-then-succeeding sequence:
2026年06月22日 10:19:54.846 initializeTunnelManager: tunnelManager does not have saved server info
2026年06月22日 10:19:57.173 ServerDetailViewModel.init: Server: https://surf.eduvpn.nl/, Connection status: Invalid
2026年06月22日 10:19:57.309 proceedToConnect(shouldPreferTCP:): shouldPreferTCP = false, state = notStarted
2026年06月22日 10:19:57.309 State changed to Contacting the server... (from Not connected)
2026年06月22日 10:19:57.712 State changed to Configuring... (from Contacting the server...)
2026年06月22日 10:19:57.712 proceedToConnect(shouldPreferTCP:): Got openVPN VPN config with shouldFailover = true
2026年06月22日 10:20:00.561 Connection status: disconnected
2026年06月22日 10:20:00.561 State changed to Not connected (from Configuring...)
2026年06月22日 10:20:00.601 Connection status: connecting
2026年06月22日 10:20:00.602 State changed to Connecting... (from Not connected)
2026年06月22日 10:20:07.725 Connection status: diconnecting
2026年06月22日 10:20:07.726 State changed to Disconnecting... (from Connecting...)
2026年06月22日 10:20:07.760 Connection status: disconnected
2026年06月22日 10:20:07.760 State changed to Not connected (from Disconnecting...)
2026年06月22日 10:20:07.785 Error: ServerDetailViewModel: proceedToConnect(shouldPreferTCP:): Error: cannotStartTunnel
2026年06月22日 10:21:11.257 proceedToConnect(shouldPreferTCP:): shouldPreferTCP = false, state = notConnected
2026年06月22日 10:21:11.257 State changed to Contacting the server... (from Not connected)
2026年06月22日 10:21:11.426 State changed to Configuring... (from Contacting the server...)
2026年06月22日 10:21:11.426 proceedToConnect(shouldPreferTCP:): Got openVPN VPN config with shouldFailover = true
2026年06月22日 10:21:11.482 Connection status: connecting
2026年06月22日 10:21:11.482 State changed to Connecting... (from Configuring...)
2026年06月22日 10:21:12.267 Connection status: connected
2026年06月22日 10:21:12.268 State changed to Connected (from Connecting...)
The 7s-then-abort on the first attempt looks like the failover probe timing out rather than failing over. The config has shouldFailover = true.
Possibly related: #586 (first connect fails, but is phrased specifically towards menu bar + multiple profiles), #595 (TCP-only removed).
Happy to provide full logs or whatever info you need.
macOS app 4.1.3 (2456), connecting to surf.eduvpn.nl. Profile is OpenVPN.
First connect attempt after launching the app always fails.
It goes Configuring → Connecting, sits for ~7s, then disconnects with cannotStartTunnel.
Immediately hitting connect again works — connects in under a second. I think I can reproduce this on every launch.
I checked the following:
* Not firewall-related (block-all is off, both eduVPN entries are Allow in socketfilterfw)
* Survives an app reset and a reinstall.
* No TCP-only option in 4.1.x to test whether forcing TCP avoids it (see #595).
Relevant app log lines from a failing-then-succeeding sequence:
```bash
2026年06月22日 10:19:54.846 initializeTunnelManager: tunnelManager does not have saved server info
2026年06月22日 10:19:57.173 ServerDetailViewModel.init: Server: https://surf.eduvpn.nl/, Connection status: Invalid
2026年06月22日 10:19:57.309 proceedToConnect(shouldPreferTCP:): shouldPreferTCP = false, state = notStarted
2026年06月22日 10:19:57.309 State changed to Contacting the server... (from Not connected)
2026年06月22日 10:19:57.712 State changed to Configuring... (from Contacting the server...)
2026年06月22日 10:19:57.712 proceedToConnect(shouldPreferTCP:): Got openVPN VPN config with shouldFailover = true
2026年06月22日 10:20:00.561 Connection status: disconnected
2026年06月22日 10:20:00.561 State changed to Not connected (from Configuring...)
2026年06月22日 10:20:00.601 Connection status: connecting
2026年06月22日 10:20:00.602 State changed to Connecting... (from Not connected)
2026年06月22日 10:20:07.725 Connection status: diconnecting
2026年06月22日 10:20:07.726 State changed to Disconnecting... (from Connecting...)
2026年06月22日 10:20:07.760 Connection status: disconnected
2026年06月22日 10:20:07.760 State changed to Not connected (from Disconnecting...)
2026年06月22日 10:20:07.785 Error: ServerDetailViewModel: proceedToConnect(shouldPreferTCP:): Error: cannotStartTunnel
2026年06月22日 10:21:11.257 proceedToConnect(shouldPreferTCP:): shouldPreferTCP = false, state = notConnected
2026年06月22日 10:21:11.257 State changed to Contacting the server... (from Not connected)
2026年06月22日 10:21:11.426 State changed to Configuring... (from Contacting the server...)
2026年06月22日 10:21:11.426 proceedToConnect(shouldPreferTCP:): Got openVPN VPN config with shouldFailover = true
2026年06月22日 10:21:11.482 Connection status: connecting
2026年06月22日 10:21:11.482 State changed to Connecting... (from Configuring...)
2026年06月22日 10:21:12.267 Connection status: connected
2026年06月22日 10:21:12.268 State changed to Connected (from Connecting...)
```
The 7s-then-abort on the first attempt looks like the failover probe timing out rather than failing over. The config has shouldFailover = true.
Possibly related: #586 (first connect fails, but is phrased specifically towards menu bar + multiple profiles), #595 (TCP-only removed).
Happy to provide full logs or whatever info you need.