Testnet V1 Sachiel
Search…
Testnet V1 Sachiel
Getting Started
Prepare your system
Run your own Humanode
Interact with the Humanode testnet
Troubleshooting
Powered By GitBook
Troubleshooting
Any errors you may get, what they mean, and how to solve them.

Getting help

Please read through this guide first and try to find a solution to your issue. If what you've stumbled upon is not on the list - you are welcome at our discord, where we'll do our best to help!

Windows

Please, make sure that you use WSL 2 as Windows binaries are currently not supported.

macOS

Please, make sure that you have followed prepare your system guide.

<unknown> in polkadot.js web app

If you stumble upon an <uknown> while exploring the blockchain state or interacting with extrinsic in the polkadot.js app, it is most likely due to the absence of the metadata in the polkadot.js settings.
To enable the metadata, use the links from the network explorer section.
They have metadata encoded as part of the URLs, so it'll automatically be available when you open the polkadot.js app.

Idle (0 peers)

If you have console output like this:
2021-03-10 18:32:21 💤 Idle (0 peers), best: #0 (0x9d07…7cce), finalized #0 (0x9d07…7cce), ⬇ 0 ⬆ 0
2021-03-10 18:32:26 💤 Idle (0 peers), best: #0 (0x9d07…7cce), finalized #0 (0x9d07…7cce), ⬇ 0 ⬆ 0
Then make sure:
  • that your system time is properly configured;
  • if you're using Windows operating system, make sure to run the peer under WSL 2.

Thread 'tokio-runtime-worker' panicked at 'The list of public keys is larger than 1;

The output looks like:
====================
​
Version: 0
​
0: sp_panic_handler::set::{{closure}}
1: std::panicking::rust_panic_with_hook
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:626:17
2: std::panicking::begin_panic::{{closure}}
3: std::sys_common::backtrace::__rust_end_short_backtrace
4: std::panicking::begin_panic
5: humanode_peer::service::new_full::{{closure}}::{{closure}}
6: <sc_service::task_manager::prometheus_future::PrometheusFuture<T> as core::future::future::Future>::poll
7: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
8: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
9: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
10: std::thread::local::LocalKey<T>::with
11: futures_executor::local_pool::block_on
12: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
13: tokio::runtime::task::harness::Harness<T,S>::poll
14: std::sys_common::backtrace::__rust_begin_short_backtrace
15: core::ops::function::FnOnce::call_once{{vtable.shim}}
16: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/sys/unix/thread.rs:71:17
17: start_thread
at ./nptl/./nptl/pthread_create.c:463:8
18: clone
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
​
​
Thread 'tokio-runtime-worker' panicked at 'The list of public keys is larger than 1; please report this', crates/humanode-peer/src/validator_key.rs:72
​
This is a bug. Please report it at:
​
https://github.com/humanode-network/humanode/issues/new
It means that during configuring your peer and performing keys management you have inserted more than 1 key.
So, we should remove current keystore:
  • Linux-based
    rm -r "$HOME/.local/share/humanode-peer/chains/huamnode_testnet1/keystore"
  • macOS
    rm -r "$HOME/Library/Application Support/humanode-peer/chains/huamnode_testnet1/keystore"
Then insert the key you want to use by executing the command in the same way as we did during keys management process:
humanode-peer key insert --key-type aura --suri "$SECRET_PHRASE" --chain chainspec.json
Where:
  • --key-type aura - key type that is used in Humanode testnet.
  • --suri "$SECRET_PHRASE" - your secret phrase (i.e. mnemonic).
  • --chain chainspec.json - path to the Humanode testnet chain specification file.
Make sure that you have inserted only 1 key.
Now you can run your node.

Thread 'tokio-runtime-worker' panicked at 'enroll failed: server error: unknown error: Unhandled rejection: FaceScanRejected';

The output looks like:
====================
​
Version: 0
​
0: sp_panic_handler::set::{{closure}}
1: std::panicking::rust_panic_with_hook
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:626:17
2: std::panicking::begin_panic_handler::{{closure}}
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:519:13
3: std::sys_common::backtrace::__rust_end_short_backtrace
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/sys_common/backtrace.rs:141:18
4: rust_begin_unwind
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:515:5
5: core::panicking::panic_fmt
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/core/src/panicking.rs:92:14
6: core::result::unwrap_failed
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/core/src/result.rs:1355:5
7: humanode_peer::service::new_full::{{closure}}::{{closure}}
8: <sc_service::task_manager::prometheus_future::PrometheusFuture<T> as core::future::future::Future>::poll
9: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
11: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
12: std::thread::local::LocalKey<T>::with
13: futures_executor::local_pool::block_on
14: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
15: tokio::runtime::task::harness::Harness<T,S>::poll
16: std::sys_common::backtrace::__rust_begin_short_backtrace
17: core::ops::function::FnOnce::call_once{{vtable.shim}}
18: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/sys/unix/thread.rs:71:17
19: start_thread
at ./nptl/./nptl/pthread_create.c:463:8
20: clone
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
​
​
Thread 'tokio-runtime-worker' panicked at 'enroll failed: server error: unknown error: Unhandled rejection: FaceScanRejected', crates/humanode-peer/src/service.rs:406
​
This is a bug. Please report it at:
​
https://github.com/humanode-network/humanode/issues/new
This error means that your Face Scan was rejected. We know that in the Web App you get it as successful (we will fix this in future releases).
To fix it for most of the time you need to make another scan. You can use the same QR code once again or press "Capture Again" on the Web App UI. Or use a link under the QR code to scan your face using your laptop.
For this to be successful, you need:
  1. 1.
    Good lighting in the room so that your face is clearly visible;
  2. 2.
    A clean camera, try to polish it before scanning.
If you tried a couple of times and are still unsuccessful, try to change the scanning device. Most of the time, it helps.
If you tried all the above-mentioned steps and still have this error, please reach out to our team through the #troubleshooting chat in the HUMANODE Discord.

Failed to fetch, Origin is not allowed by Access-Control-Allow-Origin.

The error happens during opening required URL on your device to pass bioauthentication.
There are 2 possible root causes:
  • You run your humanode-peer locally but something is wrong with ngrok. Please, make sure that ngrok is still running and you use the same url in option --rpc-url "$RPC_URL". Sometimes you need just to restart ngrok and update --rpc-url.\
  • You run your machine in remote way using a cloud provider. If you don't use ngrok then you need to have a properly configured reverse proxy server on your machine, your own domain and TLS certificate as well. By the way, we suggest you to use ngrok to make running humanode-peer more easy at cloud provider. But make sure that you run ngrok and humanode-peer on the same system.

Result::unwrap() on an Err value: Pool(InvalidTransaction(InvalidTransaction::Custom(99)))'

The output looks like:
====================
​
Version: 0
​
0: backtrace::backtrace::trace
1: backtrace::capture::Backtrace::new
2: sp_panic_handler::set::{{closure}}
3: std::panicking::rust_panic_with_hook
4: std::panicking::begin_panic_handler::{{closure}}
5: std::sys_common::backtrace::__rust_end_short_backtrace
6: _rust_begin_unwind
7: core::panicking::panic_fmt
8: core::result::unwrap_failed
9: humanode_peer::service::new_full::{{closure}}::{{closure}}
10: <sc_service::task_manager::prometheus_future::PrometheusFuture<T> as core::future::future::Future>::poll
11: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
13: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
14: std::thread::local::LocalKey<T>::with
15: futures_executor::local_pool::block_on
16: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
17: tokio::runtime::task::harness::Harness<T,S>::poll
18: std::sys_common::backtrace::__rust_begin_short_backtrace
19: core::ops::function::FnOnce::call_once{{vtable.shim}}
20: std::sys::unix::thread::Thread::new::thread_start
21: __pthread_start
​
​
Thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Pool(InvalidTransaction(InvalidTransaction::Custom(99)))', crates/humanode-peer/src/service.rs:455
​
This is a bug. Please report it at:
​
https://github.com/humanode-network/humanode/issues/new
It means that you've already authorized in Humanode network and your authentication is still valid.
You need just to rerun humanode-peer without --bioauth-enroll option:
$ humanode-peer --name "$NAME" --validator --chain chainspec.json --rpc-url "$RPC_URL" --rpc-cors all
Previous
Interact with the Humanode testnet
Last modified 11mo ago
Copy link
On this page
Getting help
Windows
macOS
<unknown> in polkadot.js web app
Idle (0 peers)
Thread 'tokio-runtime-worker' panicked at 'The list of public keys is larger than 1;
Thread 'tokio-runtime-worker' panicked at 'enroll failed: server error: unknown error: Unhandled rejection: FaceScanRejected';
Failed to fetch, Origin is not allowed by Access-Control-Allow-Origin.
Result::unwrap() on an Err value: Pool(InvalidTransaction(InvalidTransaction::Custom(99)))'