-
Notifications
You must be signed in to change notification settings - Fork 27
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
Could not launch local network: Orchestrator error: Provider error #401
Comments
Thanks for reporting the issue.
If is not the last one
|
I tried to redo it again but still have the same issue |
Apologies for the delayed response. I couldn't find the reason for your error.
Did the I experienced a similar issue in the past (link), but it was due to a wrong It might be a good idea to try removing this code:
And run |
Yes i use the standard parachain
even after removing this and Launching |
Thanks for your quick responses!
You can view the artifacts stored in the cache by running:
This command will display the cache path and list the stored binaries.
Could you navigate to the cache path and check if there are any permission issues with the binaries? It’s possible that WSL2 is causing some issues there. Under the hood, pop uses |
I have been following the docs to run locally a parachain for development purposes.
After running these :
I end up with this error
This is my network.toml
Did i forget anything ?
The text was updated successfully, but these errors were encountered: