Snow Commander vmware‑proxy startup failure caused by incorrect keystore password
This article helps you resolve an issue where the Snow Commander vmware‑proxy service fails to start. This problem typically occurs when the proxy can’t load the SSL keystore because the password in the configuration doesn’t match the actual keystore password. Fixing the password mismatch allows the service to start normally.
Review the vmware‑proxy logs
Check the logs in the following directory on the Access Proxy:
/var/data/logs/
Errors similar to the following indicate a keystore password issue:
Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect Caused by: java.security.UnrecoverableKeyException: Password verification failed
Verify the correct keystore password
Run the following command in your environment to inspect the keystore:
keytool -list -keystore /var/data/conf/keystore
When prompted, enter the password.
- If the password is correct, the keystore contents list successfully.
- If it's incorrect, the utility returns an error.
Update the password in your deployment configuration
Edit your docker-compose.yml file and update the environment variable with the verified password:
SERVER_SSL_KEY_STORE_PASSWORD=<correct_keystore_password>
Restart the Access Proxy service
Run the following commands to apply the change:
docker-compose down && docker-compose up -d
After updating the correct keystore password and restarting the service:
- The vmware‑proxy component should start without SSL-related errors.
- You should no longer see keystore or password verification failures in the logs.
