6.2

Table Of Contents
2 Go to the /etc/vcac/ directory and check the permissions and ownership for the Encryption.key
file. You should see a line similar to the following one:
-rw------- 1 vcac vcac 48 Dec 4 06:48 encryption.key
Read and write permission is required and the owner and group for the file must be vcac.
3 If the output you see is different, change the permissions or ownership of the file as needed.
What to do next
Log in to the Tenant page to verify that you can log in without error.
Log in to the vRealize Automation Console Fails
Your installation appears to have completed successfully, but you cannot log in to the console.
Problem
You cannot log in to the vRealize Automation console at https://vcac-va-hostname/vcac.
Cause
Multiple conditions can prevent you from logging in to vRealize Automation console.
For example, the machine from which the user authenticates using Windows Authentication must be
joined to the domain in which the vRealize Automation Identity Appliance is configured. See User
Accounts and Credentials Required for Installation.
Solution
1 Navigate to the Identity Appliance management console by using its fully qualified domain name,
https://identity-hostname.domain.name:5480/.
2 Log in and select System > Reboot to reboot the appliance.
3 Navigate to the vRealize Appliance management console by using its fully qualified domain name,
https://vra-va-hostname.domain.name:5480/.
4 Log in and select System > Reboot to reboot the appliance.
You can also check the status of the services under the SSO tab in the vRealize Automation console
or log in to the appliance and run tail -f /var/vcac/log/catalina.out.
Error Communicating to the Remote Server
An error message indicating a communication problem between the vRealize Appliance and the Identity
Appliance appears when a problem exists in Common Name.
Installation and Configuration
VMware, Inc. 178