I unretired an old racknerd vps and got it running on there… works great!

Just need to now figure out how to move it to something that can actually cope with it lol…

Any ideas how to backup an instance and move it?

I guess it would be a matter of getting a new VPS, pointing my domain to it, reinstalling and then moving over the .live folder?

I tried to run your script on a proxmox Debian 12 lxc but i hit a few issues… i already run a reverse proxy etc…

So… what VPS would you recommend to run this on ? It will literally only be for myself to maintain my subscriptions and have a singular account…

Are you able to point me to where i can find the cache options? I’m also new to Caddy and want to make sure i’m not making any silly mistakes.

I had it running but it didn’t seem to be issuing wildcards… but afterwards i realised that whilst i had told it to use the cloudflare API… i don’t think at any stage i’d actually told it to issue wildcards… i guess i need to figure out how to do that…

I’m questioning my need though really… i think the docs say it’s not recommended unless you’re dealing with thousands of subdomains…

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

Thank you for this… i need to take some time to read it more thoroughly… though your approach with Docker though will likely make a lot more sense for my environment.

If the download actually works… which i’ll try in a minute… how can i move from my apt installed version to using this binary?

Edit… so i’ve ended up with a file with no extension…

caddy_linux_amd64_custom

my experiment was largely a knee jerk reaction to things going on over at reddit…i think there are plenty more people more capable than i am of assisting in growing this environment… once i can contribute by simply offering up compute i’ll be back… for now I’ll have to enjoy from afar.

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.

I’ve been using NPM for years… but since 2.10.3 broke SSL certificates and there’s been literally no interest from JC21 to fix the problem (there’s a PR ready to go) i’ve been forced to look elsewhere and have settled on caddy for now…

this was also on my list of questions… i’ve seen nothing and i need to point things to smtp2go… but at the moment i think i’m going to hold off… i don’t have the time or resources to be an early adopter…

thats was the key… thank you!

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

They should of been… i’m running caddy so it’s pretty turn key but i’ll give it another go.