It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
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...
Former Member
5 years agoHello David,
thank you very much for your quick and detailled reply. Before writing my previous message, we did exactly as suggested by you.
However, the
path to a directory on your server (for example, /var/docker/op)
does not seem to apply for plesk. If we use a path - any path outside of the volume directory created by docker for the connect-sync service results in various error message along the lines of
{"log_message":"(I) no database found, will retry in 1s","timestamp":"2021-09-29T12:55:56.278587349Z","level":3}
So we now have a path which is something along the lines of
/var/lib/docker/volumes/e24bc803a75870004......32093/1password-credentials.json and
/var/lib/docker/volumes/e24bc803a75870004......32093/_data
set for both containers.
BUT: Spending ~2 1/2 hours on this yesterday, along with two other developers, and another 1 hour today, trying all crazy stuff, out of a sudden, today, it worked. Not sure what did the trick. We had those settings at about half the time working on it yesterday.
Anyway, leaving this here in case someone else comes across the same issues.
Thanks!