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

Error: Looping Question: "Do you want to connect to ethereum-mainnet with one of your existing wallets on Gateway?" #332

Open
jabevan opened this issue Jun 20, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@jabevan
Copy link

jabevan commented Jun 20, 2024

Looping Question: "Do you want to connect to ethereum-mainnet with one of your existing wallets on Gateway?"
// I've gotten stuck in a loop trying to add a second DEX ethereum connection. I very successfully and easily added sushiswap ethereum mainnet to my dashboard. Now when I try to add uniswap ethereum mainnet or pancakeswap ethereum mainnet the system gets stuck asking me the wallet questions.

If I say Yes, that I want to use an existing wallet it just reasks the same question over and over again. It takes 2 minutes, or more, to timeout and go back to the main prompt.

If I say No, that I don't want to use an existing wallet, it gets stuck in a loop of asking me "Enter your ethereum-mainnet wallet private key."

If I CTRL-X, it just reasks me the respective question above.

I have tried the default node and nodes at Quicknode and Infura.

Note: that gateway connect does show that sushiswap and my wallet are successfully connected. Further, gateway balance does give me an error (maybe related, maybe coincidental). Finally, I'm also getting the time_synchronizer error that I believe was supposed to be fixed in 1.3??

Screenshots (Note: I have deleted and replace the node listed).

1 2 3 4 5 6

Log File:

logs_hummingbot.log

Release version
// Release 1.28

Discord username:
// @jabevan

@jabevan jabevan added the bug Something isn't working label Jun 20, 2024
@jabevan
Copy link
Author

jabevan commented Jun 20, 2024

Please note: I have included 6 screenshots above...

@jabevan
Copy link
Author

jabevan commented Jun 20, 2024

Please also note that I setup a new server from scratch (Ubuntu 20.04 again) in Singapore and am getting the exact same behavior.

@jabevan
Copy link
Author

jabevan commented Jun 26, 2024

PLEASE NOTE: This was apparently an issue with Vultr. After trying several times on Vultr I tried on AWS and it worked immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant