"Your Connect server hasn’t contacted 1Password yet"

I spent longer than I care to admit trying to figure out why my integrations weren't updating beyond their initial states, even while Connect servers in both kubernetes and docker compose were running, and not logging any overt errors.

It would help us literal-minded types if that status message indicated that the Connect server will not try to phone home until it's been tickled by a duly-authorized client. I understood my.1password.com to be telling me that the Connect server was not yet functional, so proceeding to the next step took a while to occur to me.

Thanks for your time.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Comments

  • David_agDavid_ag

    Team Member

    Thanks for the feedback! That wording could be improved a little bit for us literal-interpretation folks, I agree.

    I'll talk to our documentation and design team and get back to you shortly. We can also try highlighting the aside that the Connect server will not have any access to secrets until it receives a valid token from an API request.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file