Entrepreneur, developer, seasoned system and network engineer, aspiring hobbyist pilot, husband and father.
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
Hey,
I’m due to make a post about the instances finances soon. I’ll get one posted in the next bit.
I’m still covering costs out of pocket but my goal has been to have this instance fully funded by its members. I want this instance to stay true to its members, the fediverse and be put in a position where it can continue to thrive transparently without me. The admin team has been doing an outstanding job keeping this instance safe and moderated for everyone. I don’t thank them enough but they are the true heroes of this instance.
As some may know, I’ve been working with a local non profit for the past 6 months to have them leveraged in accepting accepting donations for this instance. They have been slow to get things done but its progressing. I may end up doing what I was trying to avoid and create my own non-profit instead if that’s what it takes. That direction does have its own challenges and would add additional responsibilities to my plate.
In the meanwhile, while some of the costs of the services have gone up slightly, I get joy knowing that I can continue providing this instance to all of you. I’m OK paying the costs to keeping the lights on until we can transition to donations.
deleted by creator
Yes, I’ll get this done
UPDATE: here you go https://oldsh.itjust.works/
There was a little hiccup this morning unrelated to the migration tonight. The Lemmy services like to be restarted every once in a while. Once we move to the new hardware I’ll be able to look into implementing a better logging system and hopefully be more proactive when situations like these happen.
The biggest consumer of storage on this instance is related to the image hosting which we use an external object storage provider for. The second is the database which is no were near the 2TB capacity. 1TB SSDs are cheaper than 2TB SSDs and I also didn’t want to spend more than I needed. As other mentioned if we need more space or IOPs in the future, I could accomplish this by adding more drives as a quick fix. This server does not support NVME unless I leverage its PCIe ports but I don’t plan on doing that. By the time this instance gets to the point where 10 SSD drives just isn’t cutting it anymore I’ll probably have come across another opportunities on getting a new server with better NVME support.
I’ve started the preparation steps to minimize the maintenance window needed for this upgrade. These operations are running some background tasks and once they are done I’ll make an announcement to give everyone a few days heads up of the anticipated upgrade time and date. Should be soon.
Hey!
The best way is to @TheDude on our matrix channel. This action triggers notifications across all my devices, creating a barrage of alerts that almost always grab my attention, a.k.a a ddos to my sensory system.
@kersploosh@sh.itjust.works explained it well. It was related to a small bug on the pictrs service that I’ve already reported which they quickly fixed in a newer version. I will tackle this upgrade at the same time as I get this instance up to v19
Hi there
Sent you a message on the matrix chat. This should now be fixed.
Thank you
@Buddahriffic@lemmy.world Please send me a DM with the username and email address used to sign up and I’ll manually verify your account.
Could you provide some additional information on what is not functioning well? Screenshots with errors are also very valuable.
Hey all,
I have made some changes to how this instance sends email that should help with the email issues people have been experiencing. If anyone continues to have issues receiving emails please let me know
Thank you
Hey,
I did some research on this.
I will not share the list of accounts as I feel its everyone right to vote and to have their own opinions whether they align with yours or not.
I will however say, Its mostly the same accounts that are down voting you. The majority of the accounts are over 2 months old with content generated by them (they do not seem like bot account). There are a few that are just 10 days old. 99% of the down votes are from other instances with feddit.uk and feddit.nl being the primary source of them.
Please DM me your username and email address used to register and i’ll get it sorted out.
Thank you
The big email email providers are not liking the amount of email coming from the server ip. The permanent fix is to use a mail sending service. I do plan on making that adjustment soon.
In the meanwhile send me a dm with your username and email address used and I’ll verify the account for you.
Thanks
You should not be blocked from editing communities. If that’s the case we’ll have to open an issue with lemmy
I’ve went ahead and updated and applied the update to our configuration files. This issue should be sorted now.
Thanks!