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

    Restoring from backup error: self-signed certificate

    Scheduled Pinned Locked Moved Solved Backup
    41 Posts 18 Posters 9.1k Views 19 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.
    • tjkreidlT Offline
      tjkreidl Ambassador @utmoab
      last edited by

      @utmoab Strange, but I've seen some tasks "stuck" that could not be cancelled for some reason or aanother. A reboot is a drastic measure, but unfortunate;y sometimes the only recourse.

      1 Reply Last reply Reply Quote 1
      • U Offline
        uwood
        last edited by

        I'm on commit 1b515 and the error still exists.

        Pending tasks can be cancelled with "restart toolstack" on host.

        nikadeN 1 Reply Last reply Reply Quote 1
        • nikadeN Offline
          nikade Top contributor @uwood
          last edited by

          The BRANCH="0ccfd4b" revert worked for me, backups are working again in the lab.

          1 Reply Last reply Reply Quote 0
          • B Offline
            Bub @StormMaster
            last edited by

            @StormMaster said in Restoring from backup error: self-signed certificate:

            BRANCH="0ccfd4b"
            This worked for me also, thank you.

            But after this change, I have tried to run update few times but it seems my commits are falling behind and do not update to the latest.
            Am I missing something?
            0911f507-f21c-4a6f-8601-20ef120c5cf1-image.png

            DanpD 1 Reply Last reply Reply Quote 0
            • DanpD Offline
              Danp Pro Support Team @Bub
              last edited by

              @Bub said in Restoring from backup error: self-signed certificate:

              Am I missing something?

              No, you're "stuck" on commit 0ccfd4b until you revert the change in the config file. It doesn't make sense to do that now, because then you will encounter the issues with backups / restores again. Once a fix has been pushed to the Github repo, then you can switch back to the master branch.

              B D 2 Replies Last reply Reply Quote 0
              • B Offline
                Bub @Danp
                last edited by

                @Danp Got you, thanks for the clarification!

                1 Reply Last reply Reply Quote 0
                • D Offline
                  dsiminiuk @Danp
                  last edited by

                  @Danp Is it safe to say this is being worked on? I don't want to assume anything.

                  DanpD 1 Reply Last reply Reply Quote 0
                  • DanpD Offline
                    Danp Pro Support Team @dsiminiuk
                    last edited by

                    @dsiminiuk I would assume so, but I don't know the specifics.

                    1 Reply Last reply Reply Quote 0
                    • MathieuM Mathieu referenced this topic on
                    • M manilx referenced this topic on
                    • M Offline
                      michmoor0725 @StormMaster
                      last edited by

                      @StormMaster
                      I dont see a PR or even an issue posted on the github. I can add one to the board for ronivay unless someones working on it.

                      S 1 Reply Last reply Reply Quote 0
                      • S Offline
                        StormMaster @michmoor0725
                        last edited by

                        @michmoor0725 Sure!

                        I don't think that it is a ronivay issue as it appears to be occurring with any self-signed certificate. Regardless of what was used to compile it.

                        That said, if some people check there instead of here, it mays good sense to have something posted there as well. 😉

                        A 1 Reply Last reply Reply Quote 1
                        • U uwood referenced this topic on
                        • A Offline
                          andyh @StormMaster
                          last edited by

                          According to a closed issue from Ronivay the problem looks to be resolved.

                          https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/227

                          I've just updated to latest from Branch="Master" and successfully performed a health check.

                          michmoor0725 created this issue in ronivay/XenOrchestraInstallerUpdater

                          closed Backup jobs - Health check fails #227

                          1 Reply Last reply Reply Quote 0
                          • DanpD Danp has marked this topic as solved on
                          • I Offline
                            Ismail
                            last edited by

                            Thank you for the update Andy.

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