App is not configured for this data center.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

App is not configured for this data center.

L3 Networker

When installing the Alero connector on a RHEL machine, I successfully install the alero-connector, pull the container from Docker Hub but I receive the error message: "App is not configured for this data center." once I try to initialize the connector.

 

Additional information:

  • It is a reinstallation of the Alero connector on the server

 

Why do I get the error "App is not configured for this data center."?

1 accepted solution

Accepted Solutions

L2 Linker

"App is not configured for this data center."

 

This means your Alero app is not currently configured to the same Alero datacenter as the domain where the connector you are try to initialize is located.

  • If the tenant is in alero.io (US data center) - the ending of the install connector command should have been --environment_domain alero.io AND the mobile app should be 'pointed' at the US datacenter.
  • If the tenant is in alero.eu (EU data center) - the ending of the install connector command should have been --environment_domain alero.eu AND the mobile app should be 'pointed' at the EU datacenter.
  • If the tenant is in ca.alero.io (Canadian data center) - the ending of the install connector command should have been --environment_domain ca.alero.io AND the mobile app should be 'pointed' at the Canada datacenter.

 

Ref -

Change your data center in Alero mobile app

Install connector command with appropriate domain ending

View solution in original post

2 REPLIES 2

L3 Networker

If you already once installed the connector on the machine and for whatever reason have to reinstall it, you need to remove residual folder, files, etc. from the machine before reinstalling the connector.

In the troubleshooting steps of the Alero documentation are the commands which completely remove all parts of the connector from the server:

sudo docker kill alero.connector sudo docker rm alero.connector sudo docker rmi docker.io/alerocyberark/connector:latest sudo docker volume rm alero-app sudo docker volume rm alero-logs sudo snap remove alero-connector

Once everything is removed, one can reinstall the connector and this error message should not appear.

L2 Linker

"App is not configured for this data center."

 

This means your Alero app is not currently configured to the same Alero datacenter as the domain where the connector you are try to initialize is located.

  • If the tenant is in alero.io (US data center) - the ending of the install connector command should have been --environment_domain alero.io AND the mobile app should be 'pointed' at the US datacenter.
  • If the tenant is in alero.eu (EU data center) - the ending of the install connector command should have been --environment_domain alero.eu AND the mobile app should be 'pointed' at the EU datacenter.
  • If the tenant is in ca.alero.io (Canadian data center) - the ending of the install connector command should have been --environment_domain ca.alero.io AND the mobile app should be 'pointed' at the Canada datacenter.

 

Ref -

Change your data center in Alero mobile app

Install connector command with appropriate domain ending

  • 1 accepted solution
  • 1119 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!