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

    xo-cli can not register

    Scheduled Pinned Locked Moved Xen Orchestra
    10 Posts 2 Posters 1.3k Views 1 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.
    • T Offline
      tadela
      last edited by olivierlambert

      Hey, folks i have some problem with xo-cli register:

      xo-cli --register https://xo.local admin                                                                             
      Password: *************************
      āœ– {
        "target": {
          "_events": {},
          "_eventsCount": 0,
          "readyState": 3,
          "protocol": "",
          "_binaryType": "nodebuffer",
          "_closeFrameReceived": false,
          "_closeFrameSent": false,
          "_closeMessage": "",
          "_closeTimer": null,
          "_closeCode": 1006,
          "_extensions": {},
          "_receiver": null,
          "_sender": null,
          "_socket": null,
          "_isServer": false,
          "_redirects": 0,
          "url": "wss://xo.local/api/",
          "_req": null
        },
        "type": "error",
        "message": "unable to verify the first certificate",
        "error": {
          "code": "UNABLE_TO_VERIFY_LEAF_SIGNATURE"
        }
      }
      

      Maybe someone knows how to fix it?
      P.s. i added xo.local server crt certificate, but it did not help...
      P.p.s. xo-cli v0.11.1

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

        Try in HTTP first.

        T 1 Reply Last reply Reply Quote 0
        • T Offline
          tadela @olivierlambert
          last edited by

          @olivierlambert same problem.

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

            Using the IP address and not the domain name? "It's always a DNS issue".

            T 1 Reply Last reply Reply Quote 0
            • T Offline
              tadela @olivierlambert
              last edited by tadela

              @olivierlambert !

              xo-cli --register http://x.x.x.x admin                                                                                                  
              Password: *************************
              āœ– {
                "target": {
                  "_events": {},
                  "_eventsCount": 0,
                  "readyState": 3,
                  "protocol": "",
                  "_binaryType": "nodebuffer",
                  "_closeFrameReceived": false,
                  "_closeFrameSent": false,
                  "_closeMessage": "",
                  "_closeTimer": null,
                  "_closeCode": 1006,
                  "_extensions": {},
                  "_receiver": null,
                  "_sender": null,
                  "_socket": null,
                  "_isServer": false,
                  "_redirects": 0,
                  "url": "ws://x.x.x.x/api/",
                  "_req": null
                },
                "type": "error",
                "message": "connect ECONNREFUSED x.x.x.x:80",
                "error": {
                  "errno": "ECONNREFUSED",
                  "code": "ECONNREFUSED",
                  "syscall": "connect",
                  "address": "x.x.x.x",
                  "port": 80
                }
              }
              

              Sorry, but not working...

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

                Are your xo-server is listening on port 80 or not?

                T 1 Reply Last reply Reply Quote 0
                • T Offline
                  tadela @olivierlambert
                  last edited by tadela

                  @olivierlambert
                  hey, is listening only on 443port.
                  i think problem is with certificates....

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

                    Please configure XO to also listen in plain HTTP to see if that work.

                    T 1 Reply Last reply Reply Quote 0
                    • T Offline
                      tadela @olivierlambert
                      last edited by

                      @olivierlambert
                      yes, http is working for me...

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

                        Okay so it's indeed a certificate issue on your side. Double check your certs. Sometimes, you need to have a cert file with the intermediate authority.

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