For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

bowlingbe's avatar
bowlingbe
Icon for Nimbostratus rankNimbostratus
Dec 15, 2012

Internal Sites not Working through local APM proxy http://127.0.0.1:44777/

We are seeing an issue where internal sites are not working when connecting through the f5 APM edge device. We have noticed the the virutal adapter sets the proxy to us an automatic configuration script of http://127.0.0.1:44777/. However, this is not what our clients have their proxy set to when truly on the network. If I change the virtual adapter to go to our true proxy servers or user our proxy .pac the site comes up. However, this setting only remains for a few seconds and automatically gets changed back. Why is the virtual adapter set to this and how can I configure it to just use what the browser normally uses? This is causing great pains in our organization.

 

Thanks!

 

BIG-IP Access Policy Manager (APM)
remote access
security

5 Replies

  • Seth_Cooper's avatar
    Seth_Cooper
    Icon for Employee rankEmployee
    Jan 15, 2013
    Hi,

     

     

    Can you use group policy to push the .pac file configuration to your users and not configure the APM to provide the proxy? I have used the proxy configuration on firepass and APM without any issue. You might open a browser and point it to http://127.0.0.1:44777 and view what the pac file has in it. It might be that you provided it the wrong file.

     

     

    Seth
  • Seth_Cooper's avatar
    Seth_Cooper
    Icon for Employee rankEmployee
    Jan 15, 2013
    Hi,

     

     

    Can you use group policy to push the .pac file configuration to your users and not configure the APM to provide the proxy? I have used the proxy configuration on firepass and APM without any issue. You might open a browser and point it to http://127.0.0.1:44777 and view what the pac file has in it. It might be that you provided it the wrong file.

     

     

    Seth
  • bowlingbe's avatar
    bowlingbe
    Icon for Nimbostratus rankNimbostratus
    Jan 16, 2013

    The 127. pac file is the correct file. I'm not sure how group policy would do that. We have policies in place that do set the correct proxy.pac file in IE. The issue is that APM creates it's own adapter and downloads the file locally and points VPN users to the 127. I just want the VPN adapter to use the same path as the normal IE settings.

     

    • kimhenriksen's avatar
      kimhenriksen
      Icon for Cirrocumulus rankCirrocumulus
      Apr 05, 2017

      I know this is an old thread but.. did you make any progress with this? We´re trying to do the same here, we dont want to use the 127.0.0.1 url for the proxyscript. We want the proxy.fakenet.net/proxy.js

       

    • domokos_23867's avatar
      domokos_23867
      Icon for Nimbostratus rankNimbostratus
      Dec 20, 2017

      Hello, also on this issue. In our case the F5 APM policy is not configured to provide the http://127.0.0.1:44777/ proxy file. However on Win10 PCs we do see it being set (not on WIN7). Any ideas why it does it and if it can be turned off? I have a case open as well, but it takes some time :-)