Hey Folks!, I'm trying to upgrade Hydra from v1.3....
# talk-hydra
b
Hey Folks!, I'm trying to upgrade Hydra from v1.3.2 to v1.11.10 (following self-hosted/upgrade ), but after exec "hydra migrate sql ..." it looks like it didn't work because i received this message: msg=Could not ensure that signing keys for "hydra.openid.id-token" exists. If you are running against a persistent SQL database this is most likely because your "secrets.system" ("SECRETS_SYSTEM" environment variable) is not set or changed. When running with an SQL database backend you need to make sure that the secret is set and stays the same, unless when doing key rotation. This may also happen when you forget to run "hydra migrate sql".. Do you know if it is necessary to do something extra before or after executing migrate?
t
Are you running
hydra migrate sql
as is, or are you passing in the Hydra config correctly which defines your secret?
Copy code
hydra migrate sql --config /etc/config/hydra.yaml
b
Hi.
I executed:
Copy code
hydra migrate sql "mysql://${DB_USER}:${DB_PASSWORD}@tcp($DB_HOSTS)/${DB_NAME}"
And the log showed: INFO[2023-08-28T144656Z] No tracer configured - skipping tracing setup audience=application service_name=Ory Hydra service_version=v1.11.10 The following migration is planned: Version Name Status 20190100000001000000 client Applied ... 20211226156000000000 dynamic_registration Applied 20220328111500000000 support_any_subject_trusts Applied To skip the next question use flag --yes (at your own risk). Do you wish to execute this migration plan? [y/n]: y Successfully applied migrations!
t
You need to pass the same configuration as your hydra instance, that'll be why you received the error around
secrets.system
not existing/changed