My wallet was completely unlocked. I also tried a new, empty and unencrypted wallet. I took out some custom proxy settings that I thought might be impacting communication. My client is fully synced (version 0.5.3). I checked the Nu client debug log and but no entries when NuBot fails to connect. I am still getting the same error I presented earlier. I will try using 0.1.5, but I doubt that will make a change.
What is another method of connecting to the Nu client that I could employ as a test?
Are you running the Wallet as Graphical wallet or on the command line?
Could you run on the command line and then enter the command $ nud getinfo
and see what it says?
you should see some data returned. If not we can debug some more.
Can you please try opening a terminal and using curl to getinfo via RPC?
curl --user <same as in nu.conf> --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:9091/
after changing the username as in nu.conf and sending the command you will be prompted for the password.
Can you paste the output ( redact the ip address please ) ?
Are you sure that the port used by Nu is 9091? In my case, after checking the ports used by the processes (i am on Win), I realized that Win runs Nu on port 7890.
Therefore I had to change nudport and rpcport to 7890.
I’ve worked with desrever, woolly sammoth and sigmike with PM both yesterday and today to resolve the issues I possess. They have been very helpful and there has been measurable progress, but there are still outstanding issues. We will get them resolved. Between now and their resolution, thank you for patience.
Once we are open-source, we will need a liquidity provider for Bittrex, a major US alt-coin exchange. Perhaps if Exco.in is still under attack, @Muchogusto would be open to supporting Bittrex instead?
For @Excoin’s sake, I really hope that this isn’t the case. I know that their team is working overtime to shut down all avenues of the on-going DDoS extortion attempt.
I have just started working with pennybreaker and woolly_sammoth to try
to get NuBot communicating with Nu software again. Hopefully the
difficulty will be resolved soon.
Our site has been compromised by a sophisticated botnet. We are currently investigating the source. Any assistance would be greatly appreciated. All of our findings:
I still want to provide 50,000 liquidity, even with the bad news at bter and excoin. My pay will be very much earned The primary step is getting NuBot running. Progress is being made as I discuss with the NuBot team. Then, a new decision will need to be made about which exchange or exchanges to support. Where is liquidity needed?
Hi @muchogusto. Any update for us? Liquidity at Poloniex or Bitcoin.co.id would be useful at this point, and upcoming exchanges like Bittrex as well when the source code is revealed.
A few days ago @pennybreaker say he would make a Ubuntu image preconfigured that I could use.
I would be pleased to be first liquidity pool user of @KTm or @jmiller. If we can negotiate a split of my 10,000 pay and it looks like shareholders take the change in contract I can start today. We could split funds between Poloneix and Bitcoin.co.id with most going to Poloniex because they contain more trading. I would advance motion asking shareholder to approve these contract changes. If motion fails, I quit pool.
Any shareholders opposed to such changes? Changes are use pool, not solo and use Poloniex and Bitcoin.co.id, not Exco.in.
I contact @KTm and @jmiller to negotiate possibilities now.
The primary step is getting NuBot running. Progress is being made as I discuss with the NuBot team. Then, a new decision will need to be made about which exchange or exchanges to support. Where is liquidity needed?