# Socket error in call to connect. Connection timed out.

**URL:** https://discourse.paraview.org/t/socket-error-in-call-to-connect-connection-timed-out/4043
**Category:** ParaView Support
**Created:** [April 13, 2020, 8:41am UTC](https://discourse.paraview.org/t/socket-error-in-call-to-connect-connection-timed-out/4043 "2020-04-13T08:41:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Evgenii\_Sharaborin](https://discourse.paraview.org/user_avatar/discourse.paraview.org/evgenii_sharaborin/32/3386_2.png) [@Evgenii\_Sharaborin](https://discourse.paraview.org/u/Evgenii_Sharaborin)
#### Post date: [April 13, 2020, 8:41am UTC](https://discourse.paraview.org/t/socket-error-in-call-to-connect-connection-timed-out/4043/1 "2020-04-13T08:41:40Z")

</div>

Dear All,  
I am trying to connect to my cluster. Until yesterday it worked but today - no!  
it showed me an error:  
Connecting to client (reverse connection requested)…

```
Connection URL: csrc://10.16.13.219:20010

Exiting...

ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_python2_superbuild/build/superbuild/paraview/src/VTK/Common/System/vtkSocket.cxx, line 476
vtkClientSocket (0x2dde380): Socket error in call to connect. Connection timed out.

ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_python2_superbuild/build/superbuild/paraview/src/VTK/Common/System/vtkClientSocket.cxx, line 51
vtkClientSocket (0x2dde380): Failed to connect to server 10.16.13.219:20010

ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_python2_superbuild/build/superbuild/paraview/src/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 392
vtkTCPNetworkAccessManager (0x1f36240): Connect timeout.

```

I checked netstat **before running** paaraview and pvserver, it does not show open sockets by them/ everything looks good, but it doesn’t want to connect.

P.S. I use 10.13.3 High Sierra Mac OS.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [April 13, 2020, 4:03pm UTC](https://discourse.paraview.org/t/socket-error-in-call-to-connect-connection-timed-out/4043/2 "2020-04-13T16:03:57Z")

</div>

Looks to me like a blocked port, or that the cluster can’t ssh back into your Mac. From the cluster, try ssh yourMacName.

---

<div class="post-metadata">

### Author: ![Evgenii\_Sharaborin](https://discourse.paraview.org/user_avatar/discourse.paraview.org/evgenii_sharaborin/32/3386_2.png) [@Evgenii\_Sharaborin](https://discourse.paraview.org/u/Evgenii_Sharaborin)
#### Post date: [April 13, 2020, 4:19pm UTC](https://discourse.paraview.org/t/socket-error-in-call-to-connect-connection-timed-out/4043/3 "2020-04-13T16:19:40Z")

</div>

Dear Walter,  
it works in both sides.  
Mac2Cluster and Cluser2Mac

Best Regards,  
Evgenii

---

<div class="post-metadata">

### Author: ![Evgenii\_Sharaborin](https://discourse.paraview.org/user_avatar/discourse.paraview.org/evgenii_sharaborin/32/3386_2.png) [@Evgenii\_Sharaborin](https://discourse.paraview.org/u/Evgenii_Sharaborin)
#### Post date: [April 14, 2020, 6:38am UTC](https://discourse.paraview.org/t/socket-error-in-call-to-connect-connection-timed-out/4043/4 "2020-04-14T06:38:31Z")

</div>

Indeed, it is because of incorrect host-ip

Thank you, Walter!

Best regards,  
Evgenii