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

    XOA won't start HTTPS listen on configured port

    Scheduled Pinned Locked Moved Xen Orchestra
    29 Posts 5 Posters 7.8k Views 1 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      Thanks for the feedback @bill-gertz !

      Thanks for the doc update @julien-f 😉

      bill.gertzB 1 Reply Last reply Reply Quote 0
      • bill.gertzB Offline
        bill.gertz @olivierlambert
        last edited by

        @olivierlambert @julien-f @Danp

        Thanks to everyone for the clear, helpful support. Impressed.

        bill.gertzB 1 Reply Last reply Reply Quote 0
        • bill.gertzB Offline
          bill.gertz @bill.gertz
          last edited by

          @julien-f @olivierlambert

          Submitted PR to change attribute documented as 'host' to 'hostname'.
          https://github.com/vatesfr/xen-orchestra/pull/4681

          billgertz opened this pull request in vatesfr/xen-orchestra

          closed fix(docs/configuration): `host` → `hostname` #4681

          1 Reply Last reply Reply Quote 0
          • ronivayR Offline
            ronivay Top contributor
            last edited by ronivay

            Hi,

            @julien-f from sources documentation still instructs to set path relative to packages/xo-server like it used to be:

            [http.mounts]
            '/' = '../xo-web/dist/'

            sample.config.toml says that paths are relative to configuration file so this would end up looking xo-web/dist path from $HOME/.config/ since configuration is at $HOME/.config/xo-server/config.toml

            Noticed this while fixing my "well known installer script"

            1 Reply Last reply Reply Quote 0
            • julien-fJ Offline
              julien-f Vates 🪐 Co-Founder XO Team
              last edited by

              @ronivay Thanks for the report, I'll change this by make it part of the default config, it won't be necessary for the user to configure it themself.

              1 Reply Last reply Reply Quote 0
              • julien-fJ Offline
                julien-f Vates 🪐 Co-Founder XO Team
                last edited by julien-f

                In fact it's already the case, I just need to remove this from the documentation 🙂

                https://github.com/vatesfr/xen-orchestra/blob/14f0cbaec6244d66266fe2ee47b0bfb5716c2f61/packages/xo-server/config.toml#L99-L100

                1 Reply Last reply Reply Quote 0
                • julien-fJ Offline
                  julien-f Vates 🪐 Co-Founder XO Team
                  last edited by

                  Done: https://github.com/vatesfr/xen-orchestra/commit/14f0cbaec6244d66266fe2ee47b0bfb5716c2f61

                  0 julien-f committed to vatesfr/xen-orchestra
                  fix(docs/from sources): no need to configure `/` mount point
                  bill.gertzB 1 Reply Last reply Reply Quote 1
                  • bill.gertzB Offline
                    bill.gertz @julien-f
                    last edited by bill.gertz

                    All,

                    For anyone that happens into this thread and wondered if the well known installer script was confirmed working correctly. It was fixed as noted above and tested on a fresh install, The rule of thumb, a bit tongue in cheek, when it comes to these files is:

                    • Leave the config in /etc[/xo]/xo-server/config.toml alone.
                    • Set the over rides in ~/.config/xo-server/config.toml home .
                    • Use only /etc[/xo]/xo-server/config.toml and you're on your own.

                    On the last point point I mean that you need ensure whatever you use there contains attributes for the original file plus your overrides. Copying the sample config packages/xo-server/sample.config.toml to /etc[/xo]/xo-server/config.toml may not capture all of the attributes that need to be set.

                    @julien-f If missed the spirit of this please, please correct me.

                    1 Reply Last reply Reply Quote 0
                    • julien-fJ Offline
                      julien-f Vates 🪐 Co-Founder XO Team
                      last edited by

                      @bill-gertz It depends of how you install it, but it look ok. In our appliances we install and run xo-server as a global service, and there is only /etc/xo-server/config.toml which is used for user customization (you could remove it and it would still work).

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post