alright, turns out it had nothing to do with cloudflare and more related to my nginx settings. I made some changes and it appears to have fixed the issue. Let me know if this has fixed it on your side as well.

Thank you

I believe this might be related to the fact that we are behind cloudflare. I notice other instances that are behind cloudflare appear to have the same issues while those that are not behind cloudflare appear to be ok. Lemmy.world appears to strip the embedded video function completely. See https://lemmy.world/post/49302693 as an example

I also noticed someone did open a github issue on the lemmy-ui repo https://github.com/LemmyNet/lemmy-ui/issues/4001

I’ll take a look and see if there’s something in the nginx settings that could fix this

Hey all, most of today’s outage was caused by me. I implemented Anubis in attempt to differ some bot/scrapping traffic. We are presently serving over 350 million requests per month and its starting to show in the stability in the instance. I will be switching to the horizontal scaling approach in hopes to stabilize things more.

I’ll also be providing an long overdue update once I get everything back under control.

Sorry for the stability issues as of late, you all deserve better.

@dbtng@eviltoast.org I appointed you as mod on the community. Like others have mentioned its recommended that you have an account on the instance but it’s not a requirement.

Thank you for volunteering your time to the fediverse!

Hey, we did an upgrade earlier today. All tests were passed but its possible something was missed.

Could you tell us which app you are using?

Done

Hey!

Thanks for asking, I think transparency around infrastructure is important.

This instance is hosted on equipment that we own, located in a local data center in Montreal, Canada. Backups are stored within the same facility; however, the backup hardware itself is not currently owned by us. Our S3 storage is hosted in a separate Montreal data center also on equipment that we do not own or control.

Our long-term objective is to operate our own dedicated backup infrastructure and S3 storage environment. However, the significant increase in RAM costs has temporarily delayed that rollout. Someone recently donated a few new servers however they were stripped of ram beforehand.

It’s also worth noting that we are currently using Cloudflare, but my plan to align with the broader Fedecan infrastructure strategy and transition to Deflect.ca in the future.

We have not upgraded yet but will be pushing the update this week.

Hey all,

I am very well aware of the slowness and timeouts that people are experiencing. I’m working on getting a few upgrade put into place to bring things back to where they need to be. Thanks for the patience!

Hi @kertain@sh.itjust.works

I plan on making a post to share all this information and more in the following weeks.

Thank you for your thoughtfulness and consideration!

This issue appears to have been fixed. Can anyone confirm whether they are still having any problems?

Hey all, I’m travelling at the moment but have been in discussions with the other admins about this issue. I return Friday oct 31st and will schedule to get us upgraded to 0.19.13 shortly after. I won’t be giving the typical 5 day official notice to not create any extra delays. The upgrade to 0.19.13 is minor and shouldn’t take us too long to run. Thank you for being patient.

Hi there,

We are not blocking any IP ranges. The server has had an increase in traffic over the last few months. I’m in the process of identifying new hardware to buy to make things speedy again.

I have cycled the services to see if that helps.

Let me know if things get better for you.

I’ve went ahead and updated and applied the update to our configuration files. This issue should be sorted now.

Thanks!

Thanks for bringing this to my attention.

I found that there were some changes to the nginx.conf file which can be seen here

it does look like its fixed in the 19.10 version of lemmy. I’ll do another deep dive later tonight to see if we can just update the nginx configuration without upgrading to 19.10 and if its the case will schedule another small maintenance window this week to get it pushed out.

Thank you

Hey!

Everything has been reviewed and we’re good to move over the 19.9. I’ll be posting an announcement in the coming days to give everyone a heads up. I’m aiming towards the end of this week.

I want to say that I’ve been blown away by the amount of support that’s I’ve received in the last 24 hours. You all have left me speechless. Thank you everyone who have donated and those who couldn’t, know that being a good member of this community already more than I could ask for. Thank you!

Hey there, I considered this at first but my understanding with tesseract is that this would mean we’d be proxying account credentials/tokens of other instances. I’m comfortable in doing this for our own instance but it doesn’t feel I’d be a responsible human to enable it for other instances. If there was a way to be more transparent to users using it for external instances I’d reconsider. I’m open to any feedback.

edit: typo

Absolutely. This is exactly why It’s important that we get a donation strategy put into place sooner rather than later.

This is odd. I did not upgrade pictrs (the service responsible for image hosting). There may have been an error for some specific tables rows during the database migrates. Another possibility could have been an error during the schema update that I believe the new version had to go through.

Would you be able to DM me links to other posts that you come across with broken images? I will look to see if I can identify any common trends that could tell us more.

Thank you