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

    Unable to connect remote host

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    8 Posts 4 Posters 4.1k 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.
    • F Offline
      fred974
      last edited by fred974

      Hi,
      I installed XOA in location A and I am trying to add a host from location B to XOA. For some reason, I get this message:

      server.enable
      {
        "id": "59ade247-aa1f-4049-9b4c-76b1ab260088"
      }
      {
        "errno": -113,
        "code": "EHOSTUNREACH",
        "syscall": "connect",
        "address": "195.22.xxx.xx",
        "port": 443,
        "url": "https://195.22.xxx.xx/jsonrpc",
        "call": {
          "method": "session.login_with_password",
          "params": "* obfuscated *"
        },
        "message": "connect EHOSTUNREACH 195.22.xxx.xx:443",
        "name": "Error",
        "stack": "Error: connect EHOSTUNREACH 195.22.xxx.xx:443
          at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16)
          at TCPConnectWrap.callbackTrampoline (internal/async_hooks.js:131:17)"
      }
      

      I can access 195.22.xxx.xx:443 from my browser meaning it is not firewall issue

      406d130d-ed36-4b45-858d-c07194fffbac-image.png

      Wen I use XCP-ng Center from that same location A as XOA I have no issue connecting to the host.

      0fa8b417-b788-4b0e-a36e-d5cf5670b445-image.png

      Could help me in resolving this issue?

      Thank you

      TheNorthernLightT 1 Reply Last reply Reply Quote 0
      • F Offline
        fred974 @olivierlambert
        last edited by

        olivierlambert Thank you everyone for all your help. This issue is 100% user error. Sorry to have wasted your time. The IP address I was copying in XOA appeared was incorrect 😧 😲

        1 Reply Last reply Reply Quote 0
        • DanpD Offline
          Danp Pro Support Team
          last edited by

          Maybe a routing issue, such that the XOA VM can't "see" the remote xcp-ng server?

          1 Reply Last reply Reply Quote 0
          • TheNorthernLightT Offline
            TheNorthernLight @fred974
            last edited by TheNorthernLight

            fred974 Can you ping the B server from XOA CLI?

            The workstation your working on may have firewall rules to allow access to both Site. That doesnt translate necessarily from Site A > Site B FROM the XOA server itself.

            F 1 Reply Last reply Reply Quote 0
            • F Offline
              fred974 @TheNorthernLight
              last edited by

              TheNorthernLight said in Unable to connect remote host:

              Can you ping the B server from XOA CLI?

              Nope I cannot even ping google.com. I'll deploy a new XOA.

              F 1 Reply Last reply Reply Quote 0
              • F Offline
                fred974 @fred974
                last edited by

                I just deployed an new XOA and I can now resolved external ip such as google.com and kernel.com
                a17a87b7-ca2d-4486-8b1b-a483b63eb62e-image.png
                When I tried to add the host from location B I did get this:

                server.enable
                {
                  "id": "c5f48f52-722d-42f8-9306-6b8b88e798e7"
                }
                {
                  "code": "ECONNRESET",
                  "url": "https://195.22.xxx.xx/jsonrpc",
                  "call": {
                    "method": "session.login_with_password",
                    "params": "* obfuscated *"
                  },
                  "message": "socket hang up",
                  "name": "Error",
                  "stack": "Error: socket hang up
                    at connResetException (internal/errors.js:607:14)
                    at TLSSocket.socketOnEnd (_http_client.js:499:23)
                    at TLSSocket.emit (events.js:388:22)
                    at TLSSocket.emit (domain.js:470:12)
                    at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:93:17)
                    at endReadableNT (internal/streams/readable.js:1336:12)
                    at processTicksAndRejections (internal/process/task_queues.js:82:21)"
                }
                

                This is not the same error message as the one i posted originally. Why can I add the host in XCP-ng Center but not XOA

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

                  Just check you can reach it correctly. From XOA, you can do a curl -k https://195.22.xxx.xx and print the result here?

                  F 1 Reply Last reply Reply Quote 0
                  • F Offline
                    fred974 @olivierlambert
                    last edited by

                    olivierlambert Thank you everyone for all your help. This issue is 100% user error. Sorry to have wasted your time. The IP address I was copying in XOA appeared was incorrect 😧 😲

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

                      It happens 🤷 No worries 🙂

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO olivierlambert marked this topic as a question on
                      • olivierlambertO olivierlambert has marked this topic as solved on
                      • First post
                        Last post