View Single Post
Old 02-24-2025, 12:03 PM   #10390
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,005
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
AO3 Issues

Instead of the usual "This work is only available to registered users of the Archive." or "Sorry, we couldn't find the work you were looking for.", the site is returning a page that says:

Quote:
Reminder:
This site is in beta. Things may break or crash without notice.
There's a notice linked on the front page about "Intermittent site slowness and errors" including:

Quote:
We estimate the new Elasticsearch servers will be in place by early April. Until then, you might run into the following issues, especially during busy periods:
  • all pages loading more slowly
  • Elasticsearch-powered pages like search results and work and bookmark listings taking longer to update
  • error pages
  • automated checks from Cloudflare's Under Attack mode
  • stricter rate limiting
  • issues with services like the Wayback Machine or Tumblr RSS accounts that rely on bots, scrapers, or other automated tools, which we have deprioritized in favor of traffic from users
FFF likely is affected by one or more of these. And note that part about early April. This may be going on for a some time.

"Fix" (but not really)
  • I can add code to detect the "in beta" page and report it instead of parsing failing.
  • I can increase slow_down_sleep_time in defaults.ini for AO3.
I honestly don't know of anything else I can do.

Workaround

If you are already logged in, in your browser, the Browser Cache feature appears to work:
Code:
[archiveofourown.org]
always_login:false
## comment out username at least, otherwise Get Stories From Page will try to login
# username:XXX
# password:XXX
use_browser_cache:true
use_browser_cache_only:true
open_pages_in_browser:true
JimmXinu is online now   Reply With Quote