BitShares Forum
Other => Graveyard => BitShares PTS => Topic started by: ivan on December 26, 2013, 08:30:55 am
-
Today,I found one of my PTS wallet can't connet to the pts network again.Even though I follow the way.It still can't work.anybody helps me.
Help > Debug > Console
type:
addnode 168.63.12.227:80 add
addnode 168.63.12.227:80 onetry
addnode 94.23.215.174 add
addnode 94.23.215.174 onetry
-
:'( nobody can help me . I open the debug.log.It shows like that .
trying connection 162.243.45.158:3888 lastseen=18.0hrs
connection timeout
trying connection 162.243.45.158:3888 lastseen=18.1hrs
connection timeout
trying connection 162.243.45.158:3888 lastseen=18.1hrs
connection timeout
trying connection 162.243.45.158:3888 lastseen=18.1hrs
connection timeout
trying connection 54.212.175.33:3888 lastseen=141.2hrs
connection timeout
trying connection 162.243.45.158:3888 lastseen=18.1hrs
connection timeout
trying connection 162.243.45.158:3888 lastseen=18.1hrs
-
Hey, I also have had this problem just follow these steps and you won't have any problem anymore.
Open notepad type in :
protoshares-qt.exe -connect=cryptoseed.cloudapp.net:80
Save that file as xxx.bat in same directory as protoshares qt, make sure to select all files when saving.
(http://img268.imageshack.us/img268/9586/fxb2.png)
Next just open that bat file, It'll take some time and then connect. Everytime you can use that bat file to run.
-
Today,I found one of my PTS wallet can't connet to the pts network again.Even though I follow the way.It still can't work.anybody helps me.
Help > Debug > Console
type:
addnode 168.63.12.227:80 add
addnode 168.63.12.227:80 onetry
addnode 94.23.215.174 add
addnode 94.23.215.174 onetry
are those IP's stickied somewhere? cause they are crap (and often full, probably in the DNS seed list)
read my posts