Forum Discussion

Former Member's avatar
Former Member
5 years ago

[Docker] [Plesk] 401: Invalid Bearer Token

We set up the 1pw connect and api locally through docker, which was working just fine. Today we tried to move it to online, but ran into several issues. Our current issue is, that even though dockers...
secrets management
Former Member's avatar
Former Member
5 years ago

Hello!

Sorry to hear that about the issues you're having with Plesk. I'm not too familiar with how Plesk handles Docker and Docker Volumes, but I can make some suggestions for how to map the Docker volumes.

Our https://github.com/1Password/connect/blob/ad080cc3c1f982ea6af5bf83dce6a736ef4a5fc4/examples/docker/compose/docker-compose.yaml example defines the following volumes:


volumes:
- "./1password-credentials.json:/home/opuser/.op/1password-credentials.json"
- "data:/home/opuser/.op/data"

If I understand Plesk's support https://support.plesk.com/hc/en-us/articles/115001973253-How-to-map-volumes-in-Docker-on-Plesk-server- then you'll need to configure the following:

Volume 1:
- Destination: /home/opuser/.op/1password-credentials.json
- Source: a path to the 1password-credentials.json file on your server

Volume 2:
- Destination: home/opuser/.op/data
- Source: path to a directory on your server (for example, /var/docker/op)

You would need both volumes for the API container and the Sync container.

I'm not sure if Plesk has special configurations for volumes, so these instructions may need some tweaking to work with Plesk.