Quote from: dave_bbp on January 05, 2018, 07:29:45 AM

Quote from: dave_bbp on January 04, 2018, 10:35:51 PM

So I tried logging on and off several times, this didn't help. Having logged in I can open another tab and don't need to log in again, so this is working.
Then I checked the cookies my browser saved from pool.biblepay.org and I think I found the mistake: the credentials_password cookie saves a wrong value for my pw (double-checked this by deleting it, logging off and on again, same mistake). The problem seems to be that my pool-pw uses a semicolon ( ; ) in the middle of the word and this seems to create a problem for the cookie, because the cookie-pw stops at the letter before the ";". I will try and change my pw again without diacritical signs and see if that helps.

One of my computers just crashed again, I disabled SSL, let's hope for the best. :-D

Edit:
Oh, you beat me to it by posting the update, I'm gonna give this a try then, let's see how it works out over night.

Seems to have worked as expected over night. I tried 3 different things:
a) one machine with 1.0.7.5 and SSL enabled --> crashed
b) one machine with 1.0.7.5 and SSL disabled --> worked
c) one machine with 1.0.7.6 and SSL enabled --> worked

So this was definitely and solely an SSL issue, which is fixed in 76; thanks again.

Regarding the pool login: now without the semicolon in my password the pool page works like a charm and does not kick me out every couple of minutes, so problem solved I guess. Wink

Only "problem" remaining is: why is the (only existing) pool hitting less than 20% of the blocks. Roll Eyes

Great to hear, thanks! Let me take a look at this 20% block thing in detail next.

EDIT: Btw, I just realized when you fixed your problem with the removal of the semicolon, the cookie actually contained your password, the one you typed in on the UI, that was not intentional thats a bug, that is supposed to be hashed first. So this will be fixed in the next pool release also so that the password is never stored anywhere.