There is no Cloud!
Only someone else’s #selfhosting

Pondering a NAS rather than a usb drive attached to a raspberry pi or mini pc. Any recommendations for something reliable and not too expensive? If it can run Jellyfin & Nextcloud even better. Or at least be sensibly mounted for those services to use. #selfhosting #selfhosted #nas #nextcloud #jellyfin

We were without power for ~18 hours yesterday, but I’m still determined to eventually switch hosting my personal blog over to my local Raspberry Pi Zero

https://hermes.btxx.org/

#alpinelinux #raspberrypi #selfHosting

My mastodon instance had a short downtime earlier. This was caused by a power cut.

Which in turn was caused by me stupidly cutting a power cable with my hedge trimmer (thus triggering the main fuse to trip). Oops 😬

The dangers of #selfhosting when one is a bit clumsy I suppose 😁

If you run your own local DNS servers at home, do you: (select all that apply)

Comment with your preferred DNS stack and privacy friendly DNS providers.

#FreeBSD #Linux #selfHosting #DNS

@rastilin It'd be a good move to ditch GMail. I teach people how to go about it, and I'm thinking I should publish resources towards this end. But say the word if that's something that interests you. I want to see the world break free from GMail.

The outline: Buy a domain. Rent a VPS so you have an easy static IP address with reliable and power. Spin up BIND or similar. Serve up basic records for your domain. Make a glue record and delegate your domain to your name server using your registrar's web site. Next, spin up minimal web service and get a Let's Encrypt cert. Make a cron job to renew it. Spin up Postfix and Dovecot. Have Postfix use Dovecot auth and have them both use your Let's Encrypt cert. Add cron jobs to restart them when certs renew. Test. Now add MX and SPF records to your DNS. Consider spinning up DKIM, and adding records for that and DMARC to your domain. Consider procmail or maildrop for filtering and sorting. Consider RBLs, SpamAssassin, SpamProbe, and similar. Decide how you want to back the server up. Consider redundancy.

#selfhosting

TFW you realize you've had your MX entry set wrong for over a month.

Yet somehow I've still been getting (some) mail? 🤔

#SelfHosting

Alright folks, it's time for me to zero in on my self-hosted RSS aggregator setup.

Priorities: ease of maintenance, support for a variety of readers (or at least Capy)

I know people have opinions. Tell me them!

#rss #selfhosted #selfhosting

Is there anyone out there running an AMD 5650GE based system running Linux or BSD?

Can you tell us your CPU and GPU idle power numbers as displayed in btop?

Maybe this is an "easy button" of sorts to reduce power on an existing AMD AM4 system without going through the machinations of new mobo, ram, etc., etc. Get most of the way there?

#Linux #RunBSD #AMD #5650GE #PowerConsumption #Power #HomeLab #SelfHosting #SelfHosted #SOHO

Is there anyone out there running an AMD 5825U based system running Linux or BSD?

Can you tell us your CPU and GPU idle power numbers as displayed in btop?

#Linux #RunBSD #AMD #5825U #PowerConsumption #Power #HomeLab #SelfHosting #SelfHosted #SOHO

Looks like it has basic Markdown -> HTML converting. Neat.

That

works

for

me.

• (I'm not gonna show it all)

And of course, no post or poll length limit :)

#Snac #SnacServer #SelfHosting

I'm currently trying to wrap my head around setting up Radicle. The decentralization is kind of confusing when I'm used to centralized git hosting.

I have a selective seed node on my public-facing server, along with the radicle-httpd service which is reverse-proxied via Caddy. As I understand, this means I can seed (replicate) selected public repos to keep them in sync with the network. And the radicle-httpd service makes them available in an HTTP JSON API(?).

I also have a regular node on my workstation, with my dotfiles repository added to it for testing purposes.

I'm not sure how a regular node differs from a seed node. Do regular nodes also seed repositories like a seed node does, while a seed node's purpose is solely for seeding? If regular nodes also seed, is there still any reason to run a seed node separately?

I'd also like to get the radicle-explorer web UI set up on my public-facing server via reverse proxy. I'm not sure how that fits in with the rest of this. Does the radicle-explorer have to point to my seed node's HTTP endpoint to display the repositories I'm seeding?

I might have to go bother people in the Zullip chat.

#radicle #git #selfhosting

Almost done my custom recycled component OPNSense router. Final missing piece is this 2" PCIe riser. I may hit MicroCenter today. #opnsense #selfhosted #selfhosting #homekit

Alt...

The image is a close-up photograph showing a stainless steel ruler positioned vertically inside a computer case to measure the clearance of an internal component. The ruler is placed between a grey metal power supply unit on the left and a green PCI Express expansion card on the right. The expansion card features gold-plated connection fingers at the bottom and a large, black, finned aluminum heatsink on top, with the text "PCI EXPRESS" and "23.0" clearly printed on the green circuit board. According to the ruler's inch markings, the height of the green PCB aligns almost exactly with the two-inch mark. Below the card, the black PCIe slot on the motherboard is visible, along with the printed text "Designed in Taipei PCI Express." The background is softly out of focus, showing a blue-handled screwdriver and a teal-colored surface on a wooden desk, suggesting an active hardware modification or repair project.

Alt...

The image shows an open, small-form-factor black computer case resting on a wooden desk, revealing its internal components in the middle of a build or repair. Inside the case, a silver power supply is mounted on the left, while the opening is dominated by a prominent green expansion card featuring a large, black, finned heatsink. A tangle of multicolored power cables in red, yellow, and orange, along with several black SATA data cables, snakes through the compact interior. To the left of the case, an OCZ Vertex 3 solid-state drive (SSD) lies flat on the desk, connected to a power and data cable. A blue-handled Phillips-head screwdriver labeled "#1 MADE IN USA" rests next to the SSD. The background is cluttered with a messy arrangement of blue and white networking cables and a portion of a teal-colored mousepad in the upper right corner. The black case itself features a mesh ventilation pattern on its side and two blue USB 3.0 ports on what appears to be the front-facing panel.

Pleased to announce another edition of Cloudbreak, taking place May 28.

For those that don't know already, this is a 6hr fully-supported live training opportunity leading participants with no prior experience in system administration through the process of building up their own #sovereign & secured cloud server.

Hosted in the EU on renewable energy, the finished server also offers both Zoom & Google Docs alternatives.

Info & signup here:

https://courses.nikau.io/cloudbreak

#selfhosting

Alt...

The title image for the Cloudbreak training, featuring that word in white and in caps, in a sans serif typeface, against a grayscale photograph of a cumulus cloud structure

Today in #selfhosting fun. I have a mail server that's been in place for years and hasn't had any noticable problems, but today I sent the same email from two different addresses to hotmail. Both had SPF, DKIM, DMARC and the same outbound IP address. One was delivered and one went to junk. Headers on the latter show a spam score of 5 (which is sufficient for it to be diverted):

X-MS-Exchange-Organization-SCL: 5

I tried running it through https://github.com/mgeeky/decode-spam-headers but that didn't give any clues

Hi folks! I would love to hear about the non-standard physical #homelab #selfhosting security measures you've taken. From alarms to boobytraps, from customized IKEA boxes to reinforced closets. The crazier the better!

One requirement: you need to have it implemented (at some point in the past or currently). No concepts that never left the design table please.

What bring you to the path of self-hosting?

I guess for me is that because in the mid 2000's the free hosting services were quite terrible and I get my hands on the old family computer and some documentation about Debian.

#selfhosting

Looks like not only backups but also my obsession^Wpassion to write detailed entries to my "selfhosting journal" pays back. Any change, I made in my main home server, has a date and a detailed description of changes made. Also, the process of #NetBSD installation and service installation is documented too, alongside with documented list of running services, opened ports, cronjobs, etc.

At one bad day, my main server started to hangup at near 18:00 and at nea 08:00. There weren't any cron (or any another) jobs at this time. In the logs and monitoring the problems with mosquitto (MQTT server) were visible — somehow it eats at near 100% of CPU, then monit restart it, then things become working, then (after some time) the server hangs completely. Investigation showed that write to my second ZFS disk (where the PostgreSQL DB lives) were extremely slowed, so ZFS panicked, crashed and crashes the kernel

[ 204836.661198] wd0d: device timeout writing fsbn 123148477 of 123148477-123148478 (wd0 bn 123148477; cn 122171 tn 1 sn 46), xfer 38, retry 1
[ 204863.837664] wd0: soft error (corrected) xfer 38
[ 206810.672323] wd0: autoconfiguration error: wd_flushcache: status=0x5128<TIMEOU>
[ 212327.420695] SLOW IO: zio timestamp 211326864412007ns, delta 1000556283358ns, last io 211280726737075ns
[ 212327.420695] panic: I/O to pool 'zfs' appears to be hung on vdev guid 1299234741086050345 at '/dev/wd0'.
[ 212327.420695] cpu0: Begin traceback...
[ 212327.420695] vpanic() at netbsd:vpanic+0x183
[ 212327.420695] panic() at netbsd:panic+0x3c
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x15e
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x31
[ 212327.420695] spa_deadman_wq() at zfs:spa_deadman_wq+0xe0
[ 212327.430704] workqueue_worker() at netbsd:workqueue_worker+0xef
[ 212327.430704] cpu0: End traceback...

At the same time, I hear a strange metal noises from server at near 08:00 too, so the destiny of second drive was specified.

The server restoration will take some time, but since anything were written in the log file, I'm able just to replay some actions and get all systems up as soon as possible

#selfhosting #HomeServer

Alt...

Emacs buffer with journal entries (in OrgMode) related to the administrative actions in the server.

Alt...

Emacs buffer with description of NetBSD installation process on the main server and with lists of TODO items, services, opened ports, etc.

Alt...

EGA colored photo of a 2.5 inches HDD

I've been running two degraded ZFS arrays for the last few weeks (Debian host).

Yeah, I know. Whatevs.

One of the pools was basically "scratch" backup space and one of the spindles died (breaking the utility of the mirror). Pulled the drive, wiped the remaining, put back in service with minimum fuss as a single drive. I'll throw another spindle at it when drive prices drop again.

The other array had the SSD cache die and it's been chugging along fine ever since. Not a big deal, but from a "experience" point of view it "feels slow" like a working md array.

New SSD arrived in the mail so that'll get sorted sometime today/tomorrow.

So, what's this post about?

Linux peeps, if you are thinking about md arrays, just stop, take the time, and throw 'yer leg over the zfs horse. It's worth it.

#Linux #RunBSD #zfs #md #mdadm #raid #homelab #SelfHosted #SelfHosting

Here's something really useful I've found.

One of the great things about the Fediverse is being able to follow hashtags.

But.

If someone puts up a post using that hashtag, and no-one on your instance follows that person or anyone who shares it, it won't appear in your feed.

This is particularly common if you're on a small or single-user instance.

Here's the solution.

First, follow @_followback

It will follow you back.

And then tags.pub bot then reshare all of your posts that use hashtags.

So if you do a post with the hashtag #Fediverse, then @fediverse will share your post.

Here's where the magic happens.

The tags.pub bot will do the same thing to everyone else who follows that followback account.

So if you follow @fediverse, then you'll get a feed of everyone who uses #Fediverse on the Fediverse.

And you'll see their posts even if no-one on your instance follows them.

And it works for all hashtags.

Just put the name of the hashtag, followed by @tags.pub

So @tech follows all posts using #tech, for example.

Or @news follows all posts using #news

#relay #relays #selfhosted #selfhosting #Mastodon #feditip #feditips #fedihelp

New post:

"A newbie's guide to self-hosting with #YunoHost. Part 5: Upgrades & Maintenance"

Not exactly the most exciting post I have ever written, but system maintenance is so essential.

And spoiler alert: thanks to a botched #PeerTube upgrade I discovered the wonders of #tmux (thank you @teapot_ben and @drfyzziks for recommending it!)

🔗 : https://blog.elenarossini.com/a-newbies-guide-to-self-hosting-with-yunohost-part-5-upgrades-maintenance/

#SelfHosting #MySoCalledSudoLife #DigitalSovereignty

@mastodonmigration We should probably be pushing things like #Friendica and #Pixelfed and other free Fediverse servers over things like Ghost.

Even pushing free wiki software would be a win over a proprietary platform.

But yes, escaping commercial platforms is a critically important idea, and the first step to #selfhosting.