View Single Post
Old 09-25-2024, 04:21 PM   #9975
steltek
Connoisseur
steltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura aboutsteltek has a spectacular aura about
 
Posts: 70
Karma: 4484
Join Date: Jan 2016
Device: none
Quote:
Originally Posted by JimmXinu View Post
Do you have username/password set in personal.ini? What about always_login:true? Because this suggests we MIGHT be asking for login when we don't need to, if you don't have them set.

I am able to see this behavior myself this morning--and it remains inconsistent. Sometimes login works, sometimes it doesn't.

In the same Calibre session, I just saw work-fail-(time reading logs)-work-work on the same restricted story spread across 20 minutes.

As far as I know, this only affects login. And I suspect FFF sees it more often because of always_login:true being set.
I even went to far as to try to override the FFF user agent with the current browser user agent string for Firefox in personal.ini to see if that would fix the issue. My thought was that maybe something during the login was setting off the Cloudflare/A03 site security and that it was rejecting the login because it was maybe detecting that the login was coming from a non-browser application. The first time I tried it, it actually worked with links that were just seconds earlier not working. However, after getting my hopes up, it then reverted to form and started failing at login again a few minutes later.

I think you are right: the dead chicken is not just waving but is flapping in a brisk wind. Whatever is going on is a legitimate A03 server login issue (maybe something to do with Cloudflare's security and changes A03 made in their login process) and that there is nothing that can be done to fix it from the user side beyond doing exactly what you recommended - turning off always_login:true unless it is truly needed.
steltek is offline   Reply With Quote