Quote from: Boswell on February 13, 2014, 06:01:14 PM

Quote from: Unpropitious on February 13, 2014, 04:18:11 PM

If you took the one posted by someone on the first page for conf file asking for help, it did not work for me. This however worked:

listen=1
daemon=1
server=1
rpcuser=**user**
rpcpassword=**pass**
rpcallowip=10.1.1.*
rpcport=18382
rpcconnect=127.0.0.*
addnode=219.90.254.80
addnode=122.62.19.98
addnode=101.98.184.135
addnode=78.51.74.99
addnode=14.201.151.38

Also I had to delete the stuff from roaming folder after adding this. However judging from your post you might already have done this. I'm just wondering if you used this for the conf file.

Thanks for the reply. Unfortunately didn't work either Sad

I took a look at the debug.log (the actual text file, not what is displayed in the Help menu) and there are these failed connections:

Code:

UPnP: ExternalIPAddress = 86.156.164.51
AddLocal(86.156.164.51:18381,3)
connection timeout
ERROR: GetMyExternalIP() : connection to 91.198.22.70:80 failed
connection timeout
connection timeout
UPnP Port Mapping successful.
trying connection 122.62.19.98 lastseen=0.0hrs
connection timeout
ERROR: GetMyExternalIP() : connection to 74.208.43.192:80 failed
connection timeout
IRC connect failed
IRC waiting 71 seconds to reconnect
connection timeout
trying connection 101.98.184.135 lastseen=0.0hrs
connection timeout
ERROR: GetMyExternalIP() : connection to 91.198.22.70:80 failed
connection timeout
trying connection 78.51.74.99 lastseen=0.0hrs
connection timeout
ERROR: GetMyExternalIP() : connection to 212.117.175.194:80 failed
connection timeout
trying connection 14.201.151.38 lastseen=0.0hrs
connection timeout

As far as the 71 seconds to reconnect part goes, is there anything I could add to my config file to reduce the reconnect time from 70 seconds to like... 0.000001 seconds? Might be able to spam this bastard into submission

Another thought, could my IP have anything to do with it? BT is horrible with their IP allocation, and I have problems posting here, presumably because thousands of other people are sharing an IP address. It's also wrongfully blacklisted in some IRC chatrooms, because it shows up on the spamhaus.org database, even though they acknowledge it is a common BT IP, and the blacklist should only be used as a guide.

Is it possible the creator of TopCoin thought he was being clever implementing some sort of extra security feature, but instead ended up blocking a ton of BT users? It would be interesting to find the common denominator in those of us having problems, i.e. are we all BT customers?

Sorry, my theories are bordering on crazy now.

Honestly, I don't have a clue. But I googled something and someone said they unchecked the proxy of another wallet with same sort of errors and that helped. There's an option for proxy in the settings. Maybe you have that checked?