@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):
@MajorP93 various fixes have been performed on master.
Your config file should look like this
[http.mounts]
# Uncomment to setup a default version.
# Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
# '/' = '../xo-web/dist/'
'/v5' = '../xo-web/dist/'
'/v6' = '../../@xen-orchestra/web/dist/'
[http.proxies]
# [port] is used to reuse the same port declared in [http.listen.0]
'/v5/api' = '[protocol]//localhost:[port]/api'
'/v5/api/updater' = 'ws://localhost:9001'
'/v5/rest' = 'http://localhost:[port]/rest'
If you are using a different configuration file that overrides the default configuration, please verify that the paths to xo-5 and xo-6 are correct. You can use absolute paths if necessary.
Thanks!
I tried your approach but it did not fix the issue.
The maintainer of the Docker container (ronivay) was able to narrow the issue down to users that let XO handle http to https redirection and SSL encryption.
For now I made Xen Orchestra listen on port 80 only and disabled http to https redirection.
I use Traefik as reverse proxy now and let it handle those parts.
With that setup it works without any issues.
Maybe at some point somebody could further investigate wether or not http to https redirection in combination with SSL encryption is broken after XO 6 became the default.
Would be interesting to see if this issue occurs for non-docker users aswell.