Ao3 being slow
-
Hi everyone! I had a question, while trying to access ao3 using the switchbru it usually takes a while or goes to the cloudfare thing that says its ao3's fault. I go to different websites using switchbru and it works but going on ao3 on phone/computer works so. Anyone else have this problem and if so any way to fix it? Hopes this makes sense
-
The Dark Side Raven Empire ultrakill Gets hated on Chaotic People IMA BURN IN HELL, but<3 NOCTURNAL D e p r e s s i o n . . . Konoha Comrades straight allies! "Do Your Worst, You All Might Wannabe!" "Get Out Of... My Way!"! "If It Could Come True This Is All I'd Want." "...Well... I Guess Taking My Time's Not All Bad." "CHAOS, Right?"
-
Could just be browser limitations or something related to that, if it works on phone/computer then it is probably something regarding with the browser.
Cloudflare can be annoying too, I have a feeling that it is just another way for Cloudflare to verify you're a human or restrict your access because you the browser you're on. You are likely being flagged as a bot on Cloudflares side.
-
I'm seeing this as well, on Switch and not PC even on the same network. Here's a screenshot of the error:
It also seems like it happens inconsistently. If you click on search and wait for the page to load, sometimes it resolves and sometimes it doesn't. A workaround is using google's search instead, but if this issue keeps happening I'll investigate further.
-
Found another workaround! Try: http://insecure.archiveofourown.org
A quote from the ao3 team (from reddit):
Older devices unable to load the site: Due to necessary updates in the site’s security, some older devices may be unable to access the site, getting a message like “could not establish a secure connection to the server”. If upgrading to a newer device is not an option, we maintain an insecure version of the site at http://insecure.archiveofourown.org which users on obsolete devices can access. Please be aware that using an insecure site can leave you vulnerable to having personal information such as password or browsing history intercepted.
Sign in doesn't work on the insecure site, however (and you shouldn't sign in, anyway, without HTTPS). For just reading and searching however, this may be a useful option.
I still think that it's a cloudflare SSL bug that should be fixed on their end, however. It doesn't appear to be the usual Cloudflare verification issue (which Raven mentioned), and seems like a problem with their Cloudflare configuration.
