Missing file error when using Substrate EVM template

I'm following the quick start at this link: https://docs.openzeppelin.com/substrate-runtimes/2.0.2/guides/quick_start.

Everything goes well until the point that I'll try to launch the first node, that will result in the following error:

Error: NetworkKeyNotFound("./data/alpha-node-1/chains/trrue_alpha/network/secret_ed25519")

Here is the command that I run:

./target/release/trcn \
    --alice \
    --collator \
    --force-authoring \
    --chain raw-alpha-parachain-chainspec.json \
    --base-path ./data/alpha-node-1 \
    --port 40333 \
    --rpc-port 8844 \
    -- \
    --execution wasm \
    --chain paseo.json \
    --port 30343 \
    --rpc-port 9977 \
    --sync fast-unsafe

The quick start doesn't mention anything about creating or placing keys. Also I tried to search for a solution, but that didn't help me. So I'm a bit confused about which key we're talking here and what I'm doing wrong.

The OpenZeppelin docs will need an update, but yeah, you cannot run a collator node without setting the keys.

You can use the flag from point 4 below as a work around and then use Polkadot JS UI to set the collator keys with an RPC call

Starting an authorithy without network key in ./sub0-reset/chains/live/network/secret_ed25519.

       This is not a safe operation because other authorities in the network may depend on your node having a stable identity.

       Otherwise these other authorities may not being able to reach you.

       If it is the first time running your node you could use one of the following methods:

       1. [Preferred] Separately generate the key with: <NODE_BINARY> key generate-node-key --base-path <YOUR_BASE_PATH>

       2. [Preferred] Separately generate the key with: <NODE_BINARY> key generate-node-key --file <YOUR_PATH_TO_NODE_KEY>

       3. [Preferred] Separately generate the key with: <NODE_BINARY> key generate-node-key --default-base-path

       4. [Unsafe] Pass --unsafe-force-node-key-generation and make sure you remove it for subsequent node restarts