New instances do not obey "Default AMP IP Binding"

  • 110 Views
  • Last Post 29 October 2019
  • Topic Is Solved
AbhorrentJoel posted this 27 October 2019

OS/Release: Ubuntu 18.04.3 LTS

Product Name/Version: AMP V1.8.8.0

Problem Description: New instances that are created do not obey the "Default AMP IP Binding" and proceed to be bound to 0.0.0.0 as opposed to 127.0.0.1 when set to that.

Steps to reproduce:

  • Change default binding to 127.0.0.1
  • Create new instance

The new instance will be bound to 0.0.0.0.

Actions taken to resolve so far:

I have removed all the instances, changed the setting to 0.0.0.0 and back to 127.0.0.1 again followed by a restart of the ADS instance. After restart, new instances were created but again the setting was not obyed and all new instances were bound to 0.0.0.0. This has also been confirmed by using netstat (so it is not an interface bug).

I know this was mentioned a few weeks back here, but I was just wondering what the status of this issue was. I can firewall it and have firewall'd it so it is not a massive problem.

AbhorrentJoel posted this 29 October 2019

Looks like this is fixed in the Nightly. At least it is fixed in v20191029.1.

Close