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 24.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.
    • I
      Ismail @StormMaster
      last edited by

      Thank you @StormMaster

      1 Reply Last reply
      Reply Quote 0
      • A abudef referenced this topic on
      • jontybrookJ
        jontybrook
        last edited by

        Ditto the fix from @StormMaster worked for me - many thanks.

        1 Reply Last reply
        Reply Quote 0
        • ?
          A Former User @tjkreidl
          last edited by

          @tjkreidl

          The command "xe task-cancel force-true ..." with the uuid of the pending tasks did not do anything for me. After trying it on the 3 tasks I had, issuing a "xe task-list" still show me the pending tasks. It it only by rebooting the host that the pending tasks disappear.

          1 Reply Last reply
          Reply Quote 0
          • ?
            A Former User
            last edited by

            Going back to an older version of XO source also did the trick for me.
            I was in the process of pushing in production a couple VM that were previously in test and that I had backed up a couple of days ago. I was very surprised not to be able to do anything with these VMs stuck on my SR used for VM backup

            tjkreidlT 1 Reply Last reply
            Reply Quote 0
            • tjkreidlT
              tjkreidl Ambassador @Guest
              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
                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
                  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
                    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
                      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
                        Bub @Danp
                        last edited by

                        @Danp Got you, thanks for the clarification!

                        1 Reply Last reply
                        Reply Quote 0
                        • D
                          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
                            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
                              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
                                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
                                  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.

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

                                    Thank you for the update Andy.

                                    1 Reply Last reply
                                    Reply Quote 0

                                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                    With your input, this post could be even better 💗

                                    Register Login
                                    • First post
                                      Last post