Validator Stopped With Error ```Could not get seed list from seed node server, connect ENETUNREACH``` On TCP Port 4000

[Shekelme]

What is the issue?

My validator is stopping after a while with this error in dashboard:

Node exited with following message: Fatal: Could not get seed list from seed node server http://archiver-sphinx.shardeum.org:4000/nodelist: connect ENETUNREACH 3.127.57.166:4000

I have faced this problem twice already.

What impact does the issue have?

I can't run the validator 

How to reproduce the issue?

Simply start the validator in accordance with docs.shardeum.org, forwsrd the ports (9001 amd 10001) and wait for a while.

What other resources can you share regarding this issue?

[MarcusWentz]

It's possible the validator is not able to reach the archiver based on its current location.

Are you able to do a ping or trace route the archiver from that validator?

[Shekelme]

Yes.

[Shekelme]

[MarcusWentz]

It looks like most packets are transmitted.

A few questions:

Q1. Is your validator on a local computer or remote server?

Q2. What is your current tested bandwidth

https://www.google.com/search?client=firefox-b-1-lm&q=google+test+speed

?

Q3. Are you having other network issues?

[Shekelme]

A1. Local PC A2.

Testing download speed................................................................................ Download: 305.36 Mbit/s Testing upload speed...................................................................................................... Upload: 40.97 Mbit/s

A3. I didn't notice anything significant, other applications are working fine.

[MarcusWentz]

@ANiX5202

https://github.com/Shardeum/shardeum-bug-reporting/issues/54#issuecomment-1432072371

Please answer the following questions as well:

Q1. Is your validator on a local computer or remote server?

Q2. What is your current tested bandwidth

https://www.google.com/search?client=firefox-b-1-lm&q=google+test+speed

?

Q3. Are you having other network issues?

[ANiX5202]

@ANiX5202

#54 (comment)

Please answer the following questions as well:

Q1. Is your validator on a local computer or remote server?

Q2. What is your current tested bandwidth

https://www.google.com/search?client=firefox-b-1-lm&q=google+test+speed

?

Q3. Are you having other network issues?

A1. Remote server Ubuntu 20.04 A2. Node Name Upload Speed Download Speed Latency Speedtest.net 1989.05 Mbps 12111.80 Mbps 0.26 ms A3. I haven't

[MarcusWentz]

@Shekelme

Do you have logs when the validator goes from active to inactive in the CLI and GUI?

https://docs.shardeum.org/node/run/validator#step-6-monitor-validator

@ANiX5202

Were you able to run a validator in the past?

If so, was the remote server location the same when it was working before?

[Shekelme]

BTW my validator was working during Sphinx 1.0. Not sure how to watch the logs, but here is what it says in CLI:

node@8b031bec162e:~/app$ operator-cli status state: stopped exitMessage: 'Fatal: Node cannot join with invalid external IP: 0.0.0.0' exitStatus: Exit with error performance: memPercentage: 56.53958321089468 diskPercentage: 33.34332108101633 cpuPercentage: 2.3213194868662135 stakeRequirement: '10.0' lockedStake: '14.0' nominatorAddress: '0xf9055a98e7947d4000fe9a2ae30ae3e11b0bf58a'

And the same message is in GUI:

[chanderpalrathore]

Getting same error for me

[mihauman]

I have the same error

[Jensnicolaigustavsen]

alright my node is up and running!

[Jensnicolaigustavsen]

let me know if you have any problems

[mihauman]

let me know if you have any problems

ok thx

[Shekelme]

@Jensnicolaigustavsen What did you do to make your node work?

[MarcusWentz]

@Shekelme

Is port 4000 open on your system?

I heard someone opened this port and the network timeouts were fixed.

[Shekelme]

I have opened it today. Should I restart Shardeum validator somehow? Because I see it again: Node exited with following message: Fatal: Could not get seed list from seed node server http://archiver-sphinx.shardeum.org:4000/nodelist: connect ENETUNREACH 3.127.57.166:4000

[MarcusWentz]

Try this:

Go into the operator dashboard docker (may be different if you customized install location:

cd ~/.shardeum
./shell.sh

Get your node's external IP:

curl https://ipinfo.io/ip

The returned IP in the format of nnn.nnn.nnn.nnn is your EXTERNAL_IP.

Set the number above in place of EXTERNAL_IP:

export APP_IP="EXTERNAL_IP"

https://docs.shardeum.org/node/run/validator#step-9-stake-shm-to-validator

[Shekelme]

Done already. No positive effect...

[mihauman]

Shekelme You restarted the node after opening the port?

[mizovsky2304]

I have the same issue...

[Shekelme]

@mihauman Restarted the node via web GUI dashboard, and aftere a while I restarted the docker container. But again: I even opened the port 3001....

[mihauman]

Shekelme open port 4000 and 4001 and restart node

[Shekelme]

@mihauman No effect, still the same error. But this time, it seems, the node worked for several hours...

[MarcusWentz]

You can open port 4000 in Linux with:

sudo ufw allow 4000

https://www.digitalocean.com/community/tutorials/opening-a-port-on-linux

[Shekelme]

I can't, since my ufw is always inactive.

[tbros6868]

How to open ports 4000 and 4001 and then restart the validator:

sudo apt install ufw
sudo ufw allow 4000
sudo ufw allow 4001
ufw allow ssh
ufw allow 8080
ufw allow https
ufw allow http
ufw allow 443
ufw enable
sudo ufw reload
sudo ufw status

[Shekelme]

I like this project so much. OK, will try to run it on separate PC.

[ShriyanshShukla]

Not working, getting the same error

[MarcusWentz]

@Shekelme

We are looking into the archive node to see what might be causing this.

[mizovsky2304]

Same issue here... I think the devs had a lot of work the last three days... 1- public key address 2- seed list: port 4000 problem 3- today: _getSeedNodes

[xkemox]

All ports are open still got the same error.. Anyone manage to fix it?

[Jensnicolaigustavsen]

im also getting this error:

[Jongjh]

Im facing the same issue - Node exited with following message: Fatal: Could not get seed list from seed node server http://archiver-sphinx.shardeum.org:4000/nodelist: Timeout awaiting 'request' for 5000ms

[anaderiasoft]

Im facing the same issue - Node exited with following message: Fatal: Could not get seed list from seed node server http://archiver-sphinx.shardeum.org:4000/nodelist: Timeout awaiting 'request' for 5000ms

yes same "ufw allow 4000" doesnt give any result

[ostd6212]

Similar issue

[zodiac55]

Node exited with following message: Cannot read properties of undefined (reading 'id')

What can be a problem?

[mihauman]

Who had a port 4000 error in shardeum

1. sudo nano /etc/ufw/before.rules add next row before COMMIT row
2. -A ufw-before-input -p tcp --dport 4000 -j ACCEPT
3. Save the files and close the file.
4. sudo ufw reload

[Shekelme]

@mihauman But what if ufw is simply disabled?

[ostd6212]

![Uploading Screenshot 2023-02-20 at 11.28.59.png…]()

[mihauman]

Shekelme 1)sudo ufw status 2)sudo ufw enable 3)sudo nano /etc/ufw/before.rules 4)add next row before COMMIT row: -A ufw-before-input -p tcp --dport 4000 -j ACCEPT 5)-A ufw-before-input -p tcp --dport 4000 -j ACCEPT 6)sudo ufw reload

[MarcusWentz]

It sounds like we have a potential bug fix for this with the latest validator update.

Update your validator with:

curl -O https://gitlab.com/shardeum/validator/dashboard/-/raw/main/installer.sh && chmod +x installer.sh && ./installer.sh

https://docs.shardeum.org/node/run/validator#step-2-download-and-install-validator

Does this error still occur after the latest validator update?

[Shekelme]

@MarcusWentz Unfortunately yes, still the same error:

[ehenry-50]

I am having the same error-Node exited with following message: Fatal: Could not get seed list from seed node server http://archiver-sphinx.shardeum.org:4000/nodelist: Timeout awaiting 'request' for 5000ms

[scorpion141]

I have the Same Error.

Ports are open:

[Shekelme]

@scorpion141 It seems that you forgot 9001 and 10001.

[scorpion141]

@Shekelme thank you very mutch.

i opend the Porta now but i get a Link in the Discord to test the IP and the Port and it says closed to me. Maybe its a Problem with the VPS.

https://www.yougetsignal.com/tools/open-ports/

[scorpion141]

Ok i think that is not correct the Page said Port 8080 is closed but i can connect on the Webpage.

[scorpion141]

@Shekelme got the Same Error with the New Ports opend.

Iam also Try this without a Firewall and i ask the Service Provider if they Blocked Ports but no.

[MarcusWentz]

Please update your validator to version 1.1.1.

Here's what you need to do:

1. Stop and unstake your validator.
2. If you're within the Validator CLI:

exit

then:

cd ..

3. Enter:

curl -O https://gitlab.com/shardeum/validator/dashboard/-/raw/main/installer.sh && chmod +x installer.sh && ./installer.sh

4. Start the validator.
5. Stake 10 SHM.