NoVNC - Failed to connect to server

Get Help
1

Hi ,

We are getting issue with batch apps namely ANSYS workbench , it works fine on RHEL7 but as we run this application on RHEL8 , with same setup , scripts and turbovnc , websockify , we are facing this issue , looks like he noVNC gets connected for ANSYS GUI on ThinLinc because it proxies it localhost "

proxying from :48924 to localhost:5901

" .. Can you tell me how can that be prevented and the app opens in same browser without going into Thinlinc .

Also , below is the error we get in developers tool

image
image792×556 36.3 KB

Thank you for your assistance ..

2

Hi, not sure I know what ThinLinc is, we don’t use it in our stack.

That said - is there anything in output.log, vnc.log or websockify.log that could tell us what the issue is?

3

Thank you for swift response .

Well , ThinLinc allows users to access a graphical desktop environment on HPC visualization nodes.

I have attached the output.log, vnc.log or websockify.log to look further . Please let me know if you find anything . I also made sure the reverse proxy is setup correctly .

websockify_log.txt (359 Bytes)

vnc_log.txt (1.3 KB)

output_log.txt (5.2 KB)

4 
xfwm4: Unknown option --daemon.

I’d say this is your error - you never got XFCE’s window manager to boot. What version of OnDemand are you running?

5

FYI, we have recently been in discussion with the team at Cendio about providing more formal support for interfacing Open OnDemand and ThinLinc. There are some home-grown approaches people have done in the past, but at some point in the future we anticipate an official integration.

1 Like
6

We are using 3.1 version

7

We are using 3.1 OOD and I have also attached the script.sh.erb .Thank you !

script.txt (2.7 KB)

8

Oh OK, the version actually doesn’t matter here because I’m now remembering this is about Ansys not bc_desktop.

You need to do something like we do where we boot XFCE differently given the different OS.

9

Thank you , I tried that and it didnt help however , when I changed the websocket to 443 instead of 6443 ..It worked .. But , we are using port:6443 for Open ondemand which is also configured in ood_portal.yml

image
image1543×885 155 KB

10

Hello Jeff ,

Is there any way I can configure 6443 for websocket for such GUI apps because we are using 443 for other purposes . As I mentioned it works if I can change to 443..

Thank you for your assistance !

11

I don’t think so, or at least I’d have to dig in to see. But as an off the top guess, I doubt it.

12

Okay , Thank you . Ill let you know if I find it .

13

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.