You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I really dunno if it's due to my poor internet, the massive internet usage during this sanitary crisis or the plugin bugging, but it keeps happening more and more frequently that the plugin isn't able to refresh for new chapters/read chapters.
This on the chrome webstore version.
Could you please check if it's a me problem or the plugin problem?
thanks for this amazing plugin anyway :3
The text was updated successfully, but these errors were encountered:
After a quick investigation, it's caused by CloudFlare.
There is a "browser verification" to be done before accessing the website every few days now. For now, I suggest to simply click the "Open" button, pass the verification then it should work in the next refresh.
I'll see what can be done to detect this issue and have a more "natural" fix in the extension. Either showing an explanation with a button to click, or automatically loading the CloudFlare verification in the popup.
ah thats is why it never worked...
if you use containers don't forget to login with your account in the Tab without loaded container.
that is why the other browser didn't work ether.
I just published the 1.5.0 version, which should detect Cloudflare errors and show a better badge message and popup:
It should already be there for FF, and should arrive in Chrome once reviewed.
I wonder what happened for the NU admin to add CF challenges all of a sudden. 🤔
Hi,
I really dunno if it's due to my poor internet, the massive internet usage during this sanitary crisis or the plugin bugging, but it keeps happening more and more frequently that the plugin isn't able to refresh for new chapters/read chapters.
This on the chrome webstore version.
Could you please check if it's a me problem or the plugin problem?
thanks for this amazing plugin anyway :3
The text was updated successfully, but these errors were encountered: