# reverse connection with port forwarding using the master branch

**URL:** https://discourse.paraview.org/t/reverse-connection-with-port-forwarding-using-the-master-branch/736
**Category:** ParaView Support
**Created:** [October 16, 2018, 7:18am UTC](https://discourse.paraview.org/t/reverse-connection-with-port-forwarding-using-the-master-branch/736 "2018-10-16T07:18:13Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 16, 2018, 2:38pm UTC](https://discourse.paraview.org/t/reverse-connection-with-port-forwarding-using-the-master-branch/736/3 "2018-10-16T14:38:55Z")

</div>

Hi Jean,

I was the one working on the breaking commit.

> Using the exact same procedure, I can no longer connect with the master branch, compiled both on my client and server sides. I suspect the commit ec68385af is what is causing me problems. I have reverted to a commit just prior to that (specifically git checkout ad657b8ef) and my connection works fine.

This change is supposed to be fully retro compatible, please share a non working server configuration so I can investigate.

> I see a note about the variable PV\_SSH\_PF\_SERVER\_PORT should be set. But I don’t understand if it should be set to any value, or to the value of the port itself. Should it be set client-side, or server-side?

`PV_SSH_PF_SERVER_PORT` is a variable you can use in your server script, you do not need to set it, just recover it in your server script. This is the port on which the server will try to connect to the client through the ssh tunnel.

> Connection failed during handshake. vtkSocketCommunicator::GetVersion()  
> returns different values on the two connecting processes  
> (Current value: 100).

Do you see this error ?

> vtkSocketCommunicator (0x5555557e5280): Client/server version hash mismatch.

In any case, you will find lots of info there:  
[https://gitlab.kitware.com/paraview/paraview/merge\_requests/2652](https://gitlab.kitware.com/paraview/paraview/merge_requests/2652)

> [@Using SSH Support to secure your client/server communication with ParaView](https://discourse.paraview.org/t/using-ssh-support-to-secure-your-client-server-communication-with-paraview/682):
>
> Since [mr](https://gitlab.kitware.com/paraview/paraview/merge_requests/2652) and [mr](https://gitlab.kitware.com/paraview/paraview/merge_requests/2821), ParaView master now has a support for ssh, which includes port forwarding. In order to use it, you will need first to install a terminal and an ssh tool. Terminals are available by default on Windows, Mac and virtually on all linux distribution. Ssh is available by default on mac, on all package manager on all linux distribution. On windows ssh is now available by default with the Windows 10 Spring update but we recommend installing [Putty](https://www.chiark.greenend.org.uk/~sgtatham/putty/) as support for rc connection is bett…

---

_[View the full topic](https://discourse.paraview.org/t/reverse-connection-with-port-forwarding-using-the-master-branch/736)._