telnet Producer_IP 6000
telnet: could not resolve Producer_IP/6000: Temporary failure in name resolution
:~/cardano-my-node$ telnet x.x.x.x 6000
It’s saying connected?
No its not able to connect
See meaning ur port in Producer is closed
Okay opening them on AWS
Okay the telnet command works now 
Uptime: 00:20:57 │ Port: 6000 │ Guild LiveView v1.19.4 │
│------------------------└────────────┴────────────────────────┤
│ Epoch 250 [0.5%] (node) │
│ 4d 23:25:12 until epoch boundary (chain) │
│ ▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
│ │
│ Block : 5385832 Tip (ref) : 22638888 │
│ Slot : 2033 Tip (node) : 22638833 │
│ Density : 4.878 Tip (diff) : 55 
│
│--------------------------------------------------------------│
│ Processed TX : 0 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 2 4 │
├──────────────────────────────────────────────────────────────┤
│ KES current/remaining : 174 / 61 │
│ KES expiration date : 2021-05-26 09:44:51 UTC │
│--------------------------------------------------------------│
│ BLOCKS Leader | Adopted | Invalid │
│Since node start (EKG metrics) 0 | 0 | 0 │
└──────────────────────────────────────────────────────────────┘
TG Announcement/Support channel: t.me/guild_operators_official
[esc/q] Quit | [i] Info | [p] Peer Analysis
ok, you should see your relay on IN on Producer if not restart the Producer node
1 Like
thanks, i see them both !
1 Like
then open the port 6000 in AWS also for last relay
I opened 6000 for both Relay 1 and Relay 2 on my block producer.
6000 was opened on Relay 1 and 2 on AWS already
1 Like
Should I try to run the updater again?
I can’t run more then once/hour
Did u added in crontab right?
{ “resultcode”: “204”, “datetime”:“2021-02-24 22:47:57”, “clientIp”: “x.x.x.x”, “iptype”: 4, “msg”: “glad you’re staying with us” }
I did try to use the crontab, but i think it gave me a error.
U should solve the crontab issue otherwise after 3 hours the node will be declared offline
On relaynode1
cat > NODE_HOME/crontab-fragment.txt << EOF
22 * * * * {NODE_HOME}/topologyUpdater.sh
EOF
crontab -l | cat - crontab-fragment.txt >crontab.txt && crontab crontab.txt
rm crontab-fragment.txt
crontab -l | cat - crontab-fragment.txt >crontab.txt && crontab crontab.txt
:~/cardano-my-node$ rm crontab-fragment.txt
:~/cardano-my-node$
it doesnt do anything, i think it added it
rm = remove… with that command u removed the file
im just copying from coincashew
On relaynode1
cat > $NODE_HOME/crontab-fragment.txt << EOF
22 * * * * ${NODE_HOME}/topologyUpdater.sh
EOF
crontab -l | cat - crontab-fragment.txt >crontab.txt && crontab crontab.txt
rm crontab-fragment.txt
Node is up! thanks for the help for everything!~
Tomorrow I setup monitoring, figure out pledge more and do everything else that I need.
1 Like
@Alexd1985 - hi Alex
I am also facing the same issue. Can you please help me. Using version 1.25.1
https://pool.vet/#EEL
I have gone through all the post related this error. But still not able to resolve.
I have my servers on AWS. I am getting this error for topology updater. I updated my topology updater from coin cashew. (Guide: How to build a Cardano Stake Pool - CoinCashew)
{ “resultcode”: “403”, “datetime”:“2021-05-28 07:33:42”, “clientIp”: “54.221.127.96”, “iptype”: 4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” }
Both nodes are reachable from outside.