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

Redeploy caused a failed to decrypt async call request error #2652

Closed
gak opened this issue Sep 11, 2024 · 1 comment
Closed

Redeploy caused a failed to decrypt async call request error #2652

gak opened this issue Sep 11, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@gak
Copy link
Contributor

gak commented Sep 11, 2024

Previous deploy was related to checking if the key had changed, closely to another PR before that:

Logs: https://sq-tbd.slack.com/archives/C04PEQERFM0/p1726098113325829?thread_ts=1726095281.120829&cid=C04PEQERFM0

Sep 12 08:40:57.104 ftl-controller Starting FTL controller
Sep 12 08:40:57.104 ftl-controller Web console available at: http://10.2.109.16:8892
Sep 12 08:40:57.104 ftl-controller Encryption key found, using it

...

Sep 12 08:45:03.276 ftl-controller Created deployment dpl-customers-4hwzuv6k3g8nduq6
Sep 12 08:45:04.277 ftl-controller failed to decrypt async call request: failed to decrypt binary with subkey async: failed to decrypt: aead_factory: decryption failed

Potential problems:

  • Key was changed: seems unlikely since there is a check on startup to verify the correct key, but could be a bug in the checking code (the PR above)
  • NULL or empty string in the async rows.. it not checked properly, this could cause this error.
@github-actions github-actions bot added the triage Issue needs triaging label Sep 11, 2024
@gak gak added the bug Something isn't working label Sep 11, 2024
@ftl-robot ftl-robot mentioned this issue Sep 11, 2024
@gak
Copy link
Contributor Author

gak commented Sep 12, 2024

  • Key does not appear to have changed based on the logs
  • No nulls or empty strings in the request field (where the error mentioned)

@github-actions github-actions bot removed the triage Issue needs triaging label Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants