Couldn't connect to the sign-in address you provided

do I need to set OP_DEVICE before running script for add or signin ?

I think what you have there being set is fine. Do you mind trying this command from inside the cloud instance and let me know what the response is? It should print the http response code of trying to reach the signin address page.

curl -o /dev/null --silent -Iw '%{http_code}' https://www.<1password signin address>

If that call does not return a 200, there may be some networking issues to resolve.

thanks for the reply I tried the curl and still its same error
even-though the curl is returning 200 (pls see here).
just for info - I am running this in cloud run (which is serverless)

2022-04-28 12:37:45.727 CESTInside success script
Default
2022-04-28 12:37:45.827 CEST4 qipakwsw77hx6pjpezhqnu2rq
Default
2022-04-28 12:37:45.827 CEST
Default
2022-04-28 12:38:18.527 CESTInside success script
Default
2022-04-28 12:38:18.527 CEST 200
Default
2022-04-28 12:38:47.026 CESTInside Error
Default
2022-04-28 12:38:47.027 CEST[ERROR] 2022/04/28 10:38:46 Couldn't connect to the sign-in address you provided. Check the address and your network connection, then try again.
Default
2022-04-28 12:38:47.027 CEST
Default
2022-04-28 12:38:52.928 CESTInside Error
Default
2022-04-28 12:38:53.427 CESTNo accounts configured for use with 1Password CLI.
Default
2022-04-28 12:38:53.427 CEST
Default
2022-04-28 12:38:53.427 CESTYou can either:
Default
2022-04-28 12:38:53.427 CEST - Sign in with biometric unlock; see https://developer.1password.com/docs/cli/get-started/#sign-in for details.
Default
2022-04-28 12:38:53.427 CEST - Add an account manually with op account add; see op account add --help for details.

Thanks for the info, I am going to add this issue to the ongoing investigation we have with the CLI not working on another serverless instance (AWS Lambda).

Thanks a lot .. please let me posted with solution or any progress with CLI on serverless instance (cloudrun or AWS Lambda). please share the link for AWS Lamba issue as well so I can track that

Hey @avinashdubeyse,
My colleague, @"Justin.Yoon_1P" has updated the ticket with the details of this report.
Alas, our issue tracking is handled internally. Here is a link to the original AWS Lambda thread, in the meantime:
https://1password.community/discussion/123194/cli-exiting-with-error-code-133-on-aws-lambda

We'll make sure to keep you updated, as we make progress with this.
Thank you for your patience.

Best,
Horia