Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.

Failed to pair #104

Open
stratosgear opened this issue Aug 29, 2018 · 4 comments
Open

Failed to pair #104

stratosgear opened this issue Aug 29, 2018 · 4 comments

Comments

@stratosgear
Copy link

Hello, what resources are available to test why pairing with my computer fails? I just get a "Failed to pair with Chrome Linux" message on my phone, soon after I scan the QR code.

I'm using Android Android 8.0.1, and Arch Linux 4.18.5-arch1-1-ARCH #1 SMP PREEMPT Fri Aug 24 12:48:58 UTC 2018 x86_64 GNU/Linux

I believe I run the latest versions of the Chrome Extension (1.0.9) and the kr cli utility (2.4.11).

Pairing with the extension or the command line, fails with the same message.

Thanks!

@kcking
Copy link
Contributor

kcking commented Aug 29, 2018

One thing to test is whether AWS SQS is available from your workstation. You can check this by running kr debugaws

Are you running behind a corporate firewall or vpn?

@stratosgear
Copy link
Author

kr debugaws seems to work ok:

 ~  kr debugaws
Create SQS Queue took 1255ms
Send SQS Message took 143ms
Receive SQS Message took 267ms
AWS connectivity check succeeded.

And yes, I AM behind a corporate firewall. I can try again later from home to compare!

@stratosgear
Copy link
Author

Yes, from home it pairs correctly. What ports are you trying to use?

@kcking
Copy link
Contributor

kcking commented Sep 5, 2018

We just use AWS SQS/SNS over https (443). These are the hostnames:

  • sns.us-east-1.amazonaws.com
  • queue.amazonaws.com
  • sqs.us-east-1.amazonaws.com

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants