Pivotal Knowledge Base

Follow

Pivotal Cloud Foundry® being associated with Internal IP rather than FQDN

Environment 

Product Version
Pivotal Cloud Foundry® (PCF) 1.7.x

Overview

Ops Manager should always be accessed via its Fully Qualified Domain Name (FQDN). (This is to prevent any issues if its IP address changes).

Symptom

If you are unable to access Ops Manger via its FQDN after first connecting to it via its internal IP, please carry out the following resolution.

Logging into OpsManager UI using FQDN gets error:

Invalid redirect https://<FQDN address>/auth/cloudfoundry/callback did not match one of the registered values

Cause 

If it is accessed via its internal IP after an initial install, this IP will be saved to the internal database rather than the FQDN.

When accessing Ops Manager for the first time, this address gets stored in the database as the default location for accessing Ops Manager.

Resolution

The database needs to be updated with Ops Manager FQDN rather than its IP address.

1. Log on to Ops Manager VM via Single SHell (SSH).
2. Connect to the postgres database and list the current settings.

sudo -u postgres psql -d tempest_production -c "SELECT id, hostname from uaa_configs"
 id |       hostname
----+----------------------
  1 | <ops manager  IP address>
(1 row)

3. Replace FQDN with the one that is bound to your IP address.

$ sudo -u postgres psql -d tempest_production -c "UPDATE uaa_configs set hostname='<Ops Manager FQDN>' where id=1"

4. Check again that it has updated correctly.

$ sudo -u postgres psql -d tempest_production -c "SELECT id, hostname from uaa_configs"
 id |       hostname
----+----------------------
  1 | <ops manager FQDN>
(1 row)

5. Reboot the Ops Manager VM. 

$ sudo shutdown -r

After rebooting, try to access your Ops Manager via its FQDN.

 

 

Comments

  • Avatar
    Brian OConnell

    Also works for PCF 1.8 and PCF 1.9

Powered by Zendesk