🇨🇦
That is one beefy fan for a rpi.
I’ve just got a case similar to this; but all snap together, no screws:
The fan runs off the pin headers. Meant for 5v, but I use the 3.3v line to run it a little quieter/slower.
Even that makes a good 10°c difference.
I’m running ~30 containers, but they don’t typically all get new updates at the same time.
Updates are grabbed nightly, and I think the most I’ve seen update at once is like 6 containers.
Could be a problem for setting up a new system, or experimenting with new toys.
What is the api error (click on the red box)?
Likely unable to reach the host provided.
In paperless’ docker compose, set ‘container_name:’ to ‘paperless’ or similar, then use that same name as the host given to homepage:
widget: type: paperlessngx url: "http://paperless:8000/" key: [key]
“code”: “ETIMEDOUT”
Homepage is unable to reach the host you gave it. IP/hostname changed.
Don’t use the IP of the container, use its name (which you should set in paperless’ compose file: ‘container_name: paperless’)
I’ve been pretty lazy with this.
I used to use my hotmail account, but they disabled password auth for smtp and many programs dont support 0auth2.
With that change, I just moved to using gmail. You’ve gotta create an App Password for smtp, but other wise works fine.
I’ve just been too lazy to move out of gmail+hotmail. Maybe one day
They make modern versions for cats. But putting your baby in one…?
Maybe the parents weren’t watching the kid close enough and they climbed in there on their own.
Yeah; rising heat, plus the extra insulation of neighbours sharing walls. It’s uniform enough that the walls/floor doesn’t feel any warmer than usual, but it makes a difference.
Are you in a house or an apartment?
I’m on the fifth floor and pretty much never have to run my heat.
deleted by creator
Little of column A little of column B.
I use pihole on the LAN, then upstream is cloudflared translating DNS to DOH using NextDNS as the primary and Quad9 as the fallback.
Looking at the last 24hrs; my whole LAN network has made 91k DNS requests, 14.5% of that being passed to the upstream (the rest is locally cached responses or blocked) so ~12.7k served by NextDNS. When/if that 300k limit is reached, cloudflared will just fallback to Quad9.
With this I get the blocking from NextDNS as well as whatever additional lists I want to use; plus pihole serves local only records for self-hosted services and fixed names for LAN devices (I find standard broadcasted hostnames unreliable at best).
It’s really nice for random browsing/apps. Games, free tools, general web browsing; none of it loads ads.
Some mobile games will even attempt to load ads, fail, then give you the reward for ‘watching’ the ad.
It also stops devices from phoning home to upload telemetry and blocks known malware domains. (depends on the lists you use, heres a source for some lists)
They’ve added a bit more info to the query log, when you click on individual items.
It’s still not a native feature, but; You can add DOH using cloudflared, incl configuring which upstream(s) to use (you don’t have to use cloudflare itself, just the tool).
There’s even a docker version.
I’m using orbital-sync, it’s not currently compatible with v6; but that’s what they’re working on now.
Hopefully not too long.
Nice!
Upgrade went smoothly on docker, with some neat new additions. There’s new filter options in the query log. There’s a bunch of new metrics under Settings > System (enable ‘advanced’ in the top right). And overall there seems to be many more settings available under System > All Settings. For example you can easily set the TTL for blocked responses (this was a setting burried in config files before, I was looking for it like 2 weeks ago).
If you don’t use/set a password in pihole, or you set one via .env variables; you’ll probably have to reset it with the command:
sudo docker exec <container_name> sudo pihole setpassword <your password here>
(empty for no password)
/edit; seems that was a temporary solution.
These env variables have changed:
Was:
webpassword=<your password>
DNS1=<upstream1>
DNS2=<upstream2>
Now:
FTLCONF_dns_upstream=<upstream1;upstream2>
FTLCONF_webserver_api_password=<your password here>
I run Borg nightly, backing up the majority of the data on my boot disk, incl docker volumes and config + a few extra folders.
Each individual archive is around 550gb, but because of the de-duplication and compression it’s only ~800mb of new data each day taking around 3min to complete the backup.
Borgs de-duplication is honestly incredible. I keep 7 daily backups, 3 weekly, 11 monthly, then one for each year beyond that. The 21 historical backups I have right now RAW would be 10.98tb of data. After de-duplication and compression it only takes up 407.98gb on disk.
With that kind of space savings, I see no reason not to keep such frequent backups. Hell, the whole archive takes up less space than one copy of the original data.
ACME.sh? I love that little tool.
Cert renewal via DNS-01, independent of any other services or ports. Set it up like 7 years ago and haven’t had to touch it since.
I’m having some crazy deja vu reading this 5 comment thread…
It’s been a few months since I visited one of these general “how’s everyone’s week been” threads, but the last time I did someome else was talking about just having setup paperless, struggling to get their scanner to print to ftp, thinking about email, someone had suggested wireshark; it feels like I just re-read that exact conversion again, but they’re new comments…
Freaky.
I set it up a couple weeks ago. It’s alright; facial recognition works pretty well, the files are easy to manage, and setup was pretty straightforward (using docker).
Searching for images works fairly well, as long as you’re searching for content and not text. Searching ‘horse’ for example does a pretty good job showing you your pictures of horses, but often misses images containing the word horse. Not always, but it’s noticeable to me.
The mobile apps work well too; syncing files in the background as they appear, optionally creating albums based on folders. Two things I find missing though are the ability to edit faces/people in an image (you’ve gotta do that from a browser), and the ability to see what albums an image is in and quickly navigate to one.
It’s a developing project that’s well on it’s way. A good choice imo.
System updates have been a faff. I’m 'ssh’ing over tailscale. When tailscale updates it kicks me out, naturally. Which interrupts the session, naturally. Which stops the update, naturally.
Have a look at Screen. You can create a persistent terminal to start your update in, disconnect (manually or by connection loss), and resume the session when you reconnect, with it having completed the update while you were gone.
Copy of my comment in c/apple:
Honestly I think this is the right move.
Pull the feature and tell the public that the government won’t permit the public to secure their own data.
“I have security and privacy features for you, but your government won’t let you use them”
Set the public against this overreach.