-
Notifications
You must be signed in to change notification settings - Fork 823
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
unsupported proxy protocol: "127.0.0.1" #12890
Comments
Hey @Kidus-SANEDIGITAL 👋 thanks for raising this! When you pull the project what auth mechanism do you select? Does it prompt to authenticate with Amplify Studio? Additionally, are you working behind a proxy by chance? |
@josefaidt there are two option to authenticate from the amplify cli... aws access keys and aws profile. and which ever one i choose it always goes to aws profile authentication method... and it takes forever... at one point just to see i left it loading overnight and still nothing... |
Hey @Kidus-SANEDIGITAL thanks for clarifying! This sounds like it may be caused by a network-related issue. Are you working behind a corporate proxy or VPN by chance? Do you see any network-related logs that stand out in |
Hey @Kidus-SANEDIGITAL just wanted to check in here. Are you still experiencing this? |
Closing due to inactivity |
|
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v18.12.1
Amplify CLI Version
12.0.0
What operating system are you using?
windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no manual changes made
Describe the bug
trying to pull changes made in the amplify studio taking more than 24 hours authenticate the cli user and creating new app return this error " unsupported proxy protocol: "127.0.0.1" "
Expected behavior
amplify pull should have just pulled all the changes
Reproduction steps
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: