Trouble getting started

I passed this obstacle. I used the wrong portnumber for the NodePort.
service/onepassword-connect NodePort X.X.X.X <none> 8081:32581/TCP,8080:31087/TCP
Instead of calling http://localhost:8080 I should be calling http://localhost:31087

Now to the next obstacle... :) When I try to call http://localhost:31087/v1/vaults I get:
"status": 500," message": "failed to initiate, review service logs for details"

If I call http://localhost:31087/health I get:

{
"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": "TOKEN_NEEDED"
},
{
"service": "1Password",
"status": "UNINITIALIZED",
"message": "Make a request with a valid bearer token to initialize"
}

From the log:
```
{"log_message":"(E) syncer did not become healthy, terminating request","timestamp":"2021-10-12T15:03:12.0163204Z","level":1,"scope":{"request_id":"462d0e92-d5d6-4aa6-a41e-390356c6dfdc","jti":"oujuxf57ow4vymwlbynbf6rjje"}}

{"log_message":"(I) GET /v1/vaults completed (500: Internal Server Error)","timestamp":"2021-10-12T15:03:12.0164236Z","level":3,"scope":{"request_id":"462d0e92-d5d6-4aa6-a41e-390356c6dfdc","jti":"oujuxf57ow4vymwlbynbf6rjje"}}

And

{"log_message":"(I) token received, getting credentials and initializing API","timestamp":"2021-10-12T15:17:34.0979622Z","level":3}

{"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 8s), Wrapped: (failed to FindCredentials), Wrapped: (failed to Decrypt localAuthv2), Authentication failed, invalid bearer token","timestamp":"2021-10-12T15:17:34.1581481Z","level":1}
```

What I have done:
1. kubectl create secret generic onepassword-token
--from-literal=token=ey....
2. helm install connect 1password/connect --set-file connect.credentials=1password-credentials.json
3. I have copied 1password-credentials.json to /home/opuser/.op/data in the connect-api and connect-sync K8's

Am I missing something?

I finally got everything working :) I created a new connectserver and issued a new connecttoken and after that everything is working fine