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

    Proxy response 400 !== 200

    Scheduled Pinned Locked Moved Management
    3 Posts 2 Posters 410 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.
    • P Offline
      Pilow
      last edited by olivierlambert

      Hi,

      I encounter this error when trying to add a host (master) on a different XOA

      server.enable
      {
        "id": "3c563df5-b08f-4b87-877e-68e4bc1e8f85"
      }
      {
        "name": "AbortError",
        "code": "UND_ERR_ABORTED",
        "call": {
          "duration": 240,
          "method": "session.login_with_password",
          "params": "* obfuscated *"
        },
        "message": "Proxy response (400) !== 200 when HTTP Tunneling",
        "stack": "AbortError: Proxy response (400) !== 200 when HTTP Tunneling
          at Client.connect (/usr/local/lib/node_modules/xo-server/node_modules/undici/lib/dispatcher/proxy-agent.js:87:22)"
      }
      

      The goal is to replicate a VM from a client infrastructure to our infrastructure, using an XO Proxy in our infra.
      I'm trying to add one host from our infra to theirs.

      We have a working xoproxy than can get to the host. IP of host added is the local IP of our infra.

      e5fec2fa-a789-4d78-86eb-4307f6a0bd0a-image.png

      What am i missing ?

      nb : our proxy is published by Nginx Proxy Manager on TCP Port 443 with a lets encrypt SSL certificate, that is different of internal certificates...

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

        Hi,

        Have you enabled websockets?

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

          @olivierlambert yes Olivier.

          but I'm in doubt of the correct redirection I have to make in NPM ... Should I port the token part of the url also in the redirected internal part ?

          or do I miss an nginx parameter to help pass this token 'inside' ?

          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