Tower/AWX no longer working due to IP address change

[Timothy Dilbert]

Hello,

I have an instance of Tower running in my environment. I recently moved DCs and as a result, I am running in a different subnet and had to change the IPs of all of my Tower servers as well as DNS.

Everything is done. However, Tower will not load. Instead, I am getting the following error:

```

2022/08/17 14:13:41 [error] 1139#0: *544 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.5.43, server: _, request: "GET / HTTP/1.1", upstream: "uwsgi://unix:/var/run/tower/uwsgi.sock", host: "tower.domain.local"

```

If it helps direct me to the answer, I'm noticing that the highlighted IP is the old IP address of the server. It seems as though the NGINX instance on the Tower server is not using the new IP address, even though RHEL and DNS have both been updated. There are also no entries in the local hosts file.

Any ideas on how I can force NGINX to use the updated IP?

[AWX Project]

For Tower support you can contact Red Hat for support.
That being said, node names and IPs may be sprinkled throughout the system. Did you update your installer inventory and re-run the installer? That should fix the IPs/hostnames in the necessary locations.

- The AWX Team