iKill101

joined 1 year ago
MODERATOR OF
[–] [email protected] 1 points 10 months ago

When I say two servers I mean two VMs to get the system to work effectively.

From memory, the admin interface doesn't get an SSL certificate issued to it. It perpetually stays HTTP. If you don't set up another server as a reverse proxy, it won't let you log in due to CORS issues. Add another server as a reverse proxy, and it'll come good and let you log in.

Hopefully that makes sense?

[–] [email protected] 12 points 10 months ago

I mean, my local Colesworth doesn't really give a shit. I've seen people on the phone buying mass gift cards and had to step in because the staff just allow the purchases. I haven't heard a warning over the PA/in-store radio for years now. YMMV but it's still a problem around NW Sydney it seems.

 

As per title.

Wondering if anyone else here has had any experience with the self-hosted version of OneUptime? And specifically, has anyone had any luck setting it up behind Nginx Proxy Manager?

I've managed to set it up, but I'm honestly not 100% happy with how you have to essentially have two servers to host it (one being a reverse proxy for the admin interface, the other being the application core).

Don't get me wrong, it's neat and definitely full featured, but there is still a long way to go with it. For my use case, I wanted a public status page that people can subscribe to for updates. I'd come from UptimeKuma which was fantastic but lacked the subscriber feature. I used to use Cachet back in the day before it became abandonware (the original owner bought the rights back for it and has rebooted development for it, though!).

 

For my non-Aussie friends, the ATO = Australian Taxation Office.

 
 

She was asleep like this, but as I picked my phone up she woke up... still with tongue out.

 
3
Sorry about the downtime... (external-content.duckduckgo.com)
 

What happened?

Our SSL certificate expired, which rendered our instance unusable - that is, no content would load.

Why'd it happen?

We're not 100% sure. NGINX Proxy Manager is supposed to renew the certificate automatically, but it didn't. I'm suspecting this has something to do with how I've set it up. I'll need a bit of time to investigate further.

Why'd you take soo long to fix it?

Busy with IRL work, and didn't notice it. I haven't had time to jump onto Lemmy in the last 24 hours.

What steps are you taking to ensure this doesn't happen again?

I'll be adding the Lemmy instance to my UptimeKuma server to monitor the cert expiry, and give me notice before it expires. If I can't figure out why it's not renewing automatically, I'll renew the certificate before it expires again.

[–] [email protected] 3 points 1 year ago

Hey, thanks for the link/suggestion for Yattee! Never knew something like this existed for iOS.

[–] [email protected] 15 points 1 year ago* (last edited 1 year ago) (6 children)

Music production. And IT in general.

But specifically the music production; started off as "I'll by FL Studio and muck around with it" to "I need ALL THE VSTs!". I've sunk like $2500 into it in the last two months (which is a hell of a lot of money to me), and I keep buying shit for it.

Am I any good at it? Fuck no. But it's not stopping me from keeping at it and buying shit I probably don't need :P

And the IT stuff consists of rack-mount servers and Pi's. I've sunk around $25k into it all over the last 12 years.

 

Unfortunately, some people have decided to post CSAM on remote instances. The moderators of the communities have been very proactive, but because of the federated nature of Lemmy, it means the material had federated.

So like most instances are doing, we've initiated a purge on the pictrs database/filesystem to delete ALL images from the last 24 hours.

Images may appear broken. I'd like to apologise for the inconvenience, but as Lodion said best on his post in [email protected] - "... this is pretty much the nightmare scenario for an instance. I’d rather nuke all images ever than to host such content."

It's pretty disgusting.

For fellow Lemmy admins who are curious, the script to delete is:

sudo find /srv/lemmy/example.com/volumes/pictrs/files -type f -ctime -1 -exec shred {} \;

Be sure to modify the path to point to your pictrs directory!

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

I hope that in my lifetime I can see ISPs regulated as a public utility.

From an Aussie where our Internet is somewhat considered a "public utility" (NBNCo), it's not the best. I'm paying $130/mo (Aussie bucks) for 250/100 fibre.

Our NTDs are capable of gigabit symmetrical, but thanks to our Lord and Saviour, Rupert Murdoch, it was essentially limited speed wise and the network was built with ridiculous complexity, such as the CVC constraints (Connectivity Virtual Circuit), which means ISPs have to buy additional bandwidth and hope and pray that every user doesn't max out their connections at the same time.

For example, the POI (Point of Interconnect) I'm connected to has a total of 1.5Gbps with the ISP I'm with. Based on their stats which they make public to customers, I'm guesstimating that there's approximately ~50 other households in my POI area connected with this ISP. We all have to share that bandwidth otherwise it slows to a crawl.

ETA: I'm purely talking about the FTTP network here, not the other part of the mess that is NBNCo and FTTN/C/B, Fixed Wireless, Satellite & HFC... the NBN is a complete mess.

[–] [email protected] 1 points 1 year ago

And the update is done! Any issues, please let me know!

 

As per the title, 0.18.4 was released a few days ago and we'll be updating to it in the next hour.

As usual, attached is an overview of the (new) server! Barely a scratch so far. Everything is running optimally.

Thanks for all your support! ❤️

 
[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

And for context, this VM now has 4 cores (compared to 1), 8GB of RAM to play with (compared to 1GB), 120GB of storage (compared to 19GB) and is no longer contending with other VMs on the host (as I'm managing the host in colocation). RAM and storage is also easily expandable at the drop of a hat.

It should be a lot quicker!

[–] [email protected] 2 points 1 year ago

We did have an issue with NPM refusing to start, which is what took the most time to get sorted and why we were offline for more than 5 minutes.

 

Kinda. There are a few small issues to still figure out, but for the most part we're back and should be federating.

I'll be working over the coming hours to finalise things and fix the niggly errors.

If you notice any errors, please message me or post here.

Cheers!

[–] [email protected] 1 points 1 year ago

And we're ready for the migration! I sure hope this works 😂

Shutdown will begin at 16:00 AEST (in 13 minutes).

[–] [email protected] 1 points 1 year ago

Currently preparing the new VM for the migration (firewall, installing docker, etc)

 

Hopefully you won't notice much downtime, because it's going to be a relatively simple migration. But if you do notice, apologies in advance!

I plan on doing the migration within the next 24 hours. Possibly sooner. Can't give an exact time at the moment, but check the comments. I'll post updates here.

[–] [email protected] 8 points 1 year ago

Yeah it's an absolutely shitty predicament to be placed in.

My partner was lucky in the sense that she's been given basically guaranteed shifts... but she's off crook with the flu, which she caught from one of her clients. Which means she's going to be up shit creek this fortnight money wise.

[–] [email protected] 10 points 1 year ago* (last edited 1 year ago) (2 children)

perhaps having some sort of “earnings bank”

There already is this feature in place for CLink recipients. It's called "Working Credits". But, you can only earn 48 "credits" (being dollars) per fortnight, up to a maximum bank of 1000 on JobSeeker. Source

Their example of how it works:

Janine is single, has no children and doesn’t earn an income. Over time, Janine has built up 1,000 Working Credits as part of her JobSeeker payments.

Janine starts a full time job earning $1,600 per fortnight. In the first fortnight the 1,000 Working Credits reduce the amount we count as income from $1,600 to $600. This means Janine gets some JobSeeker Payment that fortnight. Janine’s Working Credit balance is zero.

The next fortnight all of Janine’s income will count. This reduces Janine’s JobSeeker Payment to zero.

My partner went through this recently. She got a casual job (which is great), and used up all of her working credit for the fortnight. I think the amount you can "bank" is a bit too small IMO. Along with the amount you can earn before you're cut off completely. With Cost of Living going through the roof, she's finding that she has to cut back on food and other essentials because rent is getting ridiculous, shopping for food is getting ridiculous and yeah. Plus the risk of it being casual work, there's no guarantee of shifts.

¯\_(ツ)_/¯

 

As per the title, we've just upgraded the instance to 0.18.3. Hopefully this'll fix the database taking up enormous amounts of space!

I've also attached some graphs of the instance's status for the nerds out there.

If you notice any issues, please let us know!

Thanks ❤️

view more: next ›