Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EXAMPLE ISSUE📢 security-api won't start, container keeps restarting because access key/trial key invalid #8

Open
daniel-trow opened this issue Nov 22, 2019 · 1 comment

Comments

@daniel-trow
Copy link
Collaborator

daniel-trow commented Nov 22, 2019

security-api won't start and the container keeps restarting because it says the access or trial key is not valid.

@daniel-trow
Copy link
Collaborator Author

daniel-trow commented Nov 22, 2019

ANSWER

A valid access or trial key is required to start security-api. This key can be provided as an environmental variable or through the database. The Velocity installer checks the validity of a key before installing, so that Velocity will only be configured with valid keys. Between the database and environmental variable keys, at least one must be valid. It is possible to not yet have a valid key in the database and for an invalid access or trial key to be introduced through an environmental variable that overrides the default configuration and prevents security-api from starting.

@daniel-trow daniel-trow changed the title security-api won't start, container keeps restarting because access key/trial key invalid EXAMPLE ISSUE📢 security-api won't start, container keeps restarting because access key/trial key invalid Jul 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant