Claude Barde
1 min readMar 29, 2020

Hi, thank you for your feedback :)

I had a similar problem the other day, the migration seemed stuck and I got a timeout error after 3–4 minutes. I just restarted Docker Desktop and restarted the sandboxed node and everything was working again normally.

Let me know if that works for you too.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

Claude Barde
Claude Barde

Written by Claude Barde

Self-taught developer interested in web3, smart contracts and functional programming

Responses (1)

Write a response

So, when I use the docker containers provided in your repo everything works fine. However, I get stuck when using my own testnet. I have the feeling that it might have to do with fees or other stuff because my node receives the operation hash. Do you have experiences with non-flextesa-testnets as well?

--