Author

Topic: Problem on getting peers (Read 1331 times)

sr. member
Activity: 812
Merit: 256
October 13, 2015, 10:49:33 AM
#7
Can you post the Debug.log?

Also check your firewalls that they are allowing port 8333 both in and out.

I have solved my problem.

The peer was compiled with the CURRENT_VERSION=1 but the wallet was compiled with the CURRENT_VERSION=6...

Thanks for all
staff
Activity: 3458
Merit: 6793
Just writing some code
October 12, 2015, 06:54:59 AM
#6
Can you post the Debug.log?

Also check your firewalls that they are allowing port 8333 both in and out.
sr. member
Activity: 812
Merit: 256
October 12, 2015, 06:39:59 AM
#5
Hi! Could be a bit more specific here on how the nodes are behaving to this? Usually the bans are generated or called by default if there an activity triggered which does not have any error handling mechanism.So if your nodes are trying to inject an unauthorized piece of code which tries to modify the sockets the activity is dropped right away which is good I suppose .However if you could elaborate a bit more on the issues or check with your nodes you could debug this . Smiley

I tried several handling but the problem persists, I reinstall everything but nothing changed. I am trying to pull my hair. What detail should allow you to help me ...  Roll Eyes Roll Eyes (I know you think....fuck the noob!).
sr. member
Activity: 812
Merit: 256
October 12, 2015, 06:30:17 AM
#4
It looks like your node thinks its peers are misbehaving so it bans them. Have you tried restarting your node and connecting specifically to other nodes?

Yes, I have restart the node i have connect the node to other nodes but the problem is not solved.  Undecided
legendary
Activity: 1988
Merit: 1317
Get your game girl
October 09, 2015, 09:06:04 AM
#3
Hi! Could be a bit more specific here on how the nodes are behaving to this? Usually the bans are generated or called by default if there an activity triggered which does not have any error handling mechanism.So if your nodes are trying to inject an unauthorized piece of code which tries to modify the sockets the activity is dropped right away which is good I suppose .However if you could elaborate a bit more on the issues or check with your nodes you could debug this . Smiley
staff
Activity: 3458
Merit: 6793
Just writing some code
October 08, 2015, 06:32:36 AM
#2
It looks like your node thinks its peers are misbehaving so it bans them. Have you tried restarting your node and connecting specifically to other nodes?
sr. member
Activity: 812
Merit: 256
October 08, 2015, 12:56:54 AM
#1
I can connect a wallet to the peer, my log return:

-log wallet:

send version message: version bla bla bla bla bla..
socket closed
disconnecting node ***.***.***


-log peer:

connection from ***.***.*** dropped (banned)
connection from ***.***.*** dropped (banned)
connection from ***.***.*** dropped (banned)
connection from ***.***.*** dropped (banned)

in peer log all IP are banned

have you an idea?

Thanks

Gabrielle
Jump to: