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

    XO Proxy not working

    Scheduled Pinned Locked Moved Xen Orchestra
    23 Posts 4 Posters 5.9k Views 5 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.
    • bullerwinsB Offline
      bullerwins @olivierlambert
      last edited by

      @olivierlambert said in XO Proxy not working:

      Your proxy is probably outdated 🤔 You need to update your proxy first.

      @julien-f am I right?

      hi @olivierlambert !
      I'm sorry but how would I update it?
      To be honest I just installed it yesterday once a couple of times testing and again from scratch today. I would guess the bash -c "$(wget -qO- https://xoa.io/proxy/deploy) from the blog would just grab the latest version?

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

        Okay I discussed that with Julien, and the possibility to update it will be available on our tomorrow's release (on latest channel). Hang on 😉

        As soon you can make the update, the "proxy" will work.

        bullerwinsB 1 Reply Last reply Reply Quote 1
        • bullerwinsB Offline
          bullerwins @olivierlambert
          last edited by

          @olivierlambert That's great!!!
          Thanks a lot.

          Even though I don't know how to update it I can install it from scratch as this is just to learn in my homelab. Also I'm not so sure which channel I'm using to be able to select latest, is this for the proxy or for xoa?

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

            Both, they are synchronized on the one you choose in XOA 🙂

            bullerwinsB 1 Reply Last reply Reply Quote 0
            • bullerwinsB Offline
              bullerwins @olivierlambert
              last edited by

              @olivierlambert Hi! I believe that I have updated to the latest version (I have "warm migration" feature for example):

              02768039-5ce8-452a-9b68-48e2910980f9-image.png

              And I did the "force upgrade" in the proxy:

              9560ee2e-182a-435f-82a5-27282d172ba4-image.png

              But I have the same results:

              XOA doens't seem to fully connect to the remote xcp-ng server

              fafc9a34-5342-4c26-8ba8-67471edd008c-image.png

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

                Ping @julien-f

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

                  @bullerwins It may be necessary to upgrade multiple times the proxy if the VM is not known to the main XO.

                  If it does not work, open a support tunnel on your XO and we'll take a look directly.

                  bullerwinsB 1 Reply Last reply Reply Quote 1
                  • bullerwinsB Offline
                    bullerwins @julien-f
                    last edited by

                    @julien-f

                    Hi! I installed the proxy from scratch again in the remote xcp-ng, registered via xo-cli in the local XOA and got this in XOA:
                    3070aa20-2de8-4adb-9dde-0f6213a220c3-image.png

                    I clicked the "upgrade" but got this error:

                    proxy.upgradeAppliance
                    {
                      "id": "a5e1b282-b10c-471d-9a4b-02477134e895"
                    }
                    {
                      "code": "ECONNRESET",
                      "url": "https://servidorpapa.duckdns.org:4443/api/v1",
                      "message": "socket hang up",
                      "name": "Error",
                      "stack": "Error: socket hang up
                        at connResetException (node:internal/errors:705:14)
                        at TLSSocket.socketCloseListener (node:_http_client:467:25)
                        at TLSSocket.emit (node:events:525:35)
                        at TLSSocket.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202211301523/@xen-orchestra/log/configure.js:135:17)
                        at node:net:301:12
                        at TCP.done (node:_tls_wrap:588:7)
                        at TCP.callbackTrampoline (node:internal/async_hooks:130:17)"
                    }
                    

                    After checking the logs and going back to the proxy page it said that it's up to date:
                    7c4fa5a1-c908-4089-8f87-2d5c572ecf62-image.png

                    I clicked the force upgrade a few times and it always said that the proxy is up-do-date but the VM is still unknown:
                    3f769931-c3a8-4513-888f-261bc160c72b-image.png

                    I'm not sure how to open a support tunnel, is there any documentation about how to do it?

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

                      @bullerwins Yes: https://xen-orchestra.com/docs/xoa.html#support-tunnel

                      bullerwinsB 1 Reply Last reply Reply Quote 0
                      • bullerwinsB Offline
                        bullerwins @julien-f
                        last edited by

                        @julien-f I believe this is for the supported version. I'm build from sources. Should I maybe try the trial premium version?

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

                          @bullerwins Indeed this is only for the official XO Appliances, my bad.

                          What you can do is deploy an official XOA in trial, register your proxy on it and open a support tunnel if you have the same behavior 🙂

                          bullerwinsB 1 Reply Last reply Reply Quote 0
                          • bullerwinsB Offline
                            bullerwins @julien-f
                            last edited by

                            @julien-f I've setup a premium trial, added the proxy via the CLI (even I could now use the GUI with the premium):
                            6a63e329-d685-49df-8964-71ed0a7fd4da-image.png

                            Seems like the same results. "Unknown VM". I click "force upgrade proxy" a few times and it says that it's up to date (same behaviur).

                            I created a support tunnel in the XOA premium:

                            c23762e7-6ade-4719-8bdb-1fcebda07c69-image.png

                            "Give this id to the support: 44155"

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

                              @bullerwins On it!

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

                                @bullerwins Restarting the xo-proxy service was enough to fix the issue.

                                If it happens again, I'll look into it further.

                                bullerwinsB 1 Reply Last reply Reply Quote 0
                                • bullerwinsB Offline
                                  bullerwins @julien-f
                                  last edited by

                                  @julien-f what is the command to restart the proxy? so I can try to do it in the build from sources XOA

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

                                    @bullerwins The issue was that the xo-proxy service was not restarted after being upgraded on the XO Proxy Appliance. I've found the cause and it will be fixed in the next release.

                                    In the meantime simply restart the XO Proxy Appliance if you have this problem again 🙂

                                    bullerwinsB 1 Reply Last reply Reply Quote 0
                                    • bullerwinsB Offline
                                      bullerwins @julien-f
                                      last edited by

                                      @julien-f Thank you so much, I restarted the XOA built from source ubuntu VM and now it works! (how could I not thought of this before #1 rule in IT, turn off and on again).
                                      Thanks a lot for the support.

                                      1 Reply Last reply Reply Quote 1
                                      • bullerwinsB Offline
                                        bullerwins
                                        last edited by

                                        This would be a more of a theoretical question:

                                        Provided that I already have a VPN tunnel set up between the networks, and I'm going to keep it as I use it for other stuff.

                                        Is there any benefit of using the XO-proxy vs a VPN tunnel installed in the XOA vm?

                                        The way I see it is:

                                        Pro XO-proxy:
                                        -Easier to set up
                                        -No need to update/mantain a vpn client in the host OS and remote network as it updates with XOA and the proxy can be updated with a click.
                                        -Might have advantages down the road if more development is done to the proxy and I'm already using it and no need to migrate from the vpn tunnel method.
                                        -Basically all-in-one solution as I don't need to worry about 3rd party stuff. If I migrate I don't have to worry/remember the vpn stuff to be able to connect.

                                        Con XO-proxy:
                                        -That I have to open another port in the router if I already have a VPN tunnel.

                                        I'm just wondering if it's worth to keep another port open in the router.

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

                                          Depends if you have other needs for the VPN, but if it's only XO related, the proxy is a better solution 🙂

                                          1 Reply Last reply Reply Quote 0
                                          • F Offline
                                            flameshretoos
                                            last edited by flameshretoos

                                            Ultimately, the choice depends on your specific requirements, security considerations, and the trade-offs you are willing to make. If security is a top priority, and the existing VPN tunnel meets your needs, sticking with it might be the best option. I also have a lot to say, if you want to buy proxies, contact me personally. However, if the advantages of XO-proxy are compelling, and you can address the security concerns, it could be a reasonable choice.

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