I didn’t miss it, but didn’t loop back. Apologies.

I disregarded that as a solution in my response to that, because it’s not really a solution to OP’s request. Yes, they are cheaper. No, they are not functional for this need due to lack of PCIe. Running SSDs on these devices is not a feature because of the bus speed and connection limitations.

Sure it’s possible. No, it’s not functional for the needs requested here, or even a good suggestion. If somebody wanted a RELIABLE backup target using SSDs, this is the last possible scenario I would even suggest, and only if working from a box of scraps.

I’m not discounting your point that it’s cheaper at all, but it’s like…okay…if someone asked me where to get steak, because they need steak for a recipe they are cooking for dinner, my response shouldn’t be “Well, you could get steak right there, but it costs $X, and you can get Chicken wayyyyyyyy over there. It’s not beef, and it’s not what your recipe calls for, but it’s cheaper and possible to get.”

You’re asserting a position into justification for an argument that doesn’t exist. OP isn’t asking what they could theoretically run backups to. That could be an esp32 board for even cheaper. It’s also an even worse solution than an RPi. It’s just not what they’re asking for is my point.

This ONLY works at an insane scale. This will never hit the consumer market.

Again…I think you’re just missing the point here and trying to justify a worse solution without cause. A cheaper, more functional solution exists already. Trying to assert “you don’t need this or that” is not useful.

If I went to a car dealership and they told me a newer model of a car I wanted was in stock for $X, I’m not going to say “Okay,bsure, but I want the shitter version, and I’ll pay more for it.”

Makes zero sense.

Gotta say… This is not how you’d generally do any of this. Where you get this info?

Then something has changed about the local deployment and concentration of the network near you. Don’t know what to tell ya 🤷

As long as the provider is the same, and your instances are using properly using DoH or DoT, you have nothing to worry about.

If you’re super concerned though, I’d be using Mullvad over Cloudflare though. Just saying.

See my other response. This is quite normal.

Yes, that’s called Round-Robin Load Balancing.

To get more specific, your DNS provider spins up a large number of DNS resolvers out in the world on a CDN network that resolves clients to the most geographically convenient server(s) at any point in time based on the GeoIP info of your public IP.

Once you resolve one set of addresses at any given time, it caches your request, so the next time you ask these DNS servers for something you’ll get a response right back from them as fast as possible.

You constantly checking is just going to show this. It’s quite normal.

You’re going out of your way to prove some unnecessary point with this solution though.

Only the RPi5 has PCIe, first of all, and the older boards would need a slow USB interface for any type of larger storage. Then you have longevity and reliability questions because of the age of the boards…it’s just worth it.

OP wants a simple solution. RPi of any kind just ain’t it when you get down a simple list of Pros v Cons list.

Your public IP is DHCP. It changes from time to time. Nothing weird about that.

Any of the other IP’s in the DNS Servers list changing is just what you get pointed to when resolved based on your GeoIP location.

SigNoz or Uptrace are alternatives to something like DataDog, which is the route you want to go versus checking each individual machine.

You could also just use Prometheus+Grafana and build your own monitoring dashboards and alerts that way, but will be a bit more manual at first.

I might be misunderstanding, but you’re checking what exactly for DNS leaks?

If the IPs are changing, that’s not uncommon. The HOST changing would be though, like if you swapped from what you expected back to Comcast or something.

You need to get better control of your local network and not have to be paranoid about this. Static reservations for long lived hosts, your router should have a setting to override and prevent internal hosts (like guests) from sending OoB DNS requests, and any sort of VPS stack should as well.

The downvotes here are from people who have no idea what in the world actually works best, and just FEEL a certain way about things 🤣

Kinda the mantra of this entire sublem.

I’m honestly not even talking about a Minipc. I’m talking a cheap ass dual bay NAS. Let’s do a price breakdown:

• RPi5/8GB: $135
• m.2 dual hat +case with active cooling: $75 (saves a bit)
• 2x 512GB OR 1TB: $200 / $300
• 45W Power supply: $50

So at the bare minimum that’s going to be $460 or $510 for the 1TB variant per device. Then you need to fuck with all the software side of things as well.

• Synology DS223j 2xbay: $200
• 2x 4TB HDD: $200

$400 and you’re done. All the software is ready to go, you’ll have automatic rebuilds of your array if you need to swap drives, and a simple interface to work with everything in.

I’m not even here simping for Synology, because QNAP and others have similarly priced solutions. I’m here pushing for SIMPLICITY and cost effective solutions.

When you go to print, just look for the link that sends out the print job to your system settings. That bypasses the browser print stack. Probably solves your issue right there.

If you’re going for reliability, and you just want things to be simple, you probably just want to spend the money on two cheap NAS boxes, honestly. There are some caveats that come with RPi’s, and you’re unfamiliar it’s: 1) going to cost about the same, 2) be simpler to manage and upgrade, and 3) be easier to repair disk columes when the time comes.

Even if you’re just looking to make these redundant to each other, just make it simple and easy.

I print a number of label sizes on a Brother Laser as well, and have zero issues. Most of the media size and handling is done by the printer itself, and the software has little to do with it…for the most part.

1. What specific printer is this?
2. Can you upload an image of the misprint to illustrate what’s happening?
3. Have you tried forcing the system print dialog when printing versus just using whatever Firefox gives you?
4. Can you print a proper label with any other programs, or do they all behave similarly?

I think it’s more about closing a backdoor to free product that was generally out of reach for most people a few years. Free API access for devs has been a thing forever for the most part, but the barriers are now lower for people to abuse it.

Yes about profits in the sense they don’t want people getting free access to content, but I don’t think this is designed to net them a bunch of money or anything.

This is going to become more of a standard due to people vibecoding their own clients for every dumb thing.

HA is definitely the largest adopted. OpenHab is probably more geared for developers, but has a more concise and powerful automation system.

As for hardware to run it on: get a cheap n100 Minipc and be done with it. Uses 6-12W, and it’s going to miles.kore efficient for this use than a regular PC.

It’s not the CPU. All that will do is consume CPU and raise your energy bill.

1. Get some sort of resource monitor running on the machine to collect timeseries data about your procs, preferably sent to another machine. Prometheus is simple enough, but SigNoz and Outrace are like DataDog alternatives if you want to go there.
2. Identify what’s running out of control. Check CPU and Memory (most likely a memory leak)
3. Check logs to see if something is obviously wrong
4. Look and see if there is an update for whatever the proc is that addresses this issue
5. If it’s a systems process, set proper limits

In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.