I am trying to deploy 1password on a linux box using docker.
My compose file looks as follows:
version: "3.4"
services:
op-connect-api:
image: 1password/connect-api:latest
ports:
- "8080:8080"
volumes:
- "/home/forge/1password-credentials.json:/home/forge/.op/1password-credentials.json"
- "data:/home/opuser/.op/data"
op-connect-sync:
image: 1password/connect-sync:latest
ports:
- "8081:8080"
volumes:
- "/home/forge/1password-credentials.json:/home/forge/.op/1password-credentials.json"
- "data:/home/opuser/.op/data"
volumes:
data:
I am able to hit the /health url on http://localhost:8080/health and these are my results
{
"name": "1Password Connect API",
"version": "1.5.4",
"dependencies": [
{
"service": "sqlite",
"status": "ACTIVE",
"message": "Connected to /home/opuser/.op/data/1password.sqlite"
},
{
"service": "account_data",
"status": "NOT_SYNCED",
"message": "Account data is not available because synchronization has not yet started"
},
{
"service": "sync",
"status": "UNKNOWN"
},
{
"service": "1Password",
"status": "UNINITIALIZED",
"message": "Make a request with a valid bearer token to initialize"
}
]
}
I am however not able to view my vaults even after passing the correct tokens of curl -H "Accept: application/json" -H "Authorization: Bearer eyJhb..." http://localhost:8080/v1/vaults
RESULTS:
{"status":500,"message":"failed to initiate, review service logs for details"}
What should I do?
1Password Version: 2.5.1
Extension Version: 3.4
OS Version: Ubuntu 20.04.4 LTS
Browser:_ Not Provided
ref: IHS-38185-159
Comments
I discovered that the issue was permissions on my 1password-credentials.json. I ran a chmod a+r 1password-credentials.json so that the json file can be read by the server. Because the user did not have read/write permissions it could not access the file so as to login to 1password servers. Thanks.
Team Member
I'm glad you were able to sort this out, thank you for leaving an update!