Troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
If you're seeing several installation errors (e.g. node-gyp rebuild
), the problem is probably due to an outdated Node.js version.
aragonCLI currently supports the latest releases of the following Node.js versions: 10, 11 and 12. Recommended version is node 12.7
Errors could also be do to the need for python2
as a dependency. In that case run:
If you're seeing errors similar to:
It's probably because you originally installed Node with root permissions. Because of this, writing to your npm directory (npm -i -g
) requires root permissions too.
While it's not a good idea to have Node installed this way, one way to quickly give yourself root permissions is to run the slightly modified command:
An arguably better way to fix the problem is to follow the steps outlined in this
In case of
Windows is not officially supported by aragonCLI at the moment.
You might need to run the shell with administrator rights when installing the aragonCLI, because our go-ipfs
dependency will need to create a symlink to work correctly.
In case the client is not loading properly, deleting the ~/.aragon
directory will make aragon run
recreate the environment the next time it is used and may solve the issue.
For interacting with aragonCLI you can configure a private key in ~/.aragon
. Create a file <network>_key.json
(eg. rinkeby_key.json
) with this structure:
Then if you use --environment aragon:<network>
when using the aragonCLI commands it will use that account.
You can also define a ~/.aragon/mnemonic.json
file like:
You can validate the smart contract and other files of a specific app installed in your Aragon organization with:
If you have a version older than 0.4.22
, you should first uninstall your current version with aragon ipfs uninstall
and install IPFS again with aragon ipfs install
.
After upgrading aragonCLI, or if unexpected errors are being experienced, resetting IPFS by deleting the ~/.ipfs
directory and then run aragon ipfs
sometimes help.
The best way around this is to:
Keep trying on the local ipfs daemon
Try accessing that same file in a more generic gateway, like ipfs.io/ipfs
When publishing a package via aragon apm publish
, you will be returned an IPFS content (root) hash. For the Aragon client to load these files through its default IPFS configuration, this hash needs to be accessible at: https://ipfs.eth.aragon.network/ipfs/<hash>
.
Otherwise, as a quick fix, if you are running into issues with your hash being propagated to this URL, try running ipfs propagate <hash>
or the following steps.
If you have aragon ipfs
running, quit that daemon.
Run the command ipfs daemon --enable-namesys-pubsub
.
Propagate your content through public gateways.
Request your content hash at the following gateways. The index.html
will automatically be loaded if it's available in the hash's root directory:
https://ipfs.eth.aragon.network/ipfs/<hash>
https://ipfs.io/ipfs/<hash>
https://ipfs.infura.io/ipfs/<hash>
If your content also includes an artifact.json
or manifest.json
, make sure to separately request these as they will usually not be requested by the index.html
:
<gateway>/ipfs/<hash>/artifact.json
<gateway>/ipfs/<hash>/manifest.json
Keep retrying if any files don't immediately become available.
Once successful with step 3, request your hash at the Aragon gateway to double check it has propagated and is immediately accessible by the Aragon client:
https://ipfs.eth.aragon.network/ipfs/<hash>
(If applicable) https://ipfs.eth.aragon.network/ipfs/<hash>/artifact.json
(If applicable) https://ipfs.eth.aragon.network/ipfs/<hash>/manifest.json
Note that it is best practice to pin the content hash to an IPFS server you manage to ensure its future availability.
It's unlocked
Private network (Localhost 8545) is chosen
The first account provided by aragon run
or aragon devchain
is imported and selected. To import the account, copy the private key (something like a8a5...1563
), go to the Metamask accounts upper icon (to the left of the hamburguer button), scroll down, click on "Import account" and paste the value you copied.
Because of the way that Metamask caches the account nonces for the different networks, you may be getting the following error when interacting with your app:
The workaround is to switch to a different network (e.g. Rinkeby) and then switch back to the Localhost 8545 network. This will refresh Metamask's account nonce cache. Sending transactions should now succeed.
If you have problems during the instalation of aragonCLI or any other dependencies. You probably need to install or similar package.
Again, if you're having trouble fixing things, please reach out to us in our on the Discord Server.
You might need to have installed. If you're unsure what Git is, or whether you have it installed, we recommend you follow
After upgrading aragonCLI, or if unexpected errors are being experienced, (by doing aragon devchain --reset
or aragon run --reset
) is sometimes useful as it will restart the chain from the snapshot.
The aragonCLI creates the .aragon
directory under the user directory where it saves the state of the devchain and the
For example voting@1.1.5
. We can check the information for that deployment in the . Be sure to look in the environment you are working (eg. rinkeby).
You can check the commitHash
in aragon-apps GitHub repo and view the smart contract code that was deployed for that specific version. For v1.1.5
this is the .
Downloading our and running npm run pin
to load all of the previous deployments into your local ipfs daemon (this is a lot of data though; ~2gb right now). Alternatively you can decompress the archive you need and then just pin that.
The best way to propagate and keep your app's content accessible is to pin it via a cloud IPFS-pinning service like or . These services generally offer a generous free-tier that will allow you to host your app if it is not too large.
for additional gateways if you are having trouble with propagating.
To interact with your organization using you must make sure that: