# ParaView version

**URL:** https://discourse.paraview.org/t/paraview-version/2214
**Category:** ParaView Support
**Created:** [July 14, 2019, 2:07pm UTC](https://discourse.paraview.org/t/paraview-version/2214 "2019-07-14T14:07:18Z")
**Posts on this page:** 19
**Page:** 1

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 14, 2019, 2:07pm UTC](https://discourse.paraview.org/t/paraview-version/2214/1 "2019-07-14T14:07:18Z")

</div>

Hi,

I installed ParaView on Amazon EC2 using “sudo apt install paraview”.  
How do I find the ParaView version?  
I tried : “paraview --version” and “paraview --V” but I got the message:  
“paraview: cannot connect to X server”

---

<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: [July 15, 2019, 8:42am UTC](https://discourse.paraview.org/t/paraview-version/2214/2 "2019-07-15T08:42:38Z")

</div>

paraview is an X application and requires a Xorg server to be able to run.

Do you mean to use pvserver or pvbatch ? They do not require Xorg.

`./bin/pvserver --version`

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 10:34am UTC](https://discourse.paraview.org/t/paraview-version/2214/3 "2019-07-15T10:34:22Z")

</div>

Thank you Mathieu.

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 10:57am UTC](https://discourse.paraview.org/t/paraview-version/2214/4 "2019-07-15T10:57:42Z")

</div>

Regarding this issue, I installed ParaView on an Amazon EC2 instance, using “sudo apt install paraview”.  
The version is apparently 5.4.1. I started “pvserver” there. The messages show that it’s running.

I downloaded the ParaView desktop app version 5.4.1 to my computer (I was using 5.6)  
I tried to connect as a client using the 5.4.1 version, but this was not successful.

On my EC2 instance, port 11111 is open to receive communication.

What am I missing? Do I need to use special configurations? Am I only able to use the ParaView web (Visualizer) as a client when I am connecting to an EC2 instance?

---

<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: [July 15, 2019, 11:10am UTC](https://discourse.paraview.org/t/paraview-version/2214/5 "2019-07-15T11:10:19Z")

</div>

are you able to ping your instance or do you use multiple ssh connection ?

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 11:26am UTC](https://discourse.paraview.org/t/paraview-version/2214/6 "2019-07-15T11:26:01Z")

</div>

I only use one ssh connection.

---

<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: [July 15, 2019, 11:26am UTC](https://discourse.paraview.org/t/paraview-version/2214/7 "2019-07-15T11:26:30Z")

</div>

is the port 11111 open ?

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 11:28am UTC](https://discourse.paraview.org/t/paraview-version/2214/8 "2019-07-15T11:28:36Z")

</div>

It supposed to be open, I added it on the security group.

---

<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: [July 15, 2019, 11:29am UTC](https://discourse.paraview.org/t/paraview-version/2214/9 "2019-07-15T11:29:35Z")

</div>

when you run pvserver and tries to connect to it with your ParaView, is anything shown in the pvserver output ?

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 11:31am UTC](https://discourse.paraview.org/t/paraview-version/2214/10 "2019-07-15T11:31:16Z")

</div>

No. No message. On the ParaView desktop app the message is “something is wrong with the socket”…

---

<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: [July 15, 2019, 11:32am UTC](https://discourse.paraview.org/t/paraview-version/2214/11 "2019-07-15T11:32:08Z")

</div>

ParaView can’t communicate with pvserver at all. You will have to check your network.

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 11:33am UTC](https://discourse.paraview.org/t/paraview-version/2214/12 "2019-07-15T11:33:07Z")

</div>

Ok, thank you. I will do that. Just to be clear, this procedure is ok, right? It supposed to work?

---

<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: [July 15, 2019, 11:33am UTC](https://discourse.paraview.org/t/paraview-version/2214/13 "2019-07-15T11:33:18Z")

</div>

Yes it is.

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 11:33am UTC](https://discourse.paraview.org/t/paraview-version/2214/14 "2019-07-15T11:33:50Z")

</div>

Thank you very much. I will check my network.

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 12:37pm UTC](https://discourse.paraview.org/t/paraview-version/2214/15 "2019-07-15T12:37:12Z")

</div>

Ok. So I checked my network and it’s ok.

Apparently you need to connect with another ssh connection to the EC2 instance (besides the one that you are already using to control your instance).

You need to create a port forwarding using plink in windows (run it from inside the PuTTY folder). It’s something similar in Mac (not plink).

the link is the following format:  
plink -i “your\_amazon\_key” your\_amazon\_username@your\_amazon\_host -L 11111:localhost:11111

After connecting with another connection, you can start your ParaView desktop app and connect to the server using regular localhost server configuration (not remote host).

However, after doing so I got the following error message on the pvserver side:

ERROR: In /build/paraview-lH8wFv/paraview-5.4.1+dfsg3/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 413  
vtkTCPNetworkAccessManager (0x55ef54b202f0):

* * *

Connection failed during handshake. This can happen for the following reasons:

1. Connection dropped during the handshake.
2. vtkSocketCommunicator::GetVersion() returns different values on the  
two connecting processes (Current value: 100).
3. ParaView handshake strings are different on the two connecting  
processes (Current value: paraview.5.4.renderingbackend.opengl).

* * *

What seems to be the error?

Thank you for your time,  
Misha

---

<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: [July 15, 2019, 12:50pm UTC](https://discourse.paraview.org/t/paraview-version/2214/16 "2019-07-15T12:50:09Z")

</div>

You can do it like that but it is not needed if your port is open.

The connection is not working probably because they are not using the same backend.  
copy the paraview you downloaded locally to your server and run this pvserver instead.

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 12:53pm UTC](https://discourse.paraview.org/t/paraview-version/2214/17 "2019-07-15T12:53:17Z")

</div>

But who are they? Amazon? But I used “sudo apt install paraview”

---

<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: [July 15, 2019, 12:55pm UTC](https://discourse.paraview.org/t/paraview-version/2214/18 "2019-07-15T12:55:04Z")

</div>

“they” are the people packaging paraview for your linux distribution on your server, probably Ubuntu.

So download and extract our release of ParaView in your server instead of using the one provided by ubuntu.  
[https://www.paraview.org/download/](https://www.paraview.org/download/)

---

<div class="post-metadata">

### Author: ![Misha](https://discourse.paraview.org/user_avatar/discourse.paraview.org/misha/32/1732_2.png) [@Misha](https://discourse.paraview.org/u/Misha)
#### Post date: [July 15, 2019, 1:42pm UTC](https://discourse.paraview.org/t/paraview-version/2214/20 "2019-07-15T13:42:19Z")

</div>

I downloaded version 5.4.1 and it’s working.
