<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Opensearch on Mike Bell - Blog &amp; Stuff</title><link>https://mikebell.io/tags/opensearch/</link><description>Recent content in Opensearch on Mike Bell - Blog &amp; Stuff</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>hello@mikebell.io (Mike Bell)</managingEditor><webMaster>hello@mikebell.io (Mike Bell)</webMaster><copyright>© 2026 Mike Bell</copyright><lastBuildDate>Mon, 12 Jan 2026 19:41:38 +0000</lastBuildDate><atom:link href="https://mikebell.io/tags/opensearch/index.xml" rel="self" type="application/rss+xml"/><item><title>Homelab Update January 2026</title><link>https://mikebell.io/posts/homelab-update-january-2026/</link><pubDate>Mon, 12 Jan 2026 19:41:38 +0000</pubDate><author>hello@mikebell.io (Mike Bell)</author><guid>https://mikebell.io/posts/homelab-update-january-2026/</guid><description>
&lt;p>Happy new year homelabbers! I&amp;rsquo;m cheating a bit and rolling some of the work I got done in December 2025 into this update. I want to say my homelab is pretty boring now it just works which is awesome, only minor tinkering is required these days so I&amp;rsquo;ve decided to focus on observability for a bit. Knowing when and what things have gone wrong was sorely missing so I&amp;rsquo;ve finally gotten round to sorting a lot of that out which I&amp;rsquo;ll detail in a section below.&lt;/p>
&lt;h2 class="relative group">Chicken/Egg Docker Woes
&lt;div id="chickenegg-docker-woes" class="anchor">&lt;/div>
&lt;span
class="absolute top-0 w-6 transition-opacity opacity-0 ltr:-left-6 rtl:-right-6 not-prose group-hover:opacity-100">
&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700 !no-underline" href="#chickenegg-docker-woes" aria-label="Anchor">#&lt;/a>
&lt;/span>
&lt;/h2>
&lt;p>Ever since I migrated away from Ubuntu to Debian I&amp;rsquo;ve been unable to restart the VM and have all the containers come up again. Even after going through every compose file and making sure that &lt;code>restart: unless-stopped&lt;/code> was set. It&amp;rsquo;s been driving me nuts that this has been happening. Well I finally figure out what was wrong. The hint was that the only container to consistently come back up was &lt;code>fluent-bit&lt;/code>. When I migrated to Debian I decided to improve my logging so set up fluent-bit and OpenSearch. I also set the docker logging driver to fluent-bit. Can you spot the issue yet? When docker comes up all the other containers fail over refusing to connect to the fluent-bit socket, pretty obvious now, if docker isn&amp;rsquo;t running the fluent-bit container isn&amp;rsquo;t running so how can docker connect to the fluent-bit container? I could keep this sentence recursive. Eventually the fluent-bit container comes up but the rest of them containers have already stopped, restarting them all brings them up fine. I removed the fluent-bit container and ran it as a systemd unit instead. Docker restarts are perfectly fine now.&lt;/p>
&lt;h2 class="relative group">Uptime Kuma and Gotify
&lt;div id="uptime-kuma-and-gotify" class="anchor">&lt;/div>
&lt;span
class="absolute top-0 w-6 transition-opacity opacity-0 ltr:-left-6 rtl:-right-6 not-prose group-hover:opacity-100">
&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700 !no-underline" href="#uptime-kuma-and-gotify" aria-label="Anchor">#&lt;/a>
&lt;/span>
&lt;/h2>
&lt;p>A while ago I did have Uptime Kuma as part of my homelab but removed it since everything was on one physical server so if there was a huge problem UK would never pick it up since it was probably down as well. I&amp;rsquo;m now hosting it on my Media Server which while still a single point of failure it&amp;rsquo;s physically separate from my main homelab. As well as this I setup Gotify to send me notifications when services go down, these go straight to my phone so I can get near realtime downtime notifications. I&amp;rsquo;ve had to tune the thresholds in UK for some of my applications since some are less reliable than others (the ones not on my infra!).&lt;/p>
&lt;h2 class="relative group">Wireguard on Android
&lt;div id="wireguard-on-android" class="anchor">&lt;/div>
&lt;span
class="absolute top-0 w-6 transition-opacity opacity-0 ltr:-left-6 rtl:-right-6 not-prose group-hover:opacity-100">
&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700 !no-underline" href="#wireguard-on-android" aria-label="Anchor">#&lt;/a>
&lt;/span>
&lt;/h2>
&lt;p>For about 24 hours I lost all network connectivity on my phone (Pixel 7 Pro). It turns out that wireguard had crashed and completely nuked connectivity. After rebooting my phone it worked again. No idea why this happened but it was pretty annoying. I usually have my home wireguard VPN connected 24/7 even when on my home wifi but because my phone is silent all the time I didn&amp;rsquo;t notice, I guess I didn&amp;rsquo;t need to use my phone at all that day.&lt;/p>
&lt;p>That&amp;rsquo;s it for this update, there&amp;rsquo;s still work in my todo list that I need to get around to but that can wait for a bit.&lt;/p>
&lt;p>Thanks for reading via RSS!&lt;/p>
&lt;p>Send me a message on &lt;a href="https://remotelab.uk/mikebell">Mastodon&lt;/a> or &lt;a href="mailto:hello@mikebell.io">email me&lt;/a>&lt;/p></description></item></channel></rss>