Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Unknown: (504) (Unknown), An unknown error occurred
I'm ussing 1password cli in CI to load the secrets:
op read "op://[1password-address]" >> [env-file]
It works locally but on the CI I get an error:
https://github.com/Heydonto/heydonto-stack/actions/runs/21516022746/job/61994479498?pr=102#step:7:15 Error: 2026/01/30 12:41:15 could not read secret 'op://dev-secrets/.env.': could not get item dev-secrets/.env: Unknown: (504) (Unknown), An unknown error occurred.
We have a complex infra and we run op read a lot, is that a problem?
I'm sorry for any issues you had using 1Password earlier today. Our team has implemented a mitigation for the issue and has confirmed that the issue is now resolved. You should be able to use 1Password normally again. Additional information is available on our status page.
If you are still having trouble using 1Password then send an email to support@1Password.com and our team can help further.
-Dave
6 Replies
Everything's fine now, thank you!
- 1P_Dave
Moderator
I'm sorry for any issues you had using 1Password earlier today. Our team has implemented a mitigation for the issue and has confirmed that the issue is now resolved. You should be able to use 1Password normally again. Additional information is available on our status page.
If you are still having trouble using 1Password then send an email to support@1Password.com and our team can help further.
-Dave
- 1P_Timothy
Community Manager
Hi areson111, zywopus, pmdarrow. Thanks for flagging this, and my apologies for any trouble this has caused. Our team is investigating this issue, and working to mitigate it.
You can keep an eye on our status page, and let us know if you see any improvement or further issues. Thanks again.
1P_SimonH Any update on this issue? It's blocking all our deployments.
Yeah our CI is failing with this error frequently now. status.1password.com isn't showing any outage though 😞
Same here, we've been having the same CI issue for an hour or so.
