Trouble getting started
Hi!
I followed the guide at:
https://support.1password.com/connect-deploy-kubernetes/#step-2-deploy-a-1password-connect-server
And I have two K8-containers running (without problem as far as I can see) in Docker Desktop running locally on my Windows computer.
Connect-sync
{"log_message":"(W) configured to use HTTP with no TLS","timestamp":"2021-10-10T07:54:07.2444256Z","level":2} {"log_message":"(I) [discovery-local] starting discovery, advertising endpoint 42561 /meta/message","timestamp":"2021-10-10T07:54:07.2447418Z","level":3} {"log_message":"(I) starting 1Password Connect Sync ...","timestamp":"2021-10-10T07:54:07.2456985Z","level":3} {"log_message":"(I) serving on :8081","timestamp":"2021-10-10T07:54:07.2457609Z","level":3} {"log_message":"(I) database initialization complete","timestamp":"2021-10-10T07:54:07.2470764Z","level":3} {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2021-10-10T07:54:07.2472026Z","level":3} {"log_message":"(I) GET /health","timestamp":"2021-10-10T07:54:22.3043622Z","level":3,"scope":{"request_id":"5d52c280-ce69-439c-a35b-e06d0f4aceeb"}} {"log_message":"(I) GET /health completed (200: OK)","timestamp":"2021-10-10T07:54:22.3045174Z","level":3,"scope":{"request_id":"5d52c280-ce69-439c-a35b-e06d0f4aceeb"}}
Connect-Api
{"log_message":"(W) configured to use HTTP with no TLS","timestamp":"2021-10-10T07:54:07.1816805Z","level":2} {"log_message":"(I) [discovery-local] starting discovery, advertising endpoint 37629 /meta/message","timestamp":"2021-10-10T07:54:07.1822726Z","level":3} {"log_message":"(I) starting 1Password Connect API ...","timestamp":"2021-10-10T07:54:07.1825144Z","level":3} {"log_message":"(I) serving on :8080","timestamp":"2021-10-10T07:54:07.1825535Z","level":3} {"log_message":"(I) GET /health","timestamp":"2021-10-10T07:54:22.3053204Z","level":3,"scope":{"request_id":"6c9dd3f6-4cbf-4329-bafc-402b2c9ef721"}} {"log_message":"(I) GET /health completed (200: OK)","timestamp":"2021-10-10T07:54:22.305767Z","level":3,"scope":{"request_id":"6c9dd3f6-4cbf-4329-bafc-402b2c9ef721"}}
My problem is that when I try to connect to http://localhost:8080 in Postman (using a bearer-token that I generated on 1password.com) I get
Error: connect ECONNREFUSED 127.0.0.1:8080
Does anyone have any idea what might be the problem?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Comments
-
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:31087Now 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'sAm I missing something?
0 -
I finally got everything working :) I created a new connectserver and issued a new connecttoken and after that everything is working fine
0