Issue: browsers default to broken HTTP

Like the title said, browsers default to http://cutepa.ws when writing just cutepa.ws, and the HTTP port has been 521’ing for a while now, please put a 301 or enable Always Use HTTP or enable HSTS, whichever seems fit.
_{take this with a grain of salt, idk shit about stuff like this}

I don’t know if that is the source of the most recent downtime we just emerged from as of today. I’ve also a separate theory that the website chokes on video files (I’ve seen it happen before), but no information filters down to me from higher up, since the upload you made moments before the site stopped working again has yet top be processed. I’ve deleted it to not take any chance.

As far as I can tell, the https works just fine for me as of today.

The site choking on video files does seem like a likely explanation for the downtime, albeit weird that the error given is 404, I’m sorry if it was my fault; the issue I was moreso talking about is how going to http://cutepa.ws, which some browsers seemingly default to instead of the intended HTTPS site, throws Cloudflare error 521, and so it’d be just a bit cleaner for there not to be an error. But it’s totally a cosmetic issue, plus only affects a select few browsers, plus is a Cloudflare thing, and at the end of the day I’m glad the site is even back.

Anyways, two things only related in that they’re issues and related to the site that I’m gonna drop here as a side note cause I’m too lazy to make separate topics:

My theory is that is that the specific video file (either due to size, specific file format, or some other technical detail) managed to crash the entire site, hence why the site became unavailable.

This is purely based on the coincidental timing and the fact it still had not processed after the site came back. It could be something else entirely. I just report when things go wrong and no info filters back my way 😓