Quote from: zahzin on February 03, 2016, 11:17:42 AM

Quote from: WBF1 on February 03, 2016, 02:55:02 AM

Quote from: -ck on February 03, 2016, 01:48:16 AM

Quote from: WBF1 on February 03, 2016, 01:26:55 AM

Quote from: -ck on February 03, 2016, 01:18:44 AM

Quote from: WBF1 on February 03, 2016, 01:14:05 AM

re: pool problems... it says "Failed authorization Sad

" but I literally haven't changed a thing. Still [address].[worker] yes? I get same result on 3334 and 3333

Sure you haven't added a space or something in your username in your miner's config during copy/paste? Also once you fail to authorise you get throttled for attempted auths for the next 10 minutes (this has always been the case though).

yeah 100% sure all i did was turn off my miners for like a day. oh and i had them pointed to kano.is for a while as well.

That is most unusual indeed. Last time this happened to someone on this forum they restarted their machine and re-entered their credentials and everything worked after that. Perhaps in failover you never noticed it had never mined on solo and was always running on a backup?

i'll reboot tomorrow sometime. happily mining on DE server right now.

I have had same problem for a while, not being able to authenticate on the main server, but DE server is authenticating and working fine..

Have not reported it before since DE server is closer to me and did not want to bother thinking it was just me, but I can confirm I have copy pasted same address.worker name and can mine on DE but main SOLO is rejecting my authentication even if I put it as a backup..

Hmm that reminds me I've had this problem before. If you authed first on the DE pool you cannot auth on the main pool later on. I thought I'd fixed this bug but it seems to have returned. That would explain it. I'll look into it.