the problems mentioned by @cstine@lemmy.uncomfortable.business are what lead me to try Caddy.. there's no fancy gui but it does "just work" once you figure out the caddyfile..

wasabi is cheaper than B2 unless...

• you store less than 1TB (they charge for a minimum of 1TB even if you store nothing)
• you pay for any data you upload for 90 days minimum.. so if you upload 500GB and then delete it within 90 days, you're paying for it for the duration anyway..
• You can only download the same amount as you store in a month without incurring egress costs.

The 3 points above are how they can not charge egress for the majority of people.

not difficult to understand really.. I posted that comment in a different thread but it showed up in this one..

Or.. to be more precise (possibly) I intended to post it in a different thread...

torrentgalaxy, search for :

Buffy.the.Vampire.Slayer.S01.1080p.WEBRip.x265-RARBG Buffy.the.Vampire.Slayer.S02.1080p.WEBRip.x265-RARBG Buffy.the.Vampire.Slayer.S03.1080p.WEBRip.x265-RARBG Buffy.the.Vampire.Slayer.S04.1080p.WEBRip.x265-RARBG Buffy.the.Vampire.Slayer.S05.1080p.WEBRip.x265-RARBG Buffy.the.Vampire.Slayer.S06.1080p.WEBRip.x265-RARBG Buffy.the.Vampire.Slayer.S07.1080p.WEBRip.x265-RARBG

oh wth..this isn't the first time this has happened.. i posted that on a thread about buffy.. how the hell did it end up in here.

Depends what it is you miss about RARBG.. if it's the x265 encodes, then look up Infinity on torrentgalaxy

your connection is 50 megaBITS not megaBYTES.. so divide 50 by 8 and you'll get your answer..

50 / 8 = 6.25

Now take in to account the overheads.. the speed you're seeing is completely accurate.

If you wanted to download at 50 MegaBYTES as you insinuated then the same math applies...

50 * 8 = 400

So you'd need to pay for a 400 to 500 Megabit connection.

I have a 900 / 110 connection and my actual MegaByte speeds are 90 / 10

You may feel hard done by, but this has always been the way.. as far as I know every ISP in the world markets in Mb (MegaBit) not MB (MegaByte)

It's a very good question and of course.. i could fork it and fix it using the PR.. but then that would be it.. I'm not experienced enough to even achieve that to be honest..

My issue I guess is not so much with the fact that there is a problem... it's with the fact that i can't afford for my homelab to be down because it's never fixed or takes time to fix... i appreciate all of this is free.. i think i may of even donated at some point because i was so thankful it existed.. but now it's such an integral part of my and my families life that i cannot have something in my stack that isn't going to be fixed rapidly.

JC21 created an amazing product and if it's fixed or V3 ever appears i'll 100% check it out.. but for now whilst it's not as pretty.. i have to fall back to caddy.

Agreed but it's more the worry that it's been broken for over 3 weeks and the dev(s) seems to have no interest in resolving it... to me that is a bad sign of things to come and projects being abandoned.

If i'm incorrect and the devs have been vocal about the issue then please correct me and point me to where i should be looking.

I've switched from NginxProxyManager to Caddy as i don't like the fact that 2.10.3 has just broken the certificate side of things...

The thing i really miss is having a GUI to handle things but having cockpit on the same system makes a (poor) suitable replacement.

thats was the key.. thank you!

huh.. the guide i followed didn't mention a lemmy.hjson file.. let me start again!