Temporary fix for those who are having issues connecting to our Peercoin network

Thireus · March 15, 2015, 4:27pm

Some people are reporting issues to connect to our Peercoin network. This issue is related to the node discovery service (IRC/DNS) which is not working at the moment. As a temporary fix and until we find the root cause of this issue you can add the following Peercoin nodes manually to your wallet client (ppcoind, Peerunity or Peercoin-QT):

[ul][li]62.210.141.185 ([member=32109]Thireus[/member]'s node)[/li]
[li]107.170.43.92 ([member=31330]MatthewLM[/member]'s node)[/li][/ul]

On Windows:

[ol][li]Create a shortcut for your Peercoin Wallet (i.e. Peerunity) on your desktop[/li]
[li]Right click, and open the “Shortcut” tab[/li]
[li]Add -addnode=62.210.141.185 at the end of the “Target” field[/li]
[li]The “Target” field should look like: “C:\Program Files (x86)\Peerunity\Peerunity” -addnode=62.210.141.185[/li]
[li]Apply the changes[/li][/ol]

Now open Peerunity by doube clicking on the shortcut you’ve just modified.

Also, don’t forget to authorize Full network access for your Wallet in your Windows firewall rules (Peerunity connects to nodes on port 9901, so you should allow outgoing connections for that port):

On Linux:

[ul][li]Launch ppcoind/Peerunity/Peercoin-QT with the option -addnode=62.210.141.185 directly from your command line[/li]
[li]You can also add nodes via the Peercoin’s configuration file, explained by [member=1]FuzzyBear[/member] here: https://www.peercointalk.org/index.php?topic=3.0[/li]
[li]Or you can also add the node via: ppcoind addnode 62.210.141.185 add[/li][/ul]

On MacOS:

[ul][li]Launch ppcoind/Peerunity/Peercoin-QT with the option -addnode=62.210.141.185 directly from your Terminal[/li]
[li]Peerunity and Peercoin-QT binaries are normally located in ‘/Applications/(Peerunity/Peercoin-Qt).app/Contents/MacOS/’[/li]
[li]Example: “/Applications/Peerunity.app/Contents/MacOS/Peerunity -addnode=62.210.141.185”[/li][/ul]

Old post containing other nodes: https://www.reddit.com/r/peercoin/comments/1ritix/wallet_not_connected_to_ppcoin_network/cdogfj1

[size=18pt]Please if you want to help we need a bigger list of Full Active Nodes.[/size] Also, if anyone can provide EN screenshots that will be more helpful…

The issue has been reported on Github: https://github.com/ppcoin/ppcoin/issues/85 and https://github.com/Peerunity/Peerunity/issues/159

[quote=“Sunny King”]Weekly Update #134

[…]

[ul][li]There was a outage with two of our main seed nodes on the network earlier this week, some users might have experienced difficulty initializing connection to the peercoin/primecoin network. Existing nodes on the network are not affected. The seed nodes in question are now up and operational.[/li][/ul][/quote]

peerchemist · March 15, 2015, 6:03pm

I will issue a hotfix for Peerbox if anyone can confirm this happening.

Azhija · March 15, 2015, 10:11pm

My raspberriPi peerbox (running since 3/10/15) seems to be fine with the network. However, I just compiled a Peerunity Wallet on my Linux machine, and it showed no network connection. I had to use the command line to start peerunity with “-addnode=62.210.141.185”, as suggested by Thireus. Now it seems connected and gathering block data.

Does the “ppcoin.conf” work for PeerUnity (linux)? I couldn’t find the file and was not sure I need to make it or edit it.

Thireus · March 15, 2015, 11:30pm

I think it does, but you have to create it :).

github.com

Peerunity/Peerunity/blob/master/src/init.cpp#L199


      
          if (mapArgs.count("-?") || mapArgs.count("--help"))
          {
              string strUsage = string() +
                _("Peerunity version") + " " + FormatFullVersion() + "\n\n" +
                _("Usage:") + "\t\t\t\t\t\t\t\t\t\t\n" +
                  "  peerunityd [options]                   \t  " + "\n" +
                  "  peerunityd [options] <command> [params]\t  " + _("Send command to -server or peerunityd") + "\n" +
                  "  peerunityd [options] help              \t\t  " + _("List commands") + "\n" +
                  "  peerunityd [options] help <command>    \t\t  " + _("Get help for a command") + "\n" +
                _("Options:") + "\n" +
                  "  -conf=<file>     \t\t  " + _("Specify configuration file (default: ppcoin.conf)") + "\n" +
                  "  -pid=<file>      \t\t  " + _("Specify pid file (default: ppcoind.pid)") + "\n" +
                  "  -gen             \t\t  " + _("Generate coins") + "\n" +
                  "  -gen=0           \t\t  " + _("Don't generate coins") + "\n" +
                  "  -min             \t\t  " + _("Start minimized") + "\n" +
                  "  -splash          \t\t  " + _("Show splash screen on startup (default: 1)") + "\n" +
                  "  -datadir=<dir>   \t\t  " + _("Specify data directory") + "\n" +
                  "  -dbcache=<n>     \t\t  " + _("Set database cache size in megabytes (default: 25)") + "\n" +
                  "  -dblogsize=<n>   \t\t  " + _("Set database disk log size in megabytes (default: 100)") + "\n" +
                  "  -timeout=<n>     \t  "   + _("Specify connection timeout (in milliseconds)") + "\n" +
                  "  -proxy=<ip:port> \t  "   + _("Connect through socks proxy") + "\n" +

github.com

Peerunity/Peerunity/blob/master/src/util.cpp#L919


      
              fs::create_directory(path);
          
              cachedPath[fNetSpecific]=true;
              return path;
          }
          
          boost::filesystem::path GetConfigFile()
          {
              namespace fs = boost::filesystem;
          
              fs::path pathConfigFile(GetArg("-conf", "ppcoin.conf"));
              if (!pathConfigFile.is_complete()) pathConfigFile = GetDataDir(false) / pathConfigFile;
              return pathConfigFile;
          }
          
          void ReadConfigFile(map<string, string>& mapSettingsRet,
                              map<string, vector<string> >& mapMultiSettingsRet)
          {
              namespace fs = boost::filesystem;
              namespace pod = boost::program_options::detail;

paumiau · March 16, 2015, 8:59am

Thanks Thireus!!
Great work

Thireus · March 16, 2015, 9:11am

This issue has been reported on Github, so hopefully we’ll come up with a temporary fix soon: https://github.com/ppcoin/ppcoin/issues/85

But that means modifying ppcoin, Peerunity and Peercoin-QT.

thokon00 · March 16, 2015, 10:19am

Hi,

I don’t think it is necessary to modify the the clients. With the right DNS configuration of the current seed host names in the clients we could almost instantly make use to the bitcoin-seeder software: https://github.com/sipa/bitcoin-seeder. I’ve already done that earlier and it works just great. I also commented on github issue #85 and I would be willing to help here. Please get in touch with me.

regs
Thomas

Sunny_King · March 18, 2015, 7:57am

Two main seed nodes have been down recently. They should be up and running as of today.

Thireus · March 18, 2015, 9:34am

[quote=“Sunny King”]Weekly Update #134

[…]

[ul][li]There was a outage with two of our main seed nodes on the network earlier this week, some users might have experienced difficulty initializing connection to the peercoin/primecoin network. Existing nodes on the network are not affected. The seed nodes in question are now up and operational.[/li][/ul][/quote]

Thanks SK!