Skip to content
vScope Support Page

Troubleshoot HTTPS configuration in vScope

Use this page when HTTPS setup in vScope fails or when the web UI becomes inaccessible after enabling HTTPS.

Keystore and certificate errors

Section titled “Keystore and certificate errors”

Failed to update settings: Keystore validation failed: Alias ‘myalias’ not found in the keystore.

Section titled “Failed to update settings: Keystore validation failed: Alias ‘myalias’ not found in the keystore.”

The alias you entered was not found in the keystore.

  • If the keystore contains only one certificate, leave the alias field empty.
  • If the keystore contains multiple certificates, enter the alias for the certificate vScope should use.

Failed to update settings: Keystore validation failed: No certificate found in the keystore. If the keystore is password protected, make sure you have the correct keystore password.

Section titled “Failed to update settings: Keystore validation failed: No certificate found in the keystore. If the keystore is password protected, make sure you have the correct keystore password.”

vScope could not find a certificate in the keystore.

  • Confirm the file contains a certificate and private key.
  • If the keystore is password protected, enter the correct keystore password.

Failed to update settings: Keystore validation failed: No private key found in the keystore. HTTPS requires a private key to function.

Section titled “Failed to update settings: Keystore validation failed: No private key found in the keystore. HTTPS requires a private key to function.”

vScope could not find a private key in the keystore.

  • Confirm the keystore contains both certificate and private key.

Failed to update settings: Keystore validation failed: Private key could not be read. If the private key is password protected, make sure you have the correct key password.

Section titled “Failed to update settings: Keystore validation failed: Private key could not be read. If the private key is password protected, make sure you have the correct key password.”

The private key is likely password protected and the key password is missing or incorrect.

  • Re-enter the key password.
  • If you generated the keystore with OpenSSL, key and keystore passwords are often the same.

Failed to update settings: Keystore Parsing failed. Supported types: [pkcs12, jks]. Exceptions: [as ‘pkcs12’:keystore password was incorrect, as ‘jks’:keystore password was incorrect]

Section titled “Failed to update settings: Keystore Parsing failed. Supported types: [pkcs12, jks]. Exceptions: [as ‘pkcs12’:keystore password was incorrect, as ‘jks’:keystore password was incorrect]”

vScope could not parse the keystore because the keystore password is incorrect.

  • Re-enter the keystore password.
  • Re-export the keystore if you are unsure which password was used.

Locked out of vScope after enabling HTTPS

Section titled “Locked out of vScope after enabling HTTPS”

If HTTPS is misconfigured, disable it temporarily in local settings so you can access the UI and reconfigure.

  1. Stop the vScope service.
  2. Open the .settings folder in the vScope data folder, for example C:\vScopeData\configuration\.settings.
  3. Open com.infrasight.backend.app.webservice.prefs in a text editor.
  4. Change https.enabled = true to https.enabled = false.
  5. Start the vScope service.
  6. Open vScope and reconfigure HTTPS in Settings > Network.
Section titled “Related”