Hi all. I was recently made aware that people have been getting error 429’s and other error 500’s when visiting fedia.io. My hope/expectation is that those will no longer happen now that I’ve moved back to a bare metal install, but if you do experience that, please comment below, or if that doesn’t work, send me an emai to jerry@infosec.exchange.
Thank you!
Okay not an error 429 or 500 this time and just some noncommittal Error with no real message in a logged-out UI (that also returns to normal upon refresh) that I once again encountered for the first time.
I upvoted this very post, e-five’s comment, and then your reply in rapid succession. The first and last actions went through, but there was a circle indicator beside the “More” option on e-five’s comment and the page ultimately loaded https://fedia.io/ecf/3871174?choice=1 and thus the error page. We’re both on the same instance and I shouldn’t be blocking them or running any script that should mess with upvoting btw
After going back from the error page to submit this comment, hit submit button only to be redirected to https://fedia.io/m/fedia/t/552719/-/comment without the comment having posted. I find the page usually needs to refresh to send a message but this was the first time I ended up on a different page when trying to write something?
Everything about your post is slightly indicative to me of javascript failing, for some reason.
So many actions taken, upvoting / boosting / replying, do javascript actions. However, all of these things have fallbacks in the case either: javascript hasn’t fully finished loading on the page yet or javascript requests failed.
For instance, if javascript had failed when I clicked reply to your message, instead this page would’ve loaded for me https://fedia.io/m/fedia/t/552719/Request-for-errors-on-fedia-io/comment/3937344#add-comment but since it worked, all it did was add a text box under your reply
As I said this is true for all other actions, so when you vote or boost there are also http GET routes that handle those requests.
It’s hard for me to guess more than that, it could be the JS is loading a bit slow and you click before the page finishes loading, or it could be a different error like maybe the request fails. There might also be something else involved, I’d have to double check but mercure might involve itself in dynamic page updating as well… Do you happen to notice if pages are still loading when you take actions, or in fact just browse with javascript disabled? There’s also that, last I checked, all the JS files had
deferon them so don’t block page loads, which is what makes this more likely to happen. Whether that’s good or not, I can’t say, it’s been like that since I first looked but might require more research to know whether it can be split between JS that should block page load and JS that can be deferredThe explanation of what happened makes sense, but indeed it’s hard to say how it’s happening. My internet speed is decent so I’m certain everything on the page must have loaded by the time I started clicking. I don’t disable JS, and the only extension I have active is one for grouping tabs because I happen to access Fedia on my “side” browser, so not even an adblocker. Blocking nothing at the router level either so not sure how requests could have failed :/