# Unexpected argument error when trying to run testnet node

**URL:** <https://forum.fuel.network/t/unexpected-argument-error-when-trying-to-run-testnet-node/4911>\
**Category:** General\
**Tags:** testnet, tutorials\
**Created:** [March 21, 2024, 5:42pm UTC](https://forum.fuel.network/t/unexpected-argument-error-when-trying-to-run-testnet-node/4911 "2024-03-21T17:42:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elephantlasers](https://avatars.discourse-cdn.com/v4/letter/e/ed8c4c/32.png) [@elephantlasers](https://forum.fuel.network/u/elephantlasers)\
**Post date:** [March 21, 2024, 5:42pm UTC](https://forum.fuel.network/t/unexpected-argument-error-when-trying-to-run-testnet-node/4911/1 "2024-03-21T17:42:49Z")

</div>

I am trying to run a testnet node. I have the below from the docs page on running a local node. For service name, I put in whatever I want. For keypair, I enter my secret key string. For relayer, I put in the https address from Alchemy. I leave everything else as is and run it. The message is “error: unexpected argument ‘0.0.0.0’ found”. Any clue as to what this means?

Many thanks,  
Kyle

fuel-core run   
–service-name {ANY\_SERVICE\_NAME}   
–keypair {P2P\_SECRET}   
–relayer {ETH\_RPC\_ENDPOINT}  
–ip 0.0.0.0 --port 4000 --peering-port 30333   
–db-path ~/.fuel\_beta5   
–chain ./chainConfig.json   
–utxo-validation --poa-instant false --enable-p2p   
–min-gas-price 1 --max-block-size 18874368 --max-transmit-size 18874368   
–reserved-nodes /dns4/p2p-beta-5.fuel.network/tcp/30333/p2p/16Uiu2HAmSMqLSibvGCvg8EFLrpnmrXw1GZ2ADX3U2c9ttQSvFtZX,/dns4/p2p-beta-5.fuel.network/tcp/30334/p2p/16Uiu2HAmVUHZ3Yimoh4fBbFqAb3AC4QR1cyo8bUF4qyi8eiUjpVP   
–sync-header-batch-size 100   
–enable-relayer   
–relayer-v2-listening-contracts 0x557c5cE22F877d975C2cB13D0a961a182d740fD5   
–relayer-da-deploy-height 4867877   
–relayer-log-page-size 2000

fuelup show  
root@vmi1745537:~# fuelup show  
Default host: x86\_64-unknown-linux-gnu  
fuelup home: /root/.fuelup

## installed toolchains

latest-x86\_64-unknown-linux-gnu (default)

## active toolchain

latest-x86\_64-unknown-linux-gnu (default)  
forc : 0.49.3  
- forc-client  
- forc-deploy : 0.49.3  
- forc-run : 0.49.3  
- forc-crypto : 0.49.3  
- forc-doc : 0.49.3  
- forc-explore : 0.28.1  
- forc-fmt : 0.49.3  
- forc-lsp : 0.49.3  
- forc-tx : 0.49.3  
- forc-wallet : 0.4.3  
fuel-core : 0.22.1  
fuel-core-keygen : 0.22.1

## fuels versions

forc : 0.54.0  
forc-wallet : 0.54.0

Topic discussion checklist

- Run `$ fuelup show` and add the output below
- Detailed steps to recreate issue
- Link full scope of the codebase pertaining to your issue
- Any other relevant information

---

<div class="post-metadata">

**Author:** ![crypt0mate](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/crypt0mate/32/2445_2.png) [@crypt0mate](https://forum.fuel.network/u/crypt0mate)\
**Post date:** [March 22, 2024, 7:17am UTC](https://forum.fuel.network/t/unexpected-argument-error-when-trying-to-run-testnet-node/4911/2 "2024-03-22T07:17:25Z")

</div>

Hi @elephantlasers

can you try using the `beta-5` toolchain. here are steps to update: [Peering port error setting up node - #2 by crypt0mate](https://forum.fuel.network/t/peering-port-error-setting-up-node/4901/2)