Why don't people that are having problems with NCC (mostly problems that have been explained/solved 100 times over by the way...no offense) just use the standalone lightwallet ? That's exactly why they made it. NCC has a shitty UX. The lightwallet literally couldn't be any simpler. You don't even need Java installed.
http://bob.nem.ninja/lightwallet-standalone-1.1b-cdn-nginx1.8.zipIt's a really early version but it works good enough.
My wallet has been working 100% fine since day 1 until the last week when all sorts of crap has happened for no reason.
Yes i should ask on the nem forums but havnt registered yet and im sick of signing up to countless forums for all the coins i hold etc, but NEM is one forum i should register on.
Anyway, i havnt seen anyone else reporting my issue, but i will ask on the nem forums if i will get more help there.
Ive also been concerned about security with the light wallet as mentioned here, so i would rather just use NCC if possible.
Dont know whats so shitty with NCC, its been absolutley great for me (until now! lol)
Im also interested in hosting a node, since im in New Zealand, it would be great to have some nodes running down here
What is your problem?
I posted my problem on the previous page but basically now i cant get into my wallet, it says at the top of my browser in a red bar that NIS is not running, even when the tray icon menu says it is.
Ive uninstalled, reinstalled, still the same.
Any chance you used a remote NIS before and that one is down now ? There is really no other reason for that to be happening if your local NIS is really running.
You mean delegated harvesting?
I was delegated harvesting on a remote node.
Ive tried booting a local node but it doesnt save the changes.
I don't mean delegated harvesting. I mean having a remote node configured in the settings. When you do that - e.g. when you want to harvest on a remote node but not exclusively then - you also get all the information about the blockchain from that node. If that node is then no longer online/not reachable for whatever reason you get the exact problem you're having right now.
Configure localhost or 127.0.0.1 as node in the settings and you'll be good
OK, im lost here, as i thought that the only reason for using a remote node was for delegated harvesting.
Ive had such nodes go down before and ive never had this issue, ive just always gone and changed the remote server and harvesting would start again, and all this time i was still able to login into NCC.
Anyway, ive changed the remote server to 127.0.0.1 and now it appears to login, But i now get the message at the top "NIS needs to be booted. Please open your wallet and boot a local node via the popup dialog or configure the auto-boot setting. (at block 159180)"
This is weird, since NIS is indeed booted.
Ive never had this trouble before, and my blockchain had always been syncing all this time anyway.
Just weird that trying all the servers listed would not let me in, but ill try another server and see if it works now after this