XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XO5 breaks after defaulting to XO6 (from source)

    Scheduled Pinned Locked Moved Xen Orchestra
    36 Posts 6 Posters 344 Views 5 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MathieuRAM Offline
      MathieuRA Vates 🪐 XO Team @probain
      last edited by MathieuRA

      @probain That's what I was looking for.

      It's strange you are saying you receive an error: ("Cannot get /") because logs show / is mounted and exposes XO6.

      Dec 16 16:54:04 xo xo-server[50694]: 2025-12-16T15:54:04.452Z xo:main INFO Setting up / → /opt/xen-orchestra/@xen-orchestra/web/dist

      Even when I did the same "fixes" that helped my second lab.

      The only difference with your second lab is that you use HAProxy?
      Both are listening on IPv6?

      P 1 Reply Last reply Reply Quote 0
      • P Offline
        probain @MathieuRA
        last edited by

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

        @probain That's what I was looking for.

        It's strange you are saying you receive an error: ("Cannot get /") because logs show / is mounted and exposes XO6.

        Dec 16 16:54:04 xo xo-server[50694]: 2025-12-16T15:54:04.452Z xo:main INFO Setting up / → /opt/xen-orchestra/@xen-orchestra/web/dist

        Even when I did the same "fixes" that helped my second lab.

        The only difference with your second lab is that you use HAProxy?
        Both are listening on IPv6?

        I reverted those changes from above with the [http.mounts] and [http.proxies] parts. Since that broke things even more. Sorry, I should've clarified that. I've pretty much reverted all of my troubleshooting experiments. In hopes to make it more clear if certain troubleshooting steps are needed.

        My primary lab uses Haproxy. The second one doesn't (second lab doesn't run unprivilged either).

        The logs I shared, were from the latest commit 32b3c0b5fcba17585566f0981ef62bef74c56451 (I believe).

        MathieuRAM 1 Reply Last reply Reply Quote 0
        • MathieuRAM Offline
          MathieuRA Vates 🪐 XO Team @probain
          last edited by

          @probain

          Web server listening on https://[::]:8443

          Well, I may have an idea about your issue.
          The code is looking for the port 443 to know if he should use secure protocol ('wss:' / 'https:')
          Is your second lab also in https on the 8443 port?

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            probain @MathieuRA
            last edited by

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

            @probain

            Web server listening on https://[::]:8443

            Well, I may have an idea about your issue.
            The code is looking for the port 443 to know if he should use secure protocol ('wss:' / 'https:')
            Is your second lab also in https on the 8443 port?

            Hmm, no the second lab is more "standard" and uses 443.
            I can try and set 443 on the primary lab as well to test.

            MathieuRAM 1 Reply Last reply Reply Quote 0
            • MathieuRAM Offline
              MathieuRA Vates 🪐 XO Team @probain
              last edited by

              @probain If you can, it will help a lot. Thanks

              P 1 Reply Last reply Reply Quote 0
              • P Offline
                probain @MathieuRA
                last edited by

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

                @probain If you can, it will help a lot. Thanks

                I remember why I chose to use 8443. It is because the xo-user running the service isn't running with root privileges. So doing it with an ordinary user was way more difficult to setup than just use 8443.

                But...
                Switching over so that service-user runs as root. 443 becomes possible. And things work again as expected. However, I really did like not running xo-server as root.

                MathieuRAM 1 Reply Last reply Reply Quote 0
                • MathieuRAM Offline
                  MathieuRA Vates 🪐 XO Team @probain
                  last edited by

                  @probain I will prepare a branch for a potential fix, so you can still use the 8443 port

                  P 1 Reply Last reply Reply Quote 0
                  • P Offline
                    probain @MathieuRA
                    last edited by

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

                    @probain I will prepare a branch for a potential fix, so you can still use the 8443 port

                    Absolutely fantastic. I will test it as soon as possible to help out however I can.

                    Cheers!

                    MathieuRAM 1 Reply Last reply Reply Quote 0
                    • MathieuRAM Offline
                      MathieuRA Vates 🪐 XO Team @probain
                      last edited by

                      @probain branch mra-fix-secure-port 🤞

                      P 1 Reply Last reply Reply Quote 0
                      • P Offline
                        probain @MathieuRA
                        last edited by

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

                        @probain branch mra-fix-secure-port 🤞

                        Success!! Amazing. Thank you so much

                        1 Reply Last reply Reply Quote 1
                        • A Offline
                          acebmxer
                          last edited by acebmxer

                          @mathieura

                          Maybe this has something to do with the script i used to install xo but i can not get v6 to be the default. The links going from v6 to v5 work but just defaults to v5 and accessing. i use port 443 for xo and i do use a proxy.

                          from the config.toml file

                          [http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/' = '../xo-web/dist/'
169 '/v6' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'

                          Screenshot 2025-12-16 183125.png

                          this config breaks everything. Nothing works.

                          [http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/v6' = '../xo-web/dist/'
169 '/' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'

                          Original config

                          [http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/v5' = '../xo-web/dist/'
169 '/v6' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'
                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post