XOA Proxy Error when updating
-
Hi!
I just installed the XOA Proxy following the guide from https://xen-orchestra.com/blog/xo-proxy-a-concrete-guide/ but I get an error when trying to upgrade the proxy
The whole error log is:
proxy.upgradeAppliance { "id": "3e2ad3d7-f4d1-4eb1-bea0-a6129f12325c", "ignoreRunningJobs": true } { "message": "this._app.getCurrentChannel is not a function", "name": "TypeError", "stack": "TypeError: this._app.getCurrentChannel is not a function at Proxy._getChannel (file:///opt/xo/xo-builds/xen-orchestra-202305091555/packages/xo-server/src/xo-mixins/proxies.mjs:92:41) at Proxy.updateProxyAppliance (file:///opt/xo/xo-builds/xen-orchestra-202305091555/packages/xo-server/src/xo-mixins/proxies.mjs:236:79) at Proxy.upgradeProxyAppliance (file:///opt/xo/xo-builds/xen-orchestra-202305091555/packages/xo-server/src/xo-mixins/proxies.mjs:223:18) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202305091555/packages/xo-server/src/xo-mixins/api.mjs:417:20)" }
This is with XOA built from sources, build commit https://github.com/vatesfr/xen-orchestra/commit/90ce1c4d1ed8d97c024098e26d1fb8ecfd78cb25
-
Pinging @julien-f on this
-
@bullerwins XO Proxy Appliance deployment is not supported in XO built from sources.
-
I missed that in the original message, indeed
FYI @bullerwins there's no such thing as XOA built from sources, you have either:
- XOA is Xen Orchestra virtual Appliance, that's the VM we distribute with pro support and QA/stable channel, updater and such
- XO from the sources is from Github, without pro support but community support, no QA no stable version, no udpater and such
-
@julien-f said in XOA Proxy Error when updating:
@bullerwins XO Proxy Appliance deployment is not supported in XO built from sources.
my bad, it used to work a few months back I believe
@olivierlambert said in XOA Proxy Error when updating:
I missed that in the original message, indeed
FYI @bullerwins there's no such thing as XOA built from sources, you have either:
- XOA is Xen Orchestra virtual Appliance, that's the VM we distribute with pro support and QA/stable channel, updater and such
- XO from the sources is from Github, without pro support but community support, no QA no stable version, no udpater and such
Thanks, I got confused with the naming, I'm using the second option.
As a workaround I used a VPN to manage the remote XCP-ng host, thanks!