I didn’t even bother to look since, well, I just moved to compose files sitting in a folder instead but uh, $150? Seriously?

That’d be the most expensive bit of all of my stacks, including hosting and power costs.

I mean, if it were 1994 I’d agree that maybe we shouldn’t hop on this newfangled email thing, but uh, a bit’s happened in the last 30 years y’know?

Though I’d take paid-for school and universal health care and a social safety net over being able to get an email from my doctor so, uh, tradeoffs I guess?

Nah, was mostly just making a joke about the other old tech that Japan was notorious for still using.

Also, I’m really confused WHY eFax is fine but email isn’t? I mean, once you lose the verifiability of the phone logs that say your doctor called you at 2:15pm and send 3 pages of shit, uh, you might as well just email a PDF. (Note: I’m in the US and the ‘verifiable transmission’ thing was why/how we did it for a long time, but that died in about 10 seconds when someone figured out that email was cheaper.)

If all you need is for it to go ‘I turned on the light’, they’re fine. I wouldn’t expect to use them for anything more detailed or music-oriented.

I played with a couple and went with searxng, because I was happiest with the results I was getting back from it compared to the other ones (or, for that matter, a normal Google or Bing search).

I’ve accomplished this with the Atom Echo and they work… fine?

The speaker is essentially inaudible, but the mic works well enough for me to just yell at HomeAssistant to do things.

And hey, can’t beat the size/price/power footprint and the deployment with ESPHome takes like, 30 seconds.

Did they send everyone a fax to let them know that floppies are no longer used?

I have watchtower configured to update most, but not all containers.

It runs after the nightly backup of everything runs, so if something explodes, I’ve got a backup that’s recent and revertible. I also don’t update certain types of containers (databases, critical infrastructure, etc.) automatically so that the blast radius of a bad update when I’m not there doing it is limited.

In the last ~3 years I’ve had exactly zero instances of ‘oops shit’s fucked!’, but I also don’t run anything that’s in a massive state of flux and constantly having breaking changes (see: immich).

As someone with recent platforms from both Intel and AMD, man, I do not like my 7700x’s platform.

It’s just sporadically unreliable: sometimes it posts, sometimes it doesn’t, sometimes the memory decides it needs to reset back to jedc standards instead of the expo settings, sometimes it doesn’t. Even a successful POST can take upwards of a minute sometimes, and the system may or may not reset in the middle of it, resulting in two extended delays.

Perfectly stable once the OS gets booted (memtest is fine, prime95 is fine and it boosts like crazy up to about 5.5ghz all-core), but getting there is such a pain on occasion.

I realize more than a little of this is probably attributable to the motherboard manufacturer/efi settings, but the last few AMD platforms I’ve had are just wonky and less than 100% reliable compared to the last several Intel ones, which have typically just worked, correctly, every time.

Yeah, exactly: if you know how it works, then you know how to fix it. I don’t think you need a comprehensive knowledge about how everything you run works, but you should at least have good enough notes somewhere to explain HOW you deployed it the first time, if you had to make any changes as well as anything you ran into that required you to go figure out what the blocking issue was.

And then you should make sure that documentation is visible in a form that doesn’t require ANYTHING to actually be working, which is why I just put pages of notes in the compose file: docker doesn’t care, and darn near any computer on earth made in the last 40 years can read a plan text file.

I don’t really think there’s any better/worse reverse proxy for simple configurations, but I’m most familiar with nginx, which means I’ve spent too long fixing busted shit on it so it’s the choice primarily because, well, when I break it, I already probably know how to fix what’s wrong.

I’m a grumpy linux greybeard type, so I went with… plain text files.

Everything is deployed via docker, so I’ve got a docker-compose.yml for each stack, and any notes or configuration things specific to that app is a comment in the compose file. Those are all backed up in a couple of places, since all I need to do is drop them on a filesystem, and bam, complete restoration.

Reverse proxy is nginx, because it’s reliable, tested, proven, works, and while it might not have all those fancy auto-config options other things have, it also doesn’t automatically configure itself into a way that I’d prefer it didn’t, either.

I don’t use any tools like portainer or dockge or nginx proxy manager at this point, because dealing with what’s just a couple of config files on the filesystem is faster (for me) and less complicated (again, for me) than adding another layer of software on top (and it keeps your attack surface small).

My one concession to gui shit for the docker is an install of dozzle because it certainly makes dealing with docker logs simple, and it simplifies managing the ~40 stacks and ~85 containers that I’ve got setup at the moment.

Oh sorry; my goal here was for individual metering. I’ve got an Enphase solar system, so the Envoy is already doing whole-house monitoring.

I’d like to be able to identify and ultimately be able to lower my load to stay under what the solar panels are generating, but that needs data I mostly don’t have, and specific equipment to actually turn things on and off.

Yeah the plan was for the in wall relays. I’m in the US and if I read the specs properly they’ll do 16a at 120v, which is also where my breakers would trip anyways so probably shouldn’t matter.

Because most poeple don’t care and just want to play the latest $GAME_NAME_HERE?

And I mean, Nintendo has already sued people into essential slavery and nobody said shit, so I don’t know what the fuck will get people’s attention.

Honestly it feels like they’re trying to get away from being just a file sync platform, and are pushing for more corpo feature sets to compete with gsuite or O365.

Which I mean is great: that’s exactly what I needed and why I use it - it let me ditch almost all of my Google services and move it all to selfhosted.

But I bet it also causes incentives to prioritize fixes and features that are focused on that, and pushes stuff like ‘make the android sync app work like every other file sync app in history’ to the bottom of the list.

Nope, that curl command says ‘connect to the public ip of the server, and ask for this specific site by name, and ignore SSL errors’.

So it’ll make a request to the public IP for any site configured with that server name even if the DNS resolution for that name isn’t a public IP, and ignore the SSL error that happens when you try to do that.

If there’s a private site configured with that name on nginx and it’s configured without any ACLs, nginx will happily return the content of whatever is at the server name requested.

Like I said, it’s certainly an edge case that requires you to have knowledge of your target, but at the same time, how many people will just name their, as an example, vaultwarden install as vaultwarden.private.domain.com?

You could write a script that’ll recon through various permuatations of high-value targets and have it make a couple hundred curl attempts to come up with a nice clean list of reconned and possibly vulnerable targets.

Just tested that and uh, yeah, what the hell? Not something my workflows need, but that’s a shocking oversight considering damn near everything else 100% does that.

That’s the gotcha that can bite you: if you’re sharing internal and external sites via a split horizon nginx config, and it’s accessible over the public internet, then the actual IP defined in DNS doesn’t actually matter.

If the attacker can determine that secret.local.mydomain.com is a valid server name, they can request it from nginx even if it’s got internal-only dns by including the header of that domain in their request, as an example, in curl like thus:

curl --header 'Host: secret.local.mydomain.com' https://your.public.ip.here -k

Admittedly this requires some recon which means 99.999% of attackers are never even going to get remotely close to doing this, but it’s an edge case that’s easy to work against by ACLs, and you probably should when doing split horizon configurations.

Ugh, not the best marketing for Nextcloud to have a public share not work, lol. It seems like 25% of people just can’t see them but they work for everyone else so who knows.

Anyway, have a pastebin instead: https://pastebin.com/zPyvgxYX

Not saying you’re wrong, but what doesn’t work right? I haven’t noticed any behavior that seems wrong to me. Usually interact with nextcloud via the nextcloud section that gets added by the client in the file picker/file manager on the OnePlus Nord I’m using.