Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Proxy HA slow redirect https to http - [ miragration vm with different subnet ]

    Scheduled Pinned Locked Moved Cache/Proxy
    3 Posts 2 Posters 465 Views
    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.
    • W
      wesleylc1 Rebel Alliance
      last edited by wesleylc1

      Hello friends
      I want to hear from all of you, if the drawing migration should work, remembering that in my current scenario, it is composed of two xenserver servers with different subnets, but I want to load 'vms' on a single server.

      The new server has 4 network cards, two are already operating on the subnet 192.168.40.0/22 and the third interface will make available to the 192.168.45.0/24 subnet.0_1539698179327_MIGRACAO.jpg.8cea7a9182c06eb37edbaf1f5d265cd0.jpg

      After importing the site that was using the 192.168.45.14/24 network, it is too slow for external access, remembering that I used the HA proxy to redirect traffic to the site.

      This is log "proxy has"

      Oct 16 11:49:07 haproxy haproxy[41451]: 189.62.164.137:59991 [16/Oct/2018:11:48:37.912] HA_Sistemas-http HA_Sistemas-http/<NOSRV> -1/-1/-1/-1/30010 408 212 - - cR-- 10/10/0/0/0 0/0 "<BADREQ>"

      P 1 Reply Last reply Reply Quote 0
      • P
        PiBa @wesleylc1
        last edited by

        @wesleylc1
        After talkingw with Wesley this seems to have been fixed with a haproxy upgrade from 1.8.13 to 1.8.14.

        1 Reply Last reply Reply Quote 1
        • W
          wesleylc1 Rebel Alliance
          last edited by

          @piba said in Proxy HA slow redirect https to http - [ miragration vm with different subnet ]:

          haproxy upgrade from 1.8.13 to 1.8.14.

          @PiBa

          According to Pieter response, the case was resolved after the haproxy upgrade from 1.8.13 to 1.8.14.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.