Hey @westingham

Thanks for starting a post about this.

Our traffic today jumped 4x our previous daily high. I had to enable some extra protection to give the server some breathing room to recover. One of the side effects is the mobile apps are temporarily unavailable until I get everything tweaked. It will be back in a few days. The good news is that I already got my hands on a newer more powerful server that will be going into production in the next few weeks.

For the next few days if you want to scroll the site you will need to use your mobile browser. I understand its totally not the same experience as voyager but I promise you i’ll get everything back up as it was as soon as I can.

Thanks for your trust and patience!

Edit: Access via the mobile app Voyager has been reinstated.

Hey! these screenshots are taken from the cloudflare panel

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?

Yes, this will not change. The /c/Agora will continue to be a platform for members to use to shape this instance.

Our Terms of Service will be likely be reviewed in the future, but our core philosophy of “don’t get us in trouble” will stay the same. We’ve always believed that the actions of a few shouldn’t negatively impact the experience for everyone else—and that belief still stands.

When it comes to defederation, we handle it on a case-by-case basis. We only consider it under very specific circumstances, or if there’s a clear mandate from the community. For example, we may choose to defederate from an instance if it’s causing harm or violating our rules, especially if their admin team is unresponsive or unreachable.

Whenever we do take such action, we usually start a discussion with the community to keep everyone informed. In fact, this has happened recently—you can read more about it here.

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

sh.itjust.works

Give that link a try again otherwise as @InEnduringGrowStrong@sh.itjust.works mentioned send us a PM with your account and we’ll manually verify it.

Thanks

Hey there! I’m sorry that you didn’t receive the activation email. Can I ask how long ago this was? I recently changed our email provider and want to make sure it wasn’t after the fact. Thanks!

test

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.

This one was received. Thanks!

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.