XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XOA Console not coming up

    Scheduled Pinned Locked Moved Xen Orchestra
    5 Posts 3 Posters 50 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      Dkurupp
      last edited by

      Hi,

      Background
      My XCP Ng was working all fine, when I decided to change my broadband provider and the troubles started. The main CIDR range changed from 192.168.1.x to 192.168.0.x
      and as I have my server hosted under an extended router which was still in the old CIDR range (and hence not working). DHCP fixed, and all working.

      Problem
      Not sure if this is related or not, or may be a coincidence, but now, the "Console" tab is empty - except the icons & graphs - i.e. (vnc) console doesnt come up, which means I cannot launch a new VM - as after launching I cannot install the OS and proceed to SSH.

      I have tried from the last 3 days without luck. My errors on browser console on "VM > console" tab keep repeating -

      Failed when connecting: Failed to connect to server ( (code: 1005)) util.js:44:54
      Tried changing state of a disconnected RFB object util.js:44:54
      WebSocket on-close event util.js:42:54
      Failed when connecting: Failed to connect to server ( (code: 1005)) util.js:44:54
      Tried changing state of a disconnected RFB object util.js:44:54
      WebSocket on-close event util.js:42:54
      Failed when connecting: Failed to connect to server ( (code: 1005))
      

      Removing XOA issues from equation
      As for XOA, other than the default install, I have now downloaded / compiled XOA on a different VM hosted on same XCP Ng - and the same problem persists i.e. Console is not shown

      Ask
      So starting from scratch upwards, could the experts pls explain the assumptions that XOA makes on the XCP Ng box to show a VM's console?
      What can I check, what needs to be fixed?

      Thank you !

      P 1 Reply Last reply Reply Quote 0
      • P Offline
        ph7 @Dkurupp
        last edited by

        @Dkurupp
        I have no idea but have You tried
        Restart toolstack or reboot the host

        D 1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by olivierlambert

          Hi,

          You might have a discrepancy between the IP you use to connect and the internal IP reported by XCP-ng, so likely your XO is trying to connect the console via a different IP (the old ones?)

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            Dkurupp @ph7
            last edited by

            @ph7 I try to avoid restarting the XCP ng box, but did it anyways now. No luck, Tx anyways

            1 Reply Last reply Reply Quote 0
            • D Offline
              Dkurupp @olivierlambert
              last edited by Dkurupp

              @olivierlambert

              Tried this -

              XCPNG | ~/_scripts > netstat -tulpn | sed -n '1,2p;/5900\|80/p'
              Active Internet connections (only servers)
              Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
              tcp        0      0 127.0.0.1:5900          0.0.0.0:*               LISTEN      1741/vncterm        
              tcp        0      0 0.0.0.0:10809           0.0.0.0:*               LISTEN      2896/xapi-nbd       
              tcp6       0      0 :::80                   :::*                    LISTEN      2887/xapi           
              udp        0      0 0.0.0.0:780             0.0.0.0:*                           1029/rpcbind        
              udp6       0      0 :::780                  :::*                                1029/rpcbind    
              

              VNC on the XCPNg box is listening to 127.0.01 : 5900, may be - I should change this to listen to 0.0.0.0 ?

              Also, something to do with protocol used - the browser > inspect > network - seems to use ws:// protocol and receives a 101 - upgrade, should it have been vnc ? ( apologies if its a random guess rant here) -- Attached screenshot of browser console logs.

              FYI - 192.168.0.49:3000 - is where my XOA VM is running as a VM on XCP Ng (192.168.0.45)
              and the logs below is when the console for itself (i.e. same IP)

              Selection_157.png

              1 Reply Last reply Reply Quote 0
              • First post
                Last post