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

    Snapshot failure

    Scheduled Pinned Locked Moved Xen Orchestra
    12 Posts 3 Posters 745 Views 2 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.
    • S Offline
      sumansaha @sumansaha
      last edited by

      @sumansaha Even after that XOA can't connect with the XCP-NG . But from XOA we can SSH to the XCP-NG. Any help would be great.

      DarkbeldinD 1 Reply Last reply Reply Quote 0
      • DarkbeldinD Offline
        Darkbeldin Vates 🪐 Pro Support Team @sumansaha
        last edited by

        @sumansaha
        Hi,

        When you go to Settings > Server in XOA do you have a warning on the host connection?

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          sumansaha @Darkbeldin
          last edited by sumansaha

          @Darkbeldin Screenshot 2023-06-27 at 2.51.35 PM.png Screenshot 2023-06-27 at 2.52.48 PM.png

          Yes its showing the error as attached.But from XOA server we can SSH to XCP-NG without any issue.

          DarkbeldinD 1 Reply Last reply Reply Quote 0
          • DarkbeldinD Offline
            Darkbeldin Vates 🪐 Pro Support Team @sumansaha
            last edited by

            @sumansaha Did you made an XCP update recently? rebooted recently? forgot to reboot after update?

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              sumansaha @Darkbeldin
              last edited by

              @Darkbeldin It was not updated nor rebooted actually.

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

                @sumansaha said in Snapshot failure:

                https://192.168.196.99

                Check if your host is answering on this URL.

                S 1 Reply Last reply Reply Quote 0
                • S Offline
                  sumansaha @olivierlambert
                  last edited by

                  @olivierlambert suman@xoa:~$ wget --no-check-certificate https://192.168.196.99
                  --2023-06-27 17:34:59-- https://192.168.196.99/
                  Connecting to 192.168.196.99:443... connected.
                  WARNING: cannot verify 192.168.196.99's certificate, issued by ‘CN=xcp-ng-ohiphxpk’:
                  Self-signed certificate encountered.
                  WARNING: certificate common name ‘xcp-ng-ohiphxpk’ doesn't match requested host name ‘192.168.196.99’.
                  Failed writing HTTP request: Connection reset by peer.
                  Retrying.

                  It is not accessible through the URL.

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

                    Try with a browser and see what you have 🙂

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      sumansaha @olivierlambert
                      last edited by

                      @olivierlambert BTW new finding is , we also can't connect the XCP-NG with XCP-NG center. That mean the issue is with the XCP-NG server.

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

                        @sumansaha As the issue is not only with XO. I can create the discussion again out of XO.

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

                          @sumansaha
                          Hello Team,
                          The issue has resolved after applying xe-toolstack-restart.
                          Thanks.

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