Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amplify Admin not communicating with CLI #14

Closed
DHFJIEKSMfjfdig645879312494876623644384 opened this issue Dec 3, 2020 · 11 comments
Closed
Assignees
Labels
pending-response An issue is pending response from the issue requestor

Comments

@DHFJIEKSMfjfdig645879312494876623644384

Hey all,

I'm running into a bit of an issue before I'm getting started.
I'm trying to link up my CLI with my Admin account on Amplify and when I run the line of code from the panel
"amplify pull --appId d************ --envName Example"
to the CLI for a pull, it won't communicate and stops me from connecting.

It says: "Failed to communnicate with the Amplify CLI. You can try again by running:
amplify configure --appId d************ --envName Example"

I'm pretty new at this stuff so if it seems obvious, I'm a noob.
Can anyone please help?

Many thanks,
Adam

@kaustavghosh06
Copy link
Contributor

Hello, which Platform/OS and browser are you using?

@DHFJIEKSMfjfdig645879312494876623644384

Hello, which Platform/OS and browser are you using?

I'm running Windows 10 and I'm using Brave browser

@kaustavghosh06
Copy link
Contributor

Can you try Google chrome or firefox and see if that resolves this issue?

@kaustavghosh06 kaustavghosh06 added the pending-response An issue is pending response from the issue requestor label Dec 3, 2020
@kaustavghosh06 kaustavghosh06 self-assigned this Dec 3, 2020
@DHFJIEKSMfjfdig645879312494876623644384

Can you try Google chrome or firefox and see if that resolves this issue?

Hey, sorry I'd went to sleep.
I'd been using the CLI that AWS recommends called Node.js CLI.

I'll install Firefox and try to get through that way

@DHFJIEKSMfjfdig645879312494876623644384

Can you try Google chrome or firefox and see if that resolves this issue?

Hey, sorry I'd went to sleep.
I'd been using the CLI that AWS recommends called Node.js CLI.

I'll install Firefox and try to get through that way

It still won't work unfortunately. It says it still can't communicate :(

@DHFJIEKSMfjfdig645879312494876623644384

All solved! I was just being a Muppet, thank you for your help!

@ajenkins
Copy link

ajenkins commented Dec 9, 2020

@DHFJIEKSMfjfdig645879312494876623644384 I'm running into the same problem. What did you do to fix this? The only suggestion the Admin UI gives is to try running the pull command again, but that's not helping.

I'm on Mac OS 11.0.1 and using Safari.

@ajenkins
Copy link

ajenkins commented Dec 9, 2020

Update: Switching my default browser to Firefox resolved the issue, for some reason. For any maintainers reading this, I would at least fix the typo in the error message. Someone accidentally spelled "communicate" with two n's.

@kaustavghosh06
Copy link
Contributor

@ajenkins Ack. We'll make the change. Thank you for letting us know.

@krnrnee
Copy link

krnrnee commented May 13, 2022

I'm also having this issue. Running Mac OS 12.3.1 Tried both Safari and Chrome. Checked the port. The only thing running on 4242 is Amplify. Update: installed firefox and set to default. Still doesn't work. This is ridiculously glitchy.

@renebrandel
Copy link
Contributor

Hi folks - we just launched the new Amplify CLI version 9.1.0 to address this workflow! Check out all the details here: #84 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-response An issue is pending response from the issue requestor
Projects
None yet
Development

No branches or pull requests

5 participants