Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 5036. (Read 9723858 times)

Quote from: GhostPlayer on June 27, 2014, 04:54:31 AM

"Unable fo bind to 0.0.0.0.9999" when launching Undecided

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error. Any solution ?

Refer back to that link. I just gave a shot at a fix

Thanks !
Best community - 10 seconds to wait for a top anwser, 24/24 :-)

That is the "dirty" fix !! Check out chaeplin's answer a few posts back. Much more elegant and secure.

Spratan

hero member

Activity: 689

Merit: 507

Quote from: chaeplin on June 27, 2014, 04:48:52 AM

"Unable fo bind to 0.0.0.0.9999" when launching Undecided

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error. Any solution ?

Refer back to that link. I just gave a shot at a fix

Thanks !
Best community - 10 seconds to wait for a top anwser, 24/24 :-)

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: TanteStefana2 on June 27, 2014, 04:32:17 AM

Quote from: chaeplin on June 27, 2014, 04:29:38 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

I don't think so.

Banned by peered clients.

So we could be banned, which lasts 24 hours, and have no way of knowing it? Geepers! I doubt this is an offence that happens often, but it should be viewable somewhere. I scanned my debug logs for "ban" and didn't get anything, so hopefully I haven't been banned for anything, LOL

If anyhow NM is banned(ip or pubkey..), ping of NM will not be not relayed.
So if a NM is green on the list at least 2 hours, I think the NM is ok.

http://drk.poolhash.org/masternode.html
https://elbzo.net/masternodes.html

Bugger, I just changed all my privkeys but probably didn't need to. All green on your lists. Will wait impatiently for that 1st payment... Wink

chaeplin

sr. member

Activity: 294

Merit: 250

"Unable fo bind to 0.0.0.0.9999" when launching Undecided

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error. Any solution ?

I had that error once in linux with multiple interface and aliased ip.

If port 9999 is not used by other applications, please try this.

make darkcoin.conf with options

Code:

bind=change_this_to_internal_interface_ip_public_or_private
bind=127.0.0.1
rpcport=9998
port=9999

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Quote from: TanteStefana2 on June 27, 2014, 04:32:17 AM

"Unable fo bind to 0.0.0.0.9999" when launching Undecided

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error. Any solution ?

Refer back to that link. I just gave a shot at a fix

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: chaeplin on June 27, 2014, 04:29:38 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Quote from: Macno on June 27, 2014, 04:43:24 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

I don't think so.

Banned by peered clients.

So we could be banned, which lasts 24 hours, and have no way of knowing it? Geepers! I doubt this is an offence that happens often, but it should be viewable somewhere. I scanned my debug logs for "ban" and didn't get anything, so hopefully I haven't been banned for anything, LOL

If anyhow NM is banned(ip or pubkey..), ping of NM will not be relayed.
So if a NM is green on the list at least 2 hours, I think the NM is ok.

http://drk.poolhash.org/masternode.html
https://elbzo.net/masternodes.html

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Great to see the MN payments working.
What does it take now for Darkmarkets to actually use DRK? The Darksend 10 DRK limit has to be lifted, right?

That, but also good amounts of PR to get the word out.

Spratan

hero member

Activity: 689

Merit: 507

"Unable fo bind to 0.0.0.0.9999" when launching Undecided

Same problem as here, remains unsanswered : https://darkcointalk.org/threads/unable-to-bind-9999.677/

I can't launch the wallet, and no other coin on google mentionning this error. Any solution ?

Macno

legendary

Activity: 984

Merit: 1000

Great to see the MN payments working.
What does it take now for Darkmarkets to actually use DRK? The Darksend 10 DRK limit has to be lifted, right?

Aswan

legendary

Activity: 1734

Merit: 1015

Quote from: AngusCanine on June 26, 2014, 09:16:22 PM

Quote from: franz2 on June 26, 2014, 07:33:57 PM

ich habe einen Test mit 3 clients gleichzeitig und darksend gemacht:

funktoniert einwandfrei

was ist funktoniert einwandfrei auf English?

"Works flawlessly"

TanteStefana2

legendary

Activity: 1260

Merit: 1001

Quote from: chaeplin on June 27, 2014, 04:29:38 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

I don't think so.

Banned by peered clients.

So we could be banned, which lasts 24 hours, and have no way of knowing it? Geepers! I doubt this is an offence that happens often, but it should be viewable somewhere. I scanned my debug logs for "ban" and didn't get anything, so hopefully I haven't been banned for anything, LOL

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

I don't think so.

Banned by peered clients.

innergy

hero member

Activity: 685

Merit: 500

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.

Can we see somehow the banned IP addresses?

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: Ozziecoin on June 27, 2014, 04:07:26 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Banning last 24 hours.
Banning is on ip address not on pubkey holding 1K or masternode pubkey.

If "bad masternode address signature thing" is occurred, bp is new ip + new genkey + new address for 1K.
But you can't assure wether your NM is banned by looking log of your NM.

CryptoPleb

full member

Activity: 196

Merit: 100

Quote from: CryptoPleb on June 27, 2014, 04:03:11 AM

Quote from: Ozziecoin on June 27, 2014, 03:59:47 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Quote from: CryptoPleb on June 27, 2014, 04:03:11 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

So you could tell that a couple got rebanned because they turned from green to red on chaeplins list?

Turned to grey on http://drk.poolhash.org/masternode.html - I waited >12 hours on greyed out ones and realised they were probably never going to be paid.

Sweet thanks

Ozziecoin

sr. member

Activity: 448

Merit: 250

Quote from: Ozziecoin on June 27, 2014, 03:59:47 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

So you could tell that a couple got rebanned because they turned from green to red on chaeplins list?

Turned to grey on http://drk.poolhash.org/masternode.html - I waited >12 hours on greyed out ones and realised they were probably never going to be paid.

innergy

hero member

Activity: 685

Merit: 500

Quote from: Ozziecoin on June 27, 2014, 03:59:47 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

Same here... green everywhere..

CryptoPleb

full member

Activity: 196

Merit: 100

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Quote from: thelonecrouton on June 27, 2014, 03:51:31 AM

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

So you could tell that a couple got rebanned because they turned from green to red on chaeplins list?

Ozziecoin

sr. member

Activity: 448

Merit: 250

Banning on "bad masternode signatures" is temporary removed.
This will help other nodes and yours.

So, *if* my masternodeprivkeys are banned, anyone running 10.11.5 will ignore the ban and my MNs should get paid eventually anyway?

I have updated my MNs to 10.11.5 but not generated a new privkey for each, not got any payments yet.

I generated new privkeys and almost immediately got paid across a few MNs. Then a couple got rebanned. I'm setting up new IPs for banned ones.

thelonecrouton

legendary

Activity: 966

Merit: 1000