It was created about 7 days ago and I received a reward once, but when I checked the Platform Balance on https://mnowatch.org/evonodes/, it was 0.
It was created about 7 days ago and I received a reward once, but when I checked the Platform Balance on https://mnowatch.org/evonodes/, it was 0.
If you do these commands, what do you see ?It was created about 7 days ago and I received a reward once, but when I checked the Platform Balance on https://mnowatch.org/evonodes/, it was 0.
Check your Evonode here : https://mnowatch.org/evonodes/ (scroll down until you reached section 'All Evonodes' and do ctrl+F and search on your ip address or protx hash). Verify the following :i search protx on platform-explorer.com/validator , but show There are no blocks created yet.
All services on the server are green and running well.
I asked @pshenmic to help you out.On the website, everything is normal except Platform Epoch :0
Service │ Container ID │ Image │ Status ║
║ Dashmate Helper │ 00a4418421cf │ dashpay/dashmate-helper:1.2.0 │ running ║
║ Core │ 1bd2f827ecab │ dashpay/dashd:21 │ running ║
║ Drive ABCI │ 3bfde55e259a │ dashpay/drive:1 │ running ║
║ Drive Tenderdash │ 25af6e41d443 │ dashpay/tenderdash:1 │ running ║
║ DAPI API │ f409ddd5cf67 │ dashpay/dapi:1 │ running ║
║ DAPI Transactions Filter Stream │ 3d1f19c32d9b │ dashpay/dapi:1 │ running ║
║ Gateway │ 23d9fa4f46c4 │ dashpay/envoy:1.30.2-impr.1 │ running ║
║ Gateway rate limiter │ 6fba9d4397ca │ envoyproxy/ratelimit:3fcc3609 │ running ║
║ Gateway rate limiter storage │ 39df69d2c90f │ redis:alpine │ running ║
maybe you are out of sync? what is your node's platform block height? could you post more status outputs?On the website, everything is normal except Platform Epoch :0
Service │ Container ID │ Image │ Status ║
║ Dashmate Helper │ 00a4418421cf │ dashpay/dashmate-helper:1.2.0 │ running ║
║ Core │ 1bd2f827ecab │ dashpay/dashd:21 │ running ║
║ Drive ABCI │ 3bfde55e259a │ dashpay/drive:1 │ running ║
║ Drive Tenderdash │ 25af6e41d443 │ dashpay/tenderdash:1 │ running ║
║ DAPI API │ f409ddd5cf67 │ dashpay/dapi:1 │ running ║
║ DAPI Transactions Filter Stream │ 3d1f19c32d9b │ dashpay/dapi:1 │ running ║
║ Gateway │ 23d9fa4f46c4 │ dashpay/envoy:1.30.2-impr.1 │ running ║
║ Gateway rate limiter │ 6fba9d4397ca │ envoyproxy/ratelimit:3fcc3609 │ running ║
║ Gateway rate limiter storage │ 39df69d2c90f │ redis:alpine │ running ║
should port 26656 be available immediately after running dashmate? or only after kernel sync?
I tried to run a second service on this vps through this port and everything works... but when dashmate is running, the port is closed
Check if your VPS has IPv6 enabled, that could cause false reporting of close ports like 26656 in Dashmate. Check if your Evonode ip address with port 26656 is open through an online port checker. If your server has IPv6 enabled, you will need to disable it, to force all traffic to go through IPv4. Also make sure port 26656 is allowed in your ufw firewall (sudo ufw status), below ports (including port 80) should all be in there :
If sync is in progress, then that good. Wait for full sync.I had IPv6 turned off... I misunderstood you and turned it on... port 26656 is not available. But when IPv6 was turned off, the problem was the same... now synchronization is in progress and the port is not available...
dashmate status services (copy the container id of tenderdash)
docker logs containerIDofTenderdash
Anything in that log pointing to an ERROR ? or a FAULT ?
Just ignore closed port status of port 26656 in Dashmate, most likely it is just incorrect port status reporting from Dashmate.the port in the firewall is open. but not accessible from the outside. I tried to turn off dashmate and attach another service to this port and then the port is open. but when I started dashmate again it is closed again. yesterday the logs were like this:
node_key.json` ("/tenderdash/config/node_key.json: ERROR: failed to create node"),
tried it all...didn't work..Try these commands and see if that fix your problem with Tenderdash :
dashmate stop --platform
dashmate reset --platform
dashmate update
dashmate start --platform
1 : Wait for full sync (100%) !!!tried it all...didn't work..
now it's synchronizing at 25%, I'll wait until the end.
the platform may start and the port may open, but now it's closed.