# Client/server version hash mismatch
**URL:** https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414
**Category:** ParaView Support
**Created:** [June 29, 2023, 8:13pm UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414 "2023-06-29T20:13:17Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@fra](https://discourse.paraview.org/u/fra)
#### Post date: [June 29, 2023, 8:13pm UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414/1 "2023-06-29T20:13:17Z")
Hi,
I use a workstation in my job that was recently upgraded to Debian 12 (bookworm). Paraview got upgraded to version 5.11.0. After the upgrade, I downloaded the Windows binaries on my own machine (same version), but upon connecting I obtain the client/server version hash mismatch. Any ideas what the problem might be?
Edit: Even downloading Linux binaries in WSL2 and running it from there gives the same issue.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 30, 2023, 9:38am UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414/2 "2023-06-30T09:38:13Z")
please share the exact error you are having.
> Paraview got upgraded to version 5.11.0
How was this version of ParaView installed ? Using debian package manager ?
---
### Author:  [@fra](https://discourse.paraview.org/u/fra)
#### Post date: [June 30, 2023, 10:11am UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414/3 "2023-06-30T10:11:01Z")
This is the message I get:
```auto
( 26.410s) [pvserver]vtkSocketCommunicator.c:486 ERR| vtkSocketCommunicator (0x56394cafc180): Client/server version hash mismatch.
( 26.410s) [pvserver]vtkTCPNetworkAccessMana:324 ERR| vtkTCPNetworkAccessManager (0x56394c5c7c20):
**********************************************************************
Connection failed during handshake. vtkSocketCommunicator::GetVersion()
returns different values on the two connecting processes
(Current value: 100).
*********************************************************************
```
> How was this version of ParaView installed ? Using debian package manager ?
Yes.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 30, 2023, 10:15am UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414/4 "2023-06-30T10:15:24Z")
What is the output of `pvserver --version` on debian and `paraview --version` on your windows ?
---
### Author:  [@fra](https://discourse.paraview.org/u/fra)
#### Post date: [June 30, 2023, 10:25am UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414/5 "2023-06-30T10:25:08Z")
```auto
pvserver --version
paraview version 5.11.0
```
ParaView version on Windows is 5.11.0 as well. Could be a packaging problem?
Edit: If I use the binaries from [paraview.org](http://paraview.org) on the workstation the connection opens successfully.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [July 4, 2023, 12:55pm UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414/6 "2023-07-04T12:55:58Z")
It could be that the Debian packages (which I assume you’re using) are using some other VTK. There’s really not an easy way to tell though.
---
### Author:  [@fra](https://discourse.paraview.org/u/fra)
#### Post date: [July 4, 2023, 3:48pm UTC](https://discourse.paraview.org/t/client-server-version-hash-mismatch/12414/7 "2023-07-04T15:48:51Z")
Yes, interestingly even the python-vtk repo package does not actually work, giving issues upon import. I will try to bring it up with their maintainer. Thank you!