Transport-XMPP failing to start

pdonias

@olivierlambert I'm guessing you're talking about the similar error that we're getting on the usage report plugin? But usage report and the backup reports are 2 different plugins and I don't think the errors are related. So we'll have to investigate that separately.

olivierlambert

Thanks, understood

techiem2

Just to be clear it's the Transport-XMPP plugin itself giving the error when I try to turn it back on.

Backup-Reports is still on and thinks it's working.

Danp

Seems like the problem was introduced here. Don't you need so call this._client.start in order to initiate the connection?

julien-f

@Danp Thanks for the pointer, investigating

julien-f

I don't have an easy way to test it, please check out this PR and let me know: https://github.com/vatesfr/xen-orchestra/pull/7082

julien-f opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server-transport-xmpp): fix loading #7082

Danp

@julien-f said in Transport-XMPP failing to start:

I don't have an easy way to test it,

Me either, but this update appears to at least resolve the issue of Cannot read properties of undefined (reading 'socket') when starting xo-server.

julien-f

@techiem2 Do you have the ability to test?

techiem2

@julien-f If you can give me instructions on how to update the plugin with the updated version, i'll give it a shot!

julien-f

@techiem2 Sorry, I missed your message.

Are you using an official XOA or XO built from the sources?

techiem2

@julien-f
From Source using ronivay's script:
https://github.com/ronivay/XenOrchestraInstallerUpdater

julien-f

@techiem2 In this case, I cannot tell you how to update a specific plugin or use a specific branch, you can ask for the script maintainer's help or I'll merge the PR without further tests

julien-f

The fix has been merged in master, let me know if there are more issues.

techiem2

@julien-f
Sorry, been a bit busy.
I'll update this weekend and see if the new version pulls in.
Thanks!

techiem2

@julien-f
Ok, so it doesn't fail with the socket error, but now it's saying unable to verify the first certificate:
Not sure if this is a plugin issue or something on my end, but normal clients connect fine.
I'm using Prosody with a Letsencrypt cert.

plugin.load
{
  "id": "transport-xmpp"
}
{
  "code": "UNABLE_TO_VERIFY_LEAF_SIGNATURE",
  "message": "unable to verify the first certificate",
  "name": "Error",
  "stack": "Error: unable to verify the first certificate
    at TLSSocket.onConnectSecure (node:_tls_wrap:1550:34)
    at TLSSocket.emit (node:events:514:28)
    at TLSSocket.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202310280240/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket._finishInit (node:_tls_wrap:967:8)
    at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:743:12)
    at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17)"
}

julien-f

@techiem2 Are you sure your server's certificate is correctly configured?

Is it self-signed?

techiem2

@julien-f As far as I can tell. It's a standard Let's Encrypt cert and it works with normal clients.

julien-f

@techiem2 If you can provide me access to your server and your configuration, I might be able to investigate and maybe come up with a fix.

techiem2

@julien-f Thanks!
Just got you setup and DM'd.
Let me know if you need anything else to poke around on.

julien-f

If other people get the UNABLE_TO_VERIFY_LEAF_SIGNATURE error, check that your XMPP server provides the correct certificate chain.

You can use OpenSSL for this:

$ openssl s_client -connect $domain:$port -starttls xmpp -showcerts </dev/null
CONNECTED(00000003)
depth=0 CN = $domain
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN = $domain
verify error:num=21:unable to verify the first certificate
verify return:1
depth=0 CN = $domain
verify return:1