console_instructions [Xenmodule Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Console/noVNC instructions ======


** noVNC console is client side **

first thing to know about noVNC console , that noVNC is a javascript and javascript runs on the client browser (Client side not server side), so when noVNC trys to connect your XenServer ,the connection will be from the Client IP address and not from your whmcs server IP .


so if you don't use proxy then your server must allow connection from clients , **that mean it must use Public IP** , because private IPs can't be reached by clients browser neither by noVNC javascript



----


 
==== Using console without proxy ====


- go to Xenica Configurations tab (addons>Xenica>Configurations), and make sure that both 'CONSOLE PROXY' and 'CONSOLE PROXY MAP' fields are empty .

- make sure that your XenServer is reachable for clients (public IP address , and open firewall port 443)

- you may need a valid SSl certification for your XenServer IP to let browsers connect to it without problems




----


 
==== Using console with proxy ====


you can get more information about how to install and configure haproxy from here :

[[haproxy_console|Haproxy Install and Config]]



----



==== Debugging console Connections ====

if you still get error message : 'Server disconnected (code: 1006)' , you can get some helpfull data by using chrome inspect tool:

- from your chrome browser , right click menu, choose Inspect
 
- from the inspecting form choose 'Console' tab , you will find useful data there , like : 
{{ :wiki:2018.03.14_00h35m33s_004_.png?400 |}}

with the connection error message like : 

- ERR_CONNECTION_TIMED_OUT which mean your server is not allowing connection

- ERR_CERT_AUTHORITY_INVALID that mean browser is not allowing to open this URL because you don't have SSl certification installed for your XenServer , you can bypass that for testing purposes by opening once your XenServer IP with https  , 

for example https://100.100.100.100 , you will get a warning from the browser that its unsecure URL , just bypass it and proceed for once . after that the browser will remember to allow this URL without SSl certification . 
try now the console (from the same browser) it must work .


----

<color #ed1c24>we highly advice to install valid SSL certificate for your XenServer , especially when using Public IP.</color>

The instruction to generate or install ssl cert on XenServers are available in critix main site , basically the cert files are in /etc/xensource/