27 blocks in solo Mining, 2G HashPower
![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
WHT CONF FILE ARE YOU USING?
It's the same as any other, the info is in the OP.
Still no pool?
It most certainly is NOT the same as any other. What other coin forces you to solo mine on a port OTHER than the coin's default port? Plus there must be something else in the sauce because repeated attempts by multiple people to solo mine this coin have scored a big zed.
Anyway, that doesn't address anything other than the question being a reasonable one. RTFM does no one any good when they are following the manual.
So, my experience is that using port 17333 my password gets refused. "Pool 0 slow/down or URL or credentials invalid". If I use port 17334 I get a connection but it hashes forever without finding any blocks. That could be bad luck/variance, but I was just on IRC with someone who claimed to have the same experience putting with a 160Gh/s setup.
So yeah, Looks like there is something different from other coins and a working zetacoin.conf file (sanitized of course) might actually help.
At this point, between the lack of functioning pools and my failed attempts to solo mine, I'm ready to write Zeta off entirely. I don't mean to be bitchy and take my toys and go home, but there comes a point where it's time to cut bait. Nearly 48 hours hashing with two block erupters and at least six hours of my time down the drain, for what? 65 Zetacoin. I'm a chump for putting this much energy into it.
Edit to add:Here's my zetacoin.conf. No need to share one that is working. Here's one that doesn't.
listen=1
daemon=1
server=1
rpcuser=myusername
rpcpassword=mypassword
rpcport=17334
rcpallowip=127.0.0.1
rpcallowip=10.0.13.*
maxconnections=80
addnode=188.252.16.110
addnode=54.212.51.236
addnode=75.162.220.45
addnode=105.236.111.72
And yes, of course I tried 17333 first. I used to have banscore=1 in there as well but took it out to see if that would help.