XO5 breaks after defaulting to XO6 (from source)

[Gheppy]

Same problem for me to.
The configuration file is like below, now. If I click on v6 from v5 it works but not the other way around.
And the links always go to /v5, but if v5 is the default what's the point?
I think that's the problem, instead of taking into account the config for the base they are explicitly passed in the links.

The config

[http]

[http.cookies]

[[http.listen]]
port = 443
cert = '/opt/ssl-local/fullchain.pem'
key = '/opt/ssl-local/privkey.pem'

[http.mounts]
'/v6' = '../../@xen-orchestra/web/dist/'
'/' = '../xo-web/dist/'

# List of proxied URLs (HTTP & WebSockets).
[http.proxies]
'/v5/api' = 'ws://localhost:9000/api'
'/v5/api/updater' = 'ws://localhost:9001'
'/v5/rest' = 'http://localhost:9000/rest'

[redis]

[remoteOptions]

[plugins]

The problem with /v5

[ph7]

I fired up my 2nd XO wich is a ronivay script version.
Ran the update to latest commit 9f387
When I logged in, It start in the XO5 page
In my 1st XO "from docs", It start in the XO6

Maybe ronivay is not up to date with the new #release" of XO6
If You are running this type script, maybe that is the culprit

[Gheppy]

@ph7

I don't run any scripts, I install according to the documentation.

nodejs 22

npm install -g npm
git clone -b master https://github.com/vatesfr/xen-orchestra
cp xo-server.toml  /opt/xen-orchestra/packages/xo-server/.xo-server.toml
cd /opt/xen-orchestra
yarn
yarn build
# XO6
yarn run turbo run build --filter @xen-orchestra/web
yarn cache clean
systemctl restart xo-server

The last compilation (b667bc8) works perfectly, this version is fine too, except for the links from v6 to v5 which are many.
In my opinion, v6 is not yet ready to be the default, too many links to v5..

[ph7]

@Gheppy
My links from 6 to 5 works fine
Haven’t tested all of them of course, but quit a few and none of them have faild

[ph7]

I'm not running https and still on node v22

[Gheppy]

@ph7
On http it works, but without the lines below (those with /v5) in the config. On https it is the problem and it shouldn't be.

...
# List of files/directories which will be served.
[http.mounts]
'/v6' = '../../@xen-orchestra/web/dist/'
'/' = '../xo-web/dist/'

# List of proxied URLs (HTTP & WebSockets).
[http.proxies]
#'/v5/api' = 'ws://localhost:9000/api'
#'/v5/api/updater' = 'ws://localhost:9001'
#'/v5/rest' = 'http://localhost:9000/rest'
...

[Gheppy]

I managed to get it working, although the solution is not exactly to my liking.
I enabled both 80 and 443

[http]

[[http.listen]]
port = 80

[[http.listen]]
port = 443
cert = '/opt/ssl-local/fullchain.pem'
key = '/opt/ssl-local/privkey.pem'

# CRITICAL WEBSOCKET CONFIGURATION
[http.upgrade]
'/v5/api' = true
'/v5/api/updater' = true

# Make sure these routes are allowed for WebSocket upgrade
[http.routes]
'/v5/api' = { upgrade = true }
'/v5/api/updater' = { upgrade = true }

# List of files/directories which will be served.
[http.mounts]
'/v6' = '../../@xen-orchestra/web/dist/'
'/' = '../xo-web/dist/'

[redis]

[remoteOptions]

[plugins]

[MathieuRA]

@Gheppy If I understand correctly, when you click the XO5 link from XO6, you are redirected to <url>/v5?

If so, this appears to be a bug, because according to your configuration file, your XO5 instance is located at the root (/).

can you fetch this endpoint please? /rest/v0/gui-routes

[MathieuRA]

I've identified various issues with proxied URLs. I'm on it

[MathieuRA]

@probain @Gheppy Can you please try this branch mra-fix-proxies?

[dpanegassi]

@MathieuRA I was with the same problem, the branch mra-fix-proxies fixed it for me, now i can acess the V5 correctly

[Gheppy]

@MathieuRA
I also confirm that it works. Thank you

[acebmxer]

@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):

mra-fix-proxies

Confirm test branch works... This is with Ronivay's script. Include_V6 option is set to false in config file. Maybe that is why it still defaults to v5. At least all links work now...