Wrong IP Addresses

Octopus Cloud
, ,
1

Hi.

We are running an Octopus Cloud Server instance. This morning, this instance started attempting to connect to some of our targets from the IP address 40.125.67.205. This address is not in the list of static IP addresses for our instance, which I have checked on the server’s details page. The full list is thus:
13.66.160.61
13.66.153.144
13.66.195.132
13.66.133.169
13.77.136.61
13.66.159.177
13.77.183.102
52.151.6.30
51.143.16.233
52.250.126.73
52.250.93.128/28

The last on that list is the block of IP addresses which Octopus has previously advised we should whitelist for access for the new system of addresses that Octopus Cloud is moving to, and I understand that the other IP addresses should be removed at a certain point in the future, but as they still remain in the static IP address list for the server, we have not removed them yet.

The IP address that Octopus is using, though, is not in that list, either as a single address or within the final block. We have allowed that IP address to connect to our testing environment, but I am currently unwilling to allow it to connect to our production environment without confirming that it is, indeed, an Octopus Cloud Server IP address.

Can you advise why we are seeing this IP address in use by what is apparently Octopus Cloud?

3

Hi @inv-services,

Apologies for the inconvenience here. The work being carried out to change the cloud instances from using the entire IP pool to the single range (52.250.93.128/28) has somehow caused an unexpected IP address (40.125.67.205) to be used.

Our engineers are in the process of moving any affected instances back to the original reef, so, if you are blocked at the moment then temporarily whitelisting 40.125.67.205 would be the quickest way to get back up and running.
It should be safe to remove that IP again after a day or so.

Regards,
Paul

4

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.