Full_node full_node_server : INFO Cannot connect to host 76.9.87.149:8444 ssl:<ssl.SSLContext object at 0x000002496B6F87C0>

Hello,

In the log file of the full node sometimes I have these errors:

INFO     Cannot connect to host 76.9.87.149:8444 ssl:<ssl.SSLContext object at 0x000002496B6F87C0>
Cannot connect to host 31.223.49.170:8444 ssl:<ssl.SSLContext object at 0x0000024912030640>
Cannot connect to host 62.220.56.2:8444 ssl:<ssl.SSLContext object at 0x00000249110F7B40>

In my full node connections, I don’t see these IP addresses.
When I check the port 8444 for these IPs ( Open Port Check Tool - Test Port Forwarding on Your Router (yougetsignal.com)), I see that they have port 8444 closed.

I wanted to remove these IPs from my full node connections, but I don’t see them.

Could someone tell me if there is a way to show all peer connections from the CLI? How can I disconnect from these peers that have their port 8444 closed? I don’t know why I am having these kind of messages in the log.

Please help me to understand and take actions. I am full synced from full node in wallet, but I am worry about these peer connections.

Hello,

Does someone has these kind of messages I reported in his log?

thanks

Yes, I’ve seen similar yesterday iirc.

This is a standard message that is displayed after a peer has dropped.

Most peers are just other peeps like you. Peers are dropped frequently and new ones acquired.

When your machine cannot find a peer it had it delivers the “Cannot connect to host” message and goes on to find another peer.

These info messages are totally normal, not errors and it are not related to a closed port 8444.

You can demonstrate this by noting a peers address, deleting them, and then checking your log. You will find the message in the log with the same address.