Quote from: bible_pay on January 04, 2018, 09:50:38 PM

Quote from: dave_bbp on January 04, 2018, 09:02:50 PM

Quote from: hvdb on January 04, 2018, 07:12:47 PM

I need to restart some of my miners once/twice per day (reindex fixes them)
The miners that are failing use HTTPS.

The few miners that are running using http seems to be not affected (I haven't needed to restart them, but they are also slower machines)

@Dave, are you using HTTPS or http?

Interesting, indeed I use HTTPS on all of my miners (seemed like the right thing to do...), so perhaps it's really related to that. As soon as one is crashing again I will return to HTTP and see if it runs stable again.

On another note: since the security update on the pool page (required password change) I have to log on again and again because the auto-logoff is set to just a couple of minutes. This is really annoying when you want to watch your miners' output over let's say 1-2 hours because I have quite a complicated pw that I need to type over and over again. Wink

Just as a suggestion: would it be possible to 1) change the auto-logoff time to maybe 1 hour or something like that and 2) add the function that after typing username and password you can just hit return to login (instead of having to click on "login"; not sure if this is complicated to realise...)?

That shouldnt be happening, its a little more complicated on the back end; we post an HTTPS cookie into your machine with our domain and your sha256 hash of your cookie, and try to use it after the session expires - it has a dynamic expiry time due to have an app pool, so best thing is to 1) ensure your new pass actually works by logging off many and logging on, 2) open more than one window and see if you do not need to log in twice, 3) ensure you are accepting cookies from the pool.
If all this works you should no longer have that log off nuisance.

Looking at https issue now (in the core wallet).. it appears to be isolated to https traffic...

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.