Waiting for server response(Broken pipe (code=32))

[Hasan Ugurlu]

Hi, I was able to connect to my work server through Tunnelblick until today. I asked my colleagues, and they are connecting the server without issues.

I've read other conversations about similar errors, and I tried to do following.

- Check for Tunnelblick updates.

Up to date.

- Restart computer and internet router.

Done

- Check if my isp blocking vpn for my ip. 

Connected ExpressVpn with other devices using same ip address. But I'm not sure if they blocked the work server's ip.

I'm gonna contact my isp, but maybe there is another check that I should do, and I don't know about. That's why I wanted to ask here. Thank you.

2021-08-26 09:59:57.711071 MANAGEMENT: >STATE:1629997197,RESOLVE,,,,,,

2021-08-26 09:59:57.712431 TCP/UDP: Preserving recently used remote address: [AF_INET]******

2021-08-26 09:59:57.712638 Socket Buffers: R=[786896->786896] S=[9216->9216]

2021-08-26 09:59:57.712655 UDP link local: (not bound)

2021-08-26 09:59:57.712669 UDP link remote: [AF_INET]******

2021-08-26 09:59:57.712689 MANAGEMENT: >STATE:1629997197,WAIT,,,,,,

2021-08-26 09:59:57.712935 MANAGEMENT: CMD 'hold release'

2021-08-26 09:59:59.008066 write UDP: Broken pipe (code=32)

2021-08-26 10:00:03.939674 write UDP: Broken pipe (code=32)

2021-08-26 10:00:11.266465 write UDP: Broken pipe (code=32)

2021-08-26 10:00:57.147915 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

2021-08-26 10:00:57.148762 TLS Error: TLS handshake failed

2021-08-26 10:00:57.149013 SIGUSR1[soft,tls-error] received, process restarting

2021-08-26 10:00:57.149045 MANAGEMENT: >STATE:1629997257,RECONNECTING,tls-error,,,,,

2021-08-26 10:00:57.368641 MANAGEMENT: CMD 'hold release'

2021-08-26 ****** NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2021-08-26 10:00:57.371117 MANAGEMENT: >STATE:1629997257,RESOLVE,,,,,,

2021-08-26 10:00:57.373377 TCP/UDP: Preserving recently used remote address: [AF_INET]*******

2021-08-26 10:00:57.373716 Socket Buffers: R=[786896->786896] S=[9216->9216]

2021-08-26 10:00:57.373757 UDP link local: (not bound)

2021-08-26 10:00:57.373782 UDP link remote: [AF_INET]******

2021-08-26 10:00:57.373812 MANAGEMENT: >STATE:1629997257,WAIT,,,,,,

2021-08-26 10:00:57.374972 MANAGEMENT: CMD 'hold release'

2021-08-26 10:00:59.847179 write UDP: Broken pipe (code=32)

2021-08-26 10:01:03.666915 write UDP: Broken pipe (code=32)

[Tunnelblick developer]

The "broken pipe" errors usually mean your ISP (or something like the Great Firewall of China)  is actively blocking VPNs. If you can, try to connect from another network, for example, by creating a "hot spot" with your phone.

The problem could also be with your computer, but if you are not having trouble accessing the Internet otherwise, that's not likely.

[Hasan Ugurlu]

Thanks for fast response. I've contacted them and got green light on no restrictions for any vpns or any blockades. I also tried my hotspot, and still the same issue. That leaves me with something is wrong with computer. I'll try and see if I need any updates on my mac.

[Tunnelblick developer]

One more idea: restart your router and Cable/DSL/whatever modem and any switches you have on your network.

[Mike Weber]

Broken pipe could be a bad ta.key w/ UDP too right?

--
You received this message because you are subscribed to the Google Groups "tunnelblick-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tunnelblick-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tunnelblick-discuss/8458c9eb-fdbb-4699-93ae-cb602690ab63n%40googlegroups.com.

[Tunnelblick developer]

I don't think so. I think the OpenVPN server would just ignore the packets, not reset the connection. That's what I've seen before. (I've never seen the broken pipe error in this situation.)

[Hasan Ugurlu]

Just solved the problem. It was the firewall installed in the company's mac. IT person took care of it.

[Tunnelblick developer]

Thanks for letting everyone know!

[Vaseem Akram]

Hello @Hasan /Team

We are facing same issue can you please help us to fix it?

[Tunnelblick developer]

@Vaseem, please post the diagnostic info obtained by following the instructions at Read Before You Post.

[Hasan Ugurlu]

1 response above: Just solved the problem. It was the firewall installed in the company's mac. IT person took care of it.

[NICOLAS RAMZ]

I am having the exact same problem: every 10 minutes or so tunnelblick is disconnected. Checking the log shows the same error:

> 2022-07-19 16:32:45.728604 write UDP: Broken pipe (code=32)
> 2022-07-19 16:32:47.418218 write UDP: Broken pipe (code=32)
> 2022-07-19 16:32:50.499127 write UDP: Broken pipe (code=32)
> 2022-07-19 16:32:53.580301 write UDP: Broken pipe (code=32)
> ...

After these errors, tunnelblick automatically reconnects, but it takes a long time.

My company also uses a firewall.

[Tunnelblick developer]

From an earlier reply in a different thread (I searched this discussion group for "broken pipe"):

Usually, a "broken pipe" means that the OpenVPN server, or a router or other network intermediary, has "reset" the connection.If a corporate firewall or other device between your computer and the OpenVPN server is not allowing UDP traffic, that could be the cause.

I'm assuming this is a personal VPN connection (to your home, perhaps), and not a corporate VPN connection or through a commercial VPN service. The fact that it happens every ten minutes could indicate that the VPN connection is being terminated because of inactivity, in which case you might consider adding "ping" options to your OpenVPN setup.

If it is a corporate VPN connection, talk to your IT department. If it is through a commercial VPN service, talk to them.

[NICOLAS RAMZ]

Not sure if that helps, but the log also shows this when reconnecting apparently:

> ...
> 2022-06-20 10:01:23.925071 write UDP: Broken pipe (code=32)
> 2022-06-20 10:01:24.929106 write UDP: Broken pipe (code=32)
> 2022-06-20 10:01:25.377132 write UDP: Broken pipe (code=32)
> 2022-06-20 10:01:27.010408 [vpn_server] Inactivity timeout (--ping-restart), restarting
> 2022-06-20 10:01:27.011239 SIGUSR1[soft,ping-restart] received, process restarting
> 2022-06-20 10:01:27.011289 MANAGEMENT: >STATE:1655712087,RECONNECTING,ping-restart,,
> ...