Accessing Instance Console Fails From Primary Region
PreviousForcefully Delete Cinder Volume of Non-existing Cinder Hosts.NextHostagent Fails to Communicate With the Management Plane due to Wrong Credentials
Last updated
While accessing the instance console from primary region for an instance launched in the secondary region, the UI redirect never completes and the console fails to load. Console access works when it is accessed directly from the secondary region's UI.
Platform9 Managed OpenStack - All versions
Clarity UI
During redirection from primary to secondary region UI, the authentication cookie gets blocked by the browser.
To remediate this, all the relevant region URL(s) must be allowed from the browser's Privacy & Security settings.
In Firefox:
Go to Settings -> Privacy and Security .

Under the Cookies and Site Data section, select Manage Exceptions and add all the primary and secondary region URLs.

In Chrome:
Go to Settings -> Privacy and Security .
Under the Third-party Cookies section, hover down to Allowed to use third party cookies section and add all the primary and secondary region URLs.

Last updated
