Testnet
Search…
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:
1
2021-03-10 18:32:21 πŸ’€ Idle (0 peers), best: #0 (0x9d07…7cce), finalized #0 (0x9d07…7cce), ⬇ 0 ⬆ 0
2
2021-03-10 18:32:26 πŸ’€ Idle (0 peers), best: #0 (0x9d07…7cce), finalized #0 (0x9d07…7cce), ⬇ 0 ⬆ 0
Copied!
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:
1
====================
2
​
3
Version: 0
4
​
5
0: sp_panic_handler::set::{{closure}}
6
1: std::panicking::rust_panic_with_hook
7
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:626:17
8
2: std::panicking::begin_panic::{{closure}}
9
3: std::sys_common::backtrace::__rust_end_short_backtrace
10
4: std::panicking::begin_panic
11
5: humanode_peer::service::new_full::{{closure}}::{{closure}}
12
6: <sc_service::task_manager::prometheus_future::PrometheusFuture<T> as core::future::future::Future>::poll
13
7: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
14
8: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
15
9: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
16
10: std::thread::local::LocalKey<T>::with
17
11: futures_executor::local_pool::block_on
18
12: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
19
13: tokio::runtime::task::harness::Harness<T,S>::poll
20
14: std::sys_common::backtrace::__rust_begin_short_backtrace
21
15: core::ops::function::FnOnce::call_once{{vtable.shim}}
22
16: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
23
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
24
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
25
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
26
std::sys::unix::thread::Thread::new::thread_start
27
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/sys/unix/thread.rs:71:17
28
17: start_thread
29
at ./nptl/./nptl/pthread_create.c:463:8
30
18: clone
31
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
32
​
33
​
34
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
35
​
36
This is a bug. Please report it at:
37
​
38
https://github.com/humanode-network/humanode/issues/new
Copied!
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
    1
    rm -r "$HOME/.local/share/humanode-peer/chains/huamnode_testnet1/keystore"
    Copied!
    macOS
    1
    rm -r "$HOME/Library/Application Support/humanode-peer/chains/huamnode_testnet1/keystore"
    Copied!
Then insert the key you want to use by executing the command in the same way as we did during keys management process:
1
humanode-peer key insert --key-type aura --suri "$SECRET_PHRASE" --chain chainspec.json
Copied!
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:
1
====================
2
​
3
Version: 0
4
​
5
0: sp_panic_handler::set::{{closure}}
6
1: std::panicking::rust_panic_with_hook
7
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:626:17
8
2: std::panicking::begin_panic_handler::{{closure}}
9
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:519:13
10
3: std::sys_common::backtrace::__rust_end_short_backtrace
11
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/sys_common/backtrace.rs:141:18
12
4: rust_begin_unwind
13
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/panicking.rs:515:5
14
5: core::panicking::panic_fmt
15
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/core/src/panicking.rs:92:14
16
6: core::result::unwrap_failed
17
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/core/src/result.rs:1355:5
18
7: humanode_peer::service::new_full::{{closure}}::{{closure}}
19
8: <sc_service::task_manager::prometheus_future::PrometheusFuture<T> as core::future::future::Future>::poll
20
9: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
21
10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
22
11: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
23
12: std::thread::local::LocalKey<T>::with
24
13: futures_executor::local_pool::block_on
25
14: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
26
15: tokio::runtime::task::harness::Harness<T,S>::poll
27
16: std::sys_common::backtrace::__rust_begin_short_backtrace
28
17: core::ops::function::FnOnce::call_once{{vtable.shim}}
29
18: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
30
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
31
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
32
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/alloc/src/boxed.rs:1575:9
33
std::sys::unix::thread::Thread::new::thread_start
34
at /rustc/150fad30ea25e812d481a784d02c95d3394b234b/library/std/src/sys/unix/thread.rs:71:17
35
19: start_thread
36
at ./nptl/./nptl/pthread_create.c:463:8
37
20: clone
38
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
39
​
40
​
41
Thread 'tokio-runtime-worker' panicked at 'enroll failed: server error: unknown error: Unhandled rejection: FaceScanRejected', crates/humanode-peer/src/service.rs:406
42
​
43
This is a bug. Please report it at:
44
​
45
https://github.com/humanode-network/humanode/issues/new
Copied!
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.
    Good lighting in the room so that your face is clearly visible;
    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:
1
====================
2
​
3
Version: 0
4
​
5
0: backtrace::backtrace::trace
6
1: backtrace::capture::Backtrace::new
7
2: sp_panic_handler::set::{{closure}}
8
3: std::panicking::rust_panic_with_hook
9
4: std::panicking::begin_panic_handler::{{closure}}
10
5: std::sys_common::backtrace::__rust_end_short_backtrace
11
6: _rust_begin_unwind
12
7: core::panicking::panic_fmt
13
8: core::result::unwrap_failed
14
9: humanode_peer::service::new_full::{{closure}}::{{closure}}
15
10: <sc_service::task_manager::prometheus_future::PrometheusFuture<T> as core::future::future::Future>::poll
16
11: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
17
12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
18
13: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
19
14: std::thread::local::LocalKey<T>::with
20
15: futures_executor::local_pool::block_on
21
16: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
22
17: tokio::runtime::task::harness::Harness<T,S>::poll
23
18: std::sys_common::backtrace::__rust_begin_short_backtrace
24
19: core::ops::function::FnOnce::call_once{{vtable.shim}}
25
20: std::sys::unix::thread::Thread::new::thread_start
26
21: __pthread_start
27
​
28
​
29
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
30
​
31
This is a bug. Please report it at:
32
​
33
https://github.com/humanode-network/humanode/issues/new
Copied!
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:
1
$ humanode-peer --name "$NAME" --validator --chain chainspec.json --rpc-url "$RPC_URL" --rpc-cors all
Copied!
Last modified 5d ago