Re-registered but cgminer says to me "JSON stratum auth failed: (null)"
Thats what I was getting earlier. It is cleared now using port 8348. I put all three workers on it to help test. Come on in. LOLI am still getting this, port is 8348
Topic: [RED] REDCOIN - Official thread! - page 15. (Read 72511 times)
I am still getting this, port is 8348
Re-registered but cgminer says to me "JSON stratum auth failed: (null)"
Thats what I was getting earlier. It is cleared now using port 8348. I put all three workers on it to help test. Come on in. LOL
right okay, thanks
Workers on the server. Port 8340 did not work, but 8348 did.
it should be, although its not a definite
Re-registered on pool and cgminer looks like it connected on port 8348...
So pool is up and everything ok now?
TY
So pool is up and everything ok now?
TY
on my main site theres an irc box for all users, its got all the channels im usually in aswell.
EDIT: its up now
EDIT: its up now
Redcoin needs a chat box or an irc channel on the redcoin.pw server to help work through probs like this. Plus it would give an area for miners to chat about redcoin.
yep just comparing my config with another pool op, stratum will be up in a min
OK. Startup with only your server in it.
Shows "pool 0 slow/down, check URL or creditials invalid".
Tried with both 8340 and 8348.
Now, this is the same startup that I was just using successfully before. When it did not work, I then removed the first pool (my solo mining) and tried it with only your server in it.
Rechecked website to verify correct user/worker names and passwords, all checked good.
Shows "pool 0 slow/down, check URL or creditials invalid".
Tried with both 8340 and 8348.
Now, this is the same startup that I was just using successfully before. When it did not work, I then removed the first pool (my solo mining) and tried it with only your server in it.
Rechecked website to verify correct user/worker names and passwords, all checked good.
np, im just having a word with another op about the pool, so it might not work for a min
it should be, try both 8340 and 8348
Wont connect, tried 8340 and 8348. I'll try without the solo pool in my startup. Give me a sec, the workers are in another part of the building.
it should be, try both 8340 and 8348
youll need to register again and make new workers, created a new db, ill recompensate you all after looking through the old db
I re-registered and setup the workers, but I cannot connect. Is it still at port 8348?
youll need to register again and make new workers, created a new db, ill recompensate you all after looking through the old db
Well, they 7850's auto-switched back to the server themselves, I like how that works.
All of my unpaid shares reset after whatever you did.
The hashrate graph is working now.
All of my unpaid shares reset after whatever you did.
The hashrate graph is working now.
I grabbed something to eat and when I looked at the workers, they had all changed over to solo mining. I lost connection to the server for some reason and they auto-switched to the alternative pool (using cgminer). Did something happen to the server? I can get to it on the web fine. I wanted to find out before I switch them back.
EDIT NOTE: Ok you and I were typing at the same time. I will change the 7850's back to the pool.
EDIT NOTE: Ok you and I were typing at the same time. I will change the 7850's back to the pool.
that may have been because ive just been editing the db while the webserver is online. Ive applied some fixes, time to see if they work
Thinking about this a little more and it looks like the web server is not reading from the database correctly or not fully.
Since the web stats show that there is only 3 workers and it has 2 users in the hashrate section, but lists 8 users in the share section, there might be some rights issues to read the database contents.
Since the web stats show that there is only 3 workers and it has 2 users in the hashrate section, but lists 8 users in the share section, there might be some rights issues to read the database contents.
with the pool youd be getting a bit less due to less power but now that you all have said theres a proble, ill still look into it just in case
Jump to: