Add server, Connection Failed

Berrick

Hi Everyone,

xo-server 5.53.0
xo-web 5.53.3

Hoping to get an answer as to why I cant add a XCP-ng 7.6 server to XO Free version?

Trying to add a remote server via VPN
I can ssh to it without issue
I have added it to XCP-ng Center 7.6 without issue
I used the following to add the server
IP address of server
root username and password
toggled "Unauthorized Certificates"

However I get the little red triangle stating connection failed.
Log info below. TIA

server.enable
{
  "id": "fd4ff6b9-21f3-431e-9c27-aca34f87e017"
}
{
  "errno": "ETIMEDOUT",
  "code": "ETIMEDOUT",
  "syscall": "connect",
  "address": "192.168.16.242",
  "port": 443,
  "url": "https://192.168.16.242/jsonrpc",
  "call": {
    "method": "session.login_with_password",
    "params": [
      "root",
      "NotTheActualPassword"
    ]
  },
  "message": "connect ETIMEDOUT 192.168.16.242:443",
  "name": "Error",
  "stack": "Error: connect ETIMEDOUT 192.168.16.242:443
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)"
}

olivierlambert

You need to be able to reach port 443 of the host, otherwise it won't work. SSH isn't involved at all.

You can see if your XO VM you can reach https://192.168.16.242

Berrick

Many thanks for the reply.

I should have mentioned in original post that I had checked this.

But for completeness when I https://192.168.16.242 I receive back the "mange your XCP-Ng 7.6.0" page

olivierlambert

So it might be a problem on XAPI on the host: do a XAPI toolstack restart, disconnect the host in the Settings/server view in XO. Wait 5 minutes, and then reconnect the server in XO.

Berrick

Unfortunately that didn't work either

olivierlambert

This is so basic that it must be a configuration issue somewhere.

I would start to see if locally XAPI is answering, by issuing xe vm-list on the host itself and see if there's a valid answer.

Then, to avoid any configuration issue, I would use a XOA Free to deploy and see if it works

Berrick

Hi Oliver,

My apologies I have wasted your time (though I did learn about the XOA so not totally wasted)

The old adage "If you want a job done properly. Do it yourself" is still very true.

Long story short when I looked into the issue myself, my colleague was using the wrong XO installation. This VPN isn't site to site so for now we have vmware running 2 nat'ed VMs, XO and a windows client. The windows client accesses XO and XO goes out over the hosts vpn connection to the remote site.

When using this correctly everything is OK

Case closed

olivierlambert

No worries, it happens