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

    Orchestra logon screen is messed up after update

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    10 Posts 3 Posters 374 Views 3 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.
    • JamfoFLJ Offline
      JamfoFL
      last edited by

      Exceedingly minor error... I'm really only posting just to let you know it is happening as the issue is purely cosmetic.

      Xen Orchestra from sources. I just upgraded to Commit DE934. After applying the Commit, everything is working just fine but, for some reason, the log on screen is now missing its graphics and has a "messed up" appearance:

      84dedb70-e71c-4b97-8d50-40fed99e5d4a-image.png

      Oddly enough, this seems as if it is only happening in Google Chrome. Oddly enough, it seems to look fine on both Edge and Firefox.

      Again, this isn't affecting anything else other than the appearance of the log on screen so the issue is purely cosmetic. I just wanted you all to be aware.

      Thanks!

      P 1 Reply Last reply Reply Quote 0
      • JamfoFLJ Offline
        JamfoFL @olivierlambert
        last edited by

        olivierlambert I would agree... one of those odd glitches that occurred during the build process that corrected itself on a second run.

        Thanks for everyone's help... please go ahead and close this out!

        1 Reply Last reply Reply Quote 1
        • P Online
          probain @JamfoFL
          last edited by

          JamfoFL Cleared cache?

          JamfoFLJ 1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Be sure to rebuild everything. The login page is stored in xo-server, not xo-web

            JamfoFLJ 1 Reply Last reply Reply Quote 0
            • JamfoFLJ Offline
              JamfoFL @probain
              last edited by

              probain Cleared, but did not help. Same result...

              P 1 Reply Last reply Reply Quote 0
              • JamfoFLJ Offline
                JamfoFL @olivierlambert
                last edited by

                olivierlambert I always run the following procedure when applying Commits:

                git checkout .
                git pull --ff-only
                yarn
                yarn build

                Never had any issues in the past. So I figured maybe something didn't complete quite right with the last run, so I re-ran the process again and it seems to have fixed the issue.

                I guess it was just one of those weird things that can happen from time to time.

                Thanks for getting back to me!

                1 Reply Last reply Reply Quote 0
                • P Online
                  probain @JamfoFL
                  last edited by probain

                  JamfoFL I'm still guessing cache.. Could try in incognito mode.
                  OR... you got a broken URL. I can replicate similar stuff if I do bad things with the address.
                  e.g.
                  Browse to https://<xo.example.net>/signin
                  Try https://<xo.example.net>/signin/callback
                  Continue to https://<xo.example.net>/signin again
                  The sign in page is now borked. And the page needs to be closed, and open in a new window/tab instead.

                  But it might not be the same as what you're experiencing.

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    Check what your browser console is reporting

                    JamfoFLJ 1 Reply Last reply Reply Quote 0
                    • JamfoFLJ Offline
                      JamfoFL @olivierlambert
                      last edited by

                      olivierlambert I went through all of the tabs and everything is working as it should be. The only thing that was affected was that log on screen and all looks good now!

                      Is there something in particular you would like me to check for you?

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        If it works now, I would say local build issue 🙂

                        JamfoFLJ 1 Reply Last reply Reply Quote 0
                        • JamfoFLJ Offline
                          JamfoFL @olivierlambert
                          last edited by

                          olivierlambert I would agree... one of those odd glitches that occurred during the build process that corrected itself on a second run.

                          Thanks for everyone's help... please go ahead and close this out!

                          1 Reply Last reply Reply Quote 1
                          • olivierlambertO olivierlambert marked this topic as a question on
                          • olivierlambertO olivierlambert has marked this topic as solved on
                          • First post
                            Last post