Category: Homelab & Self-Hosting

How to Run Immich for Self-Hosted Photo Storage: Your Ultimate Guide

Tired of subscription fees and privacy concerns with cloud-based photo storage? Ready to take back control of your precious memories? If you’re a self-hosting enthusiast or just dipping your toes into the homelab world, Immich is a name you absolutely need to know. It’s a powerful, open-source, self-hosted photo and video backup solution that offers a remarkable alternative to giants like Google Photos or Apple Photos. At OpenClaw Resource, we believe in empowering you with the knowledge to build your own digital fortress, and Immich is a cornerstone of a robust self-hosted media strategy.

This comprehensive guide will walk you through everything you need to know to get Immich up and running, ensuring your photos are safe, private, and entirely under your command.

Why Choose Immich for Self-Hosted Photo Storage?

Before we dive into the “how,” let’s quickly discuss the “why.” Immich isn’t just another photo gallery. It’s designed to be a full-featured replacement for commercial cloud services, offering:

• Complete Control: Your data stays on your hardware, in your home. No third-party access, no data mining.
• Feature Parity (and Beyond): Immich boasts AI-powered object and facial recognition, automatic backup from mobile devices, shared albums, timeline view, map view, and even a robust API for integrations.
• Open Source: The community-driven nature means constant development, transparency, and a vibrant support network.
• Cost-Effective: Beyond your initial hardware investment, there are no recurring fees for storage.

Prerequisites: What You’ll Need

To successfully run Immich, you’ll need a few essential components. Don’t worry, most homelabbers will already have these or similar setups.

• A Server: This can be anything from a Raspberry Pi 4 (for smaller libraries and lighter usage) to a more robust mini-PC like an Intel NUC, or a dedicated server running Proxmox or ESXi. The key is sufficient CPU power for AI tasks and enough RAM. We recommend at least 8GB RAM for a smooth experience.
• Operating System: A Linux-based OS is preferred. Ubuntu Server, Debian, or your favorite distribution will work perfectly.
• Docker and Docker Compose: Immich is containerized, making deployment incredibly straightforward. Ensure you have Docker and Docker Compose installed on your server.
• Ample Storage: Photos and videos consume significant space. Plan for plenty of HDD or SSD storage. Consider a RAID setup (e.g., RAID 1 or RAID 5/6) for data redundancy using tools like TrueNAS SCALE or a software RAID solution.
• Networking Basics: A basic understanding of networking, including port forwarding if you plan to access Immich from outside your home network (though we recommend a VPN for security).

Step-by-Step Immich Deployment with Docker Compose

This guide focuses on the most common and recommended deployment method: Docker Compose.

1. Prepare Your Server Environment

First, ensure your server is up to date and has Docker and Docker Compose installed. If you’re new to Docker, here’s a quick way to install it on Ubuntu:

sudo apt update
sudo apt upgrade -y
sudo apt install ca-certificates curl gnupg lsb-release -y
sudo mkdir -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-compose-plugin -y
sudo usermod -aG docker $USER # Add your user to the docker group
newgrp docker # Apply group changes immediately

Verify installations:

docker --version
docker compose version

2. Create Your Immich Directory and Docker Compose File

Choose a location on your server for your Immich configuration and data. We recommend creating a dedicated directory:

mkdir ~/immich
cd ~/immich

Now, create a docker-compose.yml file. You can find the latest official docker-compose.yml on the Immich GitHub repository. For simplicity, here’s a basic structure you can adapt. Use nano docker-compose.yml to create and edit the file:

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:release
    command: ["start-server.sh"]
    volumes:
      - immich_data:/usr/src/app/upload
      - /path/to/your/photos:/mnt/photos # Mount an external drive for existing photos
    env_file:
      - .env
    ports:
      - 2283:3001 # Immich web UI
    depends_on:
      - immich-redis
      - immich-database
      - immich-microservices
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-microservices:release
    command: ["start-microservices.sh"]
    volumes:
      - immich_data:/usr/src/app/upload
      - /path/to/your/photos:/mnt/photos # Mount an external drive for existing photos
    env_file:
      - .env
    depends_on:
      - immich-redis
      - immich-database
    restart: always

  immich-web:
    container_name: immich_web
    image: ghcr.io/immich-app/immich-web:release
    environment:
      - VITE_SERVER_URL=http://localhost:2283 # Adjust if using a reverse proxy
    ports:
      - 3000:3000 # Immich web client
    restart: always

  immich-redis:
    container_name: immich_redis
    image: redis/redis-stack-server:latest
    command: redis-server --requirepass ${REDIS_PASSWORD}
    volumes:
      - immich_redis:/data
    restart: always

  immich-database:
    container_name: immich_database
    image: postgres:15-alpine
    env_file:
      - .env
    volumes:
      - immich_database:/var/lib/postgresql/data
    restart: always

volumes:
  immich_data:
  immich_redis:
  immich_database:

Important Customizations:

• /path/to/your/photos: Change this to the actual path on your server where your existing photos are stored, or where you want to store new uploads. This is crucial for Immich to access your media.
• Ports: If port 2283 or 3000 are in use, change them to available ports.

3. Create Your .env File

Next, create a .env file in the same directory (nano .env) to store environment variables, especially sensitive ones like passwords. Replace the bracketed values with strong, unique passwords.

DB_HOSTNAME=immich-database
DB_USERNAME=postgres
DB_PASSWORD=[YOUR_POSTGRES_PASSWORD]
DB_DATABASE_NAME=immich
DB_PORT=5432

REDIS_HOSTNAME=immich-redis
REDIS_PASSWORD=[YOUR_REDIS_PASSWORD]
REDIS_PORT=6379

JWT_SECRET=[YOUR_JWT_SECRET]

Save both files.

4. Deploy Immich

With your docker-compose.yml and .env files ready, navigate to your ~/immich directory and run:

docker compose up -d

This command will download all necessary Docker images and start the Imm

Frequently Asked Questions

Building a homelab? See our roundup of the best mini PCs for homelab use →

Unleash a Cleaner Internet: Your Comprehensive Guide to Setting Up Pi-hole for Ad Blocking

Tired of intrusive ads cluttering your browsing experience, slowing down your network, and even posing security risks? Welcome to the world of Pi-hole! At OpenClaw, we’re all about empowering you with self-hosting solutions and homelab wizardry. Today, we’re diving deep into Pi-hole, a fantastic open-source tool that acts as a DNS sinkhole, effectively blocking ads and trackers across your entire network. Imagine a smoother, faster, and more private internet experience for every device in your home – that’s the Pi-hole promise.

Setting up Pi-hole might sound intimidating if you’re new to the homelab scene, but trust us, it’s a rewarding project that’s well within reach. This comprehensive guide will walk you through every step, from choosing your hardware to configuring your network, ensuring you’re blocking ads like a pro in no time.

What You’ll Need: The Essential Pi-hole Toolkit

Before we begin the setup process, let’s gather our ingredients. The beauty of Pi-hole is its minimal hardware requirements, making it an ideal entry point into self-hosting.

• A Dedicated Device: The most popular choice, and what we’ll focus on, is a Raspberry Pi. A Raspberry Pi 3 Model B+ or a Raspberry Pi 4 (any RAM variant) is more than sufficient. You can also run Pi-hole on an old PC, a virtual machine (like with Proxmox VE), or even a small SBC like an Orange Pi. For beginners, the Raspberry Pi offers the best balance of cost, power efficiency, and community support.
• MicroSD Card: A high-quality 8GB or 16GB MicroSD card (Class 10 or higher) for your Raspberry Pi. We recommend reputable brands like SanDisk or Samsung for reliability.
• Power Supply: A compatible USB-C (for Pi 4) or Micro-USB (for Pi 3B+) power supply. Ensure it provides adequate amperage (e.g., 5V 3A for Pi 4) to prevent stability issues.
• Ethernet Cable: For a stable, wired connection, which is highly recommended for your Pi-hole.
• Internet Connection: Obviously!
• Computer with SD Card Reader: To flash the operating system onto your MicroSD card.

Step 1: Preparing Your Raspberry Pi – OS Installation

The first step is to get an operating system onto your Raspberry Pi. For Pi-hole, a lightweight, headless (no graphical interface) version of Raspberry Pi OS (formerly Raspbian Lite) is ideal. This minimizes resource usage, leaving more power for Pi-hole itself.

1. Download Raspberry Pi Imager: Head over to the official Raspberry Pi website and download the Raspberry Pi Imager for your computer’s operating system.
2. Flash the OS:
   • Insert your MicroSD card into your computer’s card reader.
   • Open Raspberry Pi Imager.
   • Click “CHOOSE OS” and select “Raspberry Pi OS (other)” -> “Raspberry Pi OS Lite (64-bit)” or “(32-bit)” depending on your Pi model (64-bit is generally preferred for Pi 4).
   • Click “CHOOSE STORAGE” and select your MicroSD card. Double-check this step carefully to avoid wiping the wrong drive!
   • Click the gear icon (settings) before writing. Here, you can pre-configure SSH (essential for headless setup), set a hostname, and set a username/password. This saves a lot of hassle later.
   • Click “WRITE” and confirm. The process will take a few minutes.
3. Eject and Insert: Once the flashing is complete, safely eject the MicroSD card from your computer and insert it into your Raspberry Pi.

Step 2: Connecting and Accessing Your Raspberry Pi

Now, connect your Raspberry Pi:

1. Plug in the Ethernet cable from your Pi to your router.
2. Connect the power supply. Your Pi will boot up.
3. Find Your Pi’s IP Address: You’ll need to know your Pi’s IP address on your network to connect via SSH. You can usually find this in your router’s administration interface (look for “connected devices” or “DHCP clients”). Alternatively, if you have a tool like Advanced IP Scanner (for Windows) or nmap (for Linux/macOS), you can scan your network.
4. SSH into Your Pi: Open a terminal (macOS/Linux) or use an SSH client like PuTTY (Windows). Type the following command, replacing your_username with the username you set in the imager (default is pi if you didn’t set one) and your_pi_ip with your Pi’s IP address:

   ssh your_username@your_pi_ip

   Enter your password when prompted. If this is your first time connecting, you’ll be asked to confirm the authenticity of the host; type ‘yes’.

5. Update Your Pi: It’s always a good practice to update your system after a fresh OS install.

   sudo apt update && sudo apt upgrade -y

Step 3: Installing Pi-hole

With your Pi updated and accessible, installing Pi-hole is surprisingly simple thanks to its official installer script.

1. Run the Installer: In your SSH terminal, execute the following command:

   curl -sSL https://install.pi-hole.net | bash

   This command downloads and runs the official Pi-hole installation script.

2. Follow the On-Screen Prompts: The installer is user-friendly and will guide you through several configuration steps:
   • Static IP Address: The installer will recommend setting a static IP address for your Pi-hole. This is crucial as your network devices will rely on Pi-hole’s IP for DNS. Confirm this choice.
   • Upstream DNS Provider: Choose your preferred upstream DNS server. Options include Google, Cloudflare, OpenDNS, and more. Cloudflare (1.1.1.1) is a popular, privacy-focused choice.
   • Block Lists: The installer will offer to install default block lists. Leave these selected.
   • Web Admin Interface: Confirm you want to install the web admin interface (highly recommended for easy management).
   • Web Server (Lighttpd): Confirm you want to install the web server (Lighttpd) and PHP modules.
   • Logging: Decide if you want to log queries. This is useful for troubleshooting but can be disabled for maximum privacy.
3. Note Your Admin Password: At the end of the installation, you’ll be presented with a summary, including the IP address of your Pi-hole’s web interface and a randomly generated password for the admin portal. WRITE THIS DOWN! You’ll need it to log in.

Step 4: Configuring Your Network to Use Pi-hole

This is the final, crucial step. For Pi-hole to block ads, your network devices need to be configured to use it as their DNS server. You have two primary methods:

Method A: Router-Level Configuration (Recommended)

This is the most effective method as it forces all devices connected to your router to use Pi-hole for DNS, including new devices joining your network. The exact steps vary by router manufacturer, but the general process is:

1. Access Your Router’s Admin Panel: Open a web browser and navigate to your router’s IP address (e.g., 192.168.1.1 or 192.168.0.1). Log in with your router’s credentials.
2. Locate DNS Settings: Look for sections like “WAN,” “Internet,” “DHCP,” “LAN Settings,” or “DNS Server.”
3. Change Primary DNS: Change the primary DNS server to your Pi-hole’s static IP address.
4. Secondary DNS (Optional but Recommended): For redundancy, you can set a secondary DNS server. Some routers allow you to enter a second DNS server. You could use your Pi-hole’s IP again or a public

   Written by: Alex Torres, Editor at OpenClaw Resource

   Last Updated: May 2026

   Our Editorial Standards | How We Review Skills | Affiliate Disclosure

   Building a homelab? See our roundup of the best mini PCs for homelab use →

Best Routers for a Home Lab Network: Building Your OpenClaw Foundation

Welcome, fellow self-hosters and homelab enthusiasts, to OpenClaw Resource! If you’re diving into the exciting world of creating your own server infrastructure, virtual machines, or experimenting with network configurations, you know that a robust and reliable network is paramount. And at the heart of any solid network lies a capable router. But not just any router will do for a home lab. You need something that offers more than basic internet sharing – something that provides granular control, powerful features, and the stability to handle demanding workloads.

Choosing the best router for your home lab network can feel overwhelming with the myriad of options available. This comprehensive guide will cut through the noise, highlighting key features to look for and recommending specific products that will serve as an excellent foundation for your OpenClaw-powered projects and beyond.

Why a Dedicated Router for Your Home Lab?

You might be thinking, “Can’t I just use the router provided by my Internet Service Provider (ISP)?” While your ISP router gets you online, it’s typically designed for basic consumer use. For a home lab, you’ll quickly hit its limitations. Here’s why a dedicated, more advanced router is a wise investment:

• Enhanced Control: ISP routers often lock down advanced settings. A dedicated router gives you full access to features like static routing, VLANs, firewall rules, and advanced QoS.
• Increased Performance: Better processors, more RAM, and often dedicated hardware for routing tasks mean your lab traffic won’t bottleneck your main internet connection.
• Security: Granular firewall control and the ability to isolate your lab network from your main home network are crucial for security.
• Flexibility & Scalability: As your lab grows, you’ll appreciate a router that can handle more devices, more complex network configurations, and potentially faster internet speeds.
• Learning Opportunity: Configuring an advanced router is a fantastic way to deepen your networking knowledge.

Key Features to Look for in a Home Lab Router

When evaluating routers for your homelab, keep these essential features in mind:

1. Processor & RAM

Just like a server, a router’s CPU and RAM dictate its performance. For a home lab, you’ll want something with a decent multi-core processor and at least 512MB to 1GB of RAM. This ensures smooth operation when running multiple services, complex firewall rules, or VPN tunnels.

2. Port Configuration & Speed

• Gigabit Ethernet: This is a non-negotiable for any modern home lab. Ensure all WAN and LAN ports are Gigabit (10/100/1000 Mbps).
• Multi-Gigabit (2.5GbE, 5GbE, 10GbE): If you’re dealing with high-speed storage (like a ZFS server) or planning to run extremely demanding applications, consider routers with at least one 2.5GbE or even 10GbE port. This future-proofs your network.
• Number of LAN Ports: While you can always add a switch, having 4-8 LAN ports directly on the router is convenient for connecting core lab devices.

3. Advanced Networking Features

• VLAN Support: Absolutely critical for network segmentation. VLANs allow you to logically separate your lab’s management network, virtual machine networks, storage network, and more, even if they share the same physical cables. This enhances security and organization.
• Static Routing: Essential for directing traffic between different subnets within your lab.
• Firewall & NAT Rules: Robust firewall capabilities are a must for security, allowing you to control ingress and egress traffic with precision.
• VPN Server/Client: For securely accessing your lab from outside your home network or encrypting traffic.
• Quality of Service (QoS): Prioritize traffic for critical lab services over less important traffic.

4. Management Interface & Custom Firmware Potential

A user-friendly yet powerful web interface is important. Even better is a router that supports custom firmware like DD-WRT, OpenWrt, or pfSense/OPNsense. These open-source firmwares unlock a vast array of advanced features, offer greater customization, and often provide better performance and security updates than stock firmware.

5. Wireless Capabilities (Optional but useful)

While many homelabs focus on wired connections for stability and speed, a powerful Wi-Fi 6 (802.11ax) or even Wi-Fi 6E (802.11ax on 6GHz) router can be beneficial for connecting laptops, mobile devices, or IoT lab components.

Top Router Recommendations for Your Home Lab

Based on the features above, here are some excellent router options that cater to different budgets and technical requirements, perfect for building out your OpenClaw environment:

1. Ubiquiti EdgeRouter X (ER-X)

Why it’s great: The EdgeRouter X is a fantastic entry-level, yet powerful, wired router for homelabs. It’s incredibly affordable and offers an impressive feature set for its price point. Running EdgeOS (a customized Vyatta fork), it provides full CLI access for advanced configurations, alongside a capable web GUI. It supports VLANs, static routing, firewall rules, and even basic VPNs. Its five Gigabit Ethernet ports can be configured as a switch, or individual routed ports.

Considerations: It’s a wired-only router, so you’ll need a separate Access Point for Wi-Fi. The learning curve for EdgeOS can be a bit steeper than consumer routers, but it’s an excellent learning tool.

2. MikroTik hEX S (RB760iGS)

Why it’s great: MikroTik routers are renowned in the networking community for their incredible power, flexibility, and value. The hEX S is a compact Gigabit Ethernet router running RouterOS, one of the most feature-rich router operating systems available. It boasts 5x Gigabit ports (one with SFP for fiber), powerful QoS, advanced firewall, extensive VPN options, and comprehensive VLAN support. RouterOS offers unparalleled control and is a fantastic platform for network engineers to learn and experiment.

Considerations: RouterOS has a significant learning curve, often requiring a deep dive into its documentation. Like the EdgeRouter X, it’s wired-only.

3. Protectli Vault Mini PCs (or similar mini-PCs) with pfSense/OPNsense

Why it’s great: This is where true power and flexibility come into play. Instead of a dedicated router appliance, you can use a small form-factor PC (like a Protectli Vault, Qotom, or Topton mini-PC) with multiple Gigabit or 2.5GbE LAN ports and install open-source firewall/router software like pfSense or OPNsense. These distributions turn a standard PC into an incredibly powerful and feature-rich router, offering enterprise-grade features such as multi-WAN, advanced routing protocols, intrusion detection/prevention, proxy servers, and much more. This setup is highly scalable and perfect for a growing lab.

Considerations: Requires a bit more initial setup and understanding of PC hardware. You’re effectively building your own router. It’s also a wired-only solution, needing a separate AP for Wi-Fi.

4. ASUS RT-AX86U (or similar high-end consumer routers)

Why it’s great: If you prefer an all-in-one solution with excellent Wi-Fi capabilities, a high-end consumer router like the ASUS RT-AX86U can be surprisingly capable for a home lab. It offers a powerful processor, usually 2.5GbE WAN/LAN ports, good Gigabit LAN port count, and robust Wi-Fi 6. Many of these routers also support custom firmware like Merlin (for ASUS) or OpenWrt, greatly expanding their capabilities for VLANs, VPNs, and advanced routing, while still maintaining an easy-to-use interface for basic tasks.

Considerations: While powerful, they may not offer the same depth of control as dedicated firewall appliances or CLI-focused routers without custom firmware. They also tend to be more expensive.

Practical Tips for Setting Up Your Home Lab Network

1. Plan Your IP Scheme: Before you plug anything in, decide on your internal IP addressing. Use separate subnets for different VLANs (e.g., 192.168.10.0/24 for management, 192.168.20.0/24 for VMs, etc.).
2. Implement VLANs Early: Start with VLANs from day one. It’s much easier to set them up initially than to retrofit them later as your lab grows.
3. Document Everything: Keep a record of your IP addresses, VLAN
   

   Frequently Asked Questions

   Why can’t I just use my standard consumer router for a home lab?

   Consumer routers often lack advanced features like robust VLAN support, multiple WAN options, or high-performance VPN capabilities crucial for isolating lab environments and managing complex network traffic efficiently.

   What are the most important features to consider for a home lab router?

   Look for strong VLAN support, multiple Gigabit Ethernet ports, VPN server/client capabilities, robust firewall rules, and potential for open-source firmware like pfSense or OpenWRT for advanced customization and control.

   Do I need to spend a lot to get a good router for a home lab?

   Not necessarily. Many excellent routers, including refurbished enterprise gear or dedicated mini-PCs running open-source firewalls, offer powerful features and performance for a modest budget, balancing cost and capability effectively.

   Written by: Alex Torres, Editor at OpenClaw Resource

   Last Updated: May 2026

   Our Editorial Standards | How We Review Skills | Affiliate Disclosure

   Building a homelab? See our roundup of the best mini PCs for homelab use →

Unlock AI Power: How to Run Your Own AI Locally with Ollama

The world of artificial intelligence is exploding, and while cloud-based AI services offer incredible power, there’s a growing desire among tech enthusiasts, developers, and homelabbers to bring that power closer to home. Enter local AI – a game-changer for privacy, cost-efficiency, and ultimate control. At OpenClaw, we’re all about empowering you to self-host and maximize your homelab, and running AI locally with Ollama is a perfect fit for that mission.

Imagine having a powerful AI chatbot, a code generator, or a creative writing assistant running directly on your own hardware, without sending your data to external servers or incurring monthly subscription fees. This isn’t just a pipe dream; it’s a readily achievable reality thanks to tools like Ollama. In this comprehensive guide, we’ll walk you through everything you need to know to set up your own local AI environment using Ollama.

Why Run AI Locally? The OpenClaw Perspective

Before we dive into the “how,” let’s briefly touch on the “why.” For the OpenClaw community, the benefits of local AI align perfectly with our core values:

• Privacy & Data Security: Your data stays on your machines. No third-party servers, no unknown data retention policies. This is paramount for sensitive projects or personal use.
• Cost-Effectiveness: Avoid recurring cloud API costs. Once your hardware is in place, the only ongoing cost is electricity. For frequent users, this adds up to significant savings.
• Offline Capability: No internet? No problem! Your local AI continues to function flawlessly, perfect for remote setups or internet outages.
• Customization & Control: Experiment with different models, fine-tune them, and integrate them deeply with your existing local applications and workflows. You’re in the driver’s seat.
• Learning & Experimentation: It’s an excellent way to understand how large language models (LLMs) work firsthand, without the abstraction layers of cloud services.

Introducing Ollama: Your Gateway to Local LLMs

Ollama is a fantastic, user-friendly tool that simplifies the process of running large language models (LLMs) on your local machine. It provides a straightforward way to download, run, and manage various open-source models. Think of it as a Docker for LLMs – it handles the dependencies, model weights, and execution environment, making it incredibly easy to get started.

What You’ll Need: Hardware & Software Prerequisites

Running LLMs locally requires a bit of horsepower, especially for larger models. Here’s what you should consider:

Hardware Recommendations:

• CPU: A modern multi-core CPU is essential. While many models can run on CPU alone, performance will be limited.
• RAM: This is crucial. More RAM allows you to load larger models. Aim for at least 16GB, but 32GB or even 64GB is highly recommended for a smoother experience with bigger models like Llama 3 8B.
• GPU (Highly Recommended): This is where the magic happens for speed. An NVIDIA GPU with CUDA support is ideal, especially one with a good amount of VRAM (Video RAM). For example, an NVIDIA GeForce RTX 3060 with 12GB VRAM or an RTX 4070 with 12GB+ will provide a significantly better experience. AMD GPUs are also gaining better support, but NVIDIA currently offers the broadest compatibility and best performance for local LLMs.
• Storage: SSD is a must. LLM files can be large (several gigabytes each), and fast storage ensures quick loading times.

Software Prerequisites:

• Operating System: Ollama supports macOS, Linux (various distributions like Ubuntu, Fedora, Arch), and Windows.
• Internet Connection: Required for initial download of Ollama and the LLM models.

Step-by-Step Guide: Setting Up Ollama and Running Your First AI

Step 1: Install Ollama

This is the easiest part. Visit the official Ollama website (ollama.com) and download the installer for your operating system. The installation process is typically straightforward – just follow the on-screen prompts.

• macOS: Download the .dmg file, drag Ollama to your Applications folder.
• Linux: Use the one-line install script provided on their site: curl -fsSL https://ollama.com/install.sh | sh
• Windows: Download the .exe installer and run it.

Once installed, Ollama will usually start automatically in the background, listening for requests.

Step 2: Download Your First LLM Model

Ollama makes downloading models incredibly simple. Open your terminal (or PowerShell on Windows) and use the ollama run command. Let’s start with a popular and relatively lightweight model, Llama 2:

ollama run llama2

The first time you run this command, Ollama will automatically download the llama2 model. This might take a few minutes depending on your internet speed and the model size. You’ll see a progress indicator in your terminal.

Once downloaded, the model will load, and you’ll be dropped into an interactive chat session with Llama 2! Try asking it a question:

>>> Hi there! What can you do?

To exit the chat session, type /bye.

Step 3: Explore More Models

Ollama supports a wide range of models. You can find a list of available models and their descriptions on the Ollama website or by running:

ollama list

Some popular models you might want to try include:

• Llama 3: Meta’s latest powerful open-source model. Try ollama run llama3.
• Mistral: Known for its efficiency and strong performance: ollama run mistral.
• Code Llama: Specifically trained for coding tasks: ollama run codellama.
• Phi-3: Microsoft’s small, yet capable model, great for lower-spec hardware: ollama run phi3.

Simply replace llama2 with the model name you want to download and run.

Step 4: Interact with Models via API

While the interactive terminal is great for quick tests, the real power of Ollama for homelabbers comes from its API. Ollama runs a local server (by default on http://localhost:11434) that exposes a REST API. This allows you to integrate your local LLMs with other applications, scripts, or even custom web UIs.

Here’s a simple example using curl to interact with a running model:

curl http://localhost:11434/api/generate -d '{
  "model": "llama2",
  "prompt": "Why is self-hosting important for privacy?",
  "stream": false
}'

You’ll get a JSON response containing the model’s generated text. This API is your key to building custom applications that leverage your local AI.

Practical Tips for OpenClaw Enthusiasts

• Monitor Resource Usage: Use tools like htop (Linux), Task Manager (Windows), or Activity Monitor (macOS) to keep an eye on your CPU, RAM, and GPU utilization when an LLM is running. This helps you understand your hardware’s limits.
• Consider Quantization: Many models come in different “quantizations” (e.g., 7B, 7B-Q4_K_M). Lower quantization means less precision but smaller file size and lower RAM/VRAM requirements, making them more suitable for less powerful hardware. You can specify these when downloading, e.g., ollama run llama2:7b-chat-q4_K_M.
• Build a Front-End: For a more user-friendly experience, consider building a simple web interface using Python frameworks like Flask or Streamlit, or even a simple HTML/JavaScript page, to interact with Ollama’s API. This turns your terminal-based AI into a proper local application.
• Integrate with Your Homelab: Think about how local AI can enhance your existing homelab setup. Could it summarize logs from your NAS? Generate configuration snippets for your network devices? The possibilities are endless!
• Stay Updated: The local AI landscape is evolving rapidly. Regularly check the Ollama website and
  

  Frequently Asked Questions

  What is Ollama and how does it help run AI locally?

  Ollama is a platform designed to simplify running large language models (LLMs) on your own computer. It streamlines downloading, setting up, and managing various open-source AI models, making local AI accessible for everyone.

  Why would I want to run AI models on my local machine instead of cloud services?

  Local AI offers enhanced privacy and data security since your information stays on your device. It also provides greater control, reduces potential API costs, and allows you to experiment with AI even without an internet connection.

  What hardware specifications are important for running AI models with Ollama effectively?

  While some models can use a CPU, a dedicated GPU with sufficient VRAM is crucial for good performance, especially with larger models. 8GB of VRAM or more is generally recommended for a smoother experience.

  Written by: Alex Torres, Editor at OpenClaw Resource

  Last Updated: May 2026

  Our Editorial Standards | How We Review Skills | Affiliate Disclosure

  Building a homelab? See our roundup of the best mini PCs for homelab use →

Portainer vs. Dockge: The Ultimate Docker Management UI Showdown for Your Homelab

Welcome back to OpenClaw Resource, your go-to hub for all things self-hosting and homelab! Today, we’re diving deep into a topic that often sparks lively debate in our community: choosing the best Docker management UI. If you’re running a homelab, whether it’s on a Raspberry Pi, an old PC, or a dedicated server, you know the power of Docker. But managing those containers, volumes, and networks can quickly become a command-line jungle. That’s where a good graphical user interface (GUI) comes in.

For years, Portainer has been the undisputed king of Docker UIs. It’s robust, feature-rich, and widely adopted. But recently, a new challenger has emerged, gaining significant traction: Dockge. Developed by the creator of Uptime Kuma (another homelab favorite!), Dockge promises a fresh, modern approach. So, which one is right for your OpenClaw-powered homelab? Let’s break it down.

Understanding Your Needs: Why a Docker UI?

Before we pit these two titans against each other, let’s briefly recap why a Docker UI is such a game-changer for self-hosting enthusiasts:

• Simplified Management: No more memorizing complex Docker CLI commands. Start, stop, restart, and delete containers with a click.
• Visual Overview: Get a bird’s-eye view of all your running containers, their status, resource usage, and network configurations.
• Easier Troubleshooting: Quickly access container logs, inspect details, and diagnose issues without SSHing into your server.
• Volume and Network Management: Create and manage Docker volumes and networks effortlessly.
• Stack/Compose Management: Deploy and manage multi-container applications defined in docker-compose.yml files.
• User Management (for teams): Some UIs offer user roles and permissions, useful if multiple people access your homelab.

Portainer: The Established Powerhouse

Portainer has been the go-to Docker management solution for years, and for good reason. It’s incredibly comprehensive, offering a vast array of features that cater to both beginners and advanced users.

Portainer’s Strengths:

• Feature-Rich: Portainer offers an extensive feature set. You can manage almost every aspect of Docker: containers, images, volumes, networks, registries, secrets, configs, and even Docker Swarm clusters.
• Robust User Management: If you have multiple users accessing your homelab (e.g., family members or a small team), Portainer’s robust user and team management with role-based access control (RBAC) is invaluable.
• Application Templates: The “App Templates” feature allows for quick deployment of popular applications, simplifying the setup process for common homelab services like Jellyfin or Nextcloud.
• Edge Agent: For distributed environments or managing Docker on remote devices, Portainer’s Edge Agent is a powerful tool.
• Extensive Documentation & Community: Being around for a long time means Portainer has excellent documentation and a massive, active community ready to help.
• Business Edition: While the Community Edition (CE) is free and powerful, Portainer also offers a Business Edition with even more advanced features for larger deployments.

Portainer’s Considerations:

• Interface Can Feel Busy: For new users, the sheer number of options and menus can sometimes feel overwhelming.
• Resource Usage: While generally lightweight, Portainer can sometimes use slightly more resources than simpler alternatives, especially on very constrained hardware.
• Learning Curve: While powerful, there’s a slight learning curve to fully master all its capabilities.

Dockge: The Modern Challenger

Dockge is the new kid on the block, but it’s quickly making waves. Developed by Louis Lam, the creator of the immensely popular Uptime Kuma, Dockge brings a fresh perspective to Docker Compose management.

Dockge’s Strengths:

• Focus on Docker Compose: Dockge’s primary strength is its elegant and intuitive handling of docker-compose.yml files. It makes editing, deploying, and managing compose stacks incredibly simple.
• Live Log Viewer: A standout feature is its real-time, integrated log viewer directly within the compose file editor. This significantly speeds up debugging and iteration.
• Modern UI/UX: The interface is clean, modern, and highly responsive. It feels very much like a web-based IDE for your Docker Compose files.
• Fast and Lightweight: Dockge is designed to be extremely lightweight and fast, making it ideal for resource-constrained homelabs or single-board computers.
• Easy Setup: Getting Dockge up and running is typically a breeze, often just a single Docker command.
• Automated Updates: Dockge can automatically check for updates to your compose stacks, making maintenance simpler.

Dockge’s Considerations:

• Less Comprehensive: Dockge is primarily focused on Docker Compose. While you can still manage individual containers, images, and networks, it’s not as feature-rich or granular as Portainer for these specific tasks.
• Newer Project: Being a newer project, the community and documentation are still growing, though the developer is very active.
• No User Management (Yet): As of writing, Dockge lacks built-in user management with RBAC, which might be a dealbreaker for multi-user environments. It’s generally expected that only the homelab owner would access it.
• No Swarm Support: If you’re running a Docker Swarm cluster, Dockge won’t be able to manage it.

Portainer vs. Dockge: The Head-to-Head Comparison

Let’s put them side-by-side for key homelab use cases:

Ease of Use for Beginners:

• Portainer: Good, but can be intimidating due to the sheer number of options. App templates help a lot.
• Dockge: Excellent, especially for those who primarily work with Docker Compose. The clean interface is very inviting.

Managing Docker Compose Stacks:

• Portainer: Capable, but the editor is more basic. Logs are separate.
• Dockge: Superior. Its integrated editor with live logs and version control is a dream for compose-heavy users.

Granular Docker Resource Management (Images, Volumes, Networks):

• Portainer: Comprehensive and robust. You have full control over every Docker entity.
• Dockge: Adequate, but not its primary focus. You can manage them, but it’s less feature-rich than Portainer.

Performance and Resource Footprint:

• Portainer: Good, but can be slightly heavier.
• Dockge: Excellent, very lightweight and fast, ideal for low-power devices like a Orange Pi or an old NUC.

Security and User Management:

• Portainer: Industry-leading, with robust RBAC and authentication options.
• Dockge: Currently lacks built-in user management, relying on system-level security or reverse proxy authentication.

Advanced Features (Swarm, Edge Agents, Registries):

• Portainer: Dominates in this area. Essential for larger or more complex setups.
• Dockge: Does not offer these features.

Practical Tips for Your OpenClaw Homelab

1. Consider Your Primary Workflow: If you live and breathe docker-compose.yml files, Dockge will feel like home. If you prefer clicking around and having a comprehensive overview of all Docker aspects, Portainer is better.
2. Resource Constraints: For very low-power devices, Dockge’s lightweight nature might give it an edge.
3. Multi-User Environment: If multiple people need access to manage containers with different permissions, Portainer is the clear winner. For single-user homelabs, this isn’t a concern.
4. Start Simple: If you’re new to Docker UIs, you might even consider starting with Dockge for its simplicity in managing compose files. You can always add Portainer later if you need its advanced features.
5. Reverse Proxy for Security: Regardless of which UI you choose, always

   Written by: Alex Torres, Editor at OpenClaw Resource

   Last Updated: May 2026

   Our Editorial Standards | How We Review Skills | Affiliate Disclosure

   Building a homelab? See our roundup of the best mini PCs for homelab use →

The Best SSDs for Your Home NAS: Supercharge Your Self-Hosting Setup

Welcome back, OpenClaw enthusiasts! If you’re diving deeper into the world of self-hosting, homelabs, and network-attached storage (NAS), you’re likely already familiar with the incredible benefits a well-configured NAS brings. From centralized data backup and media streaming to hosting your own applications, a NAS is the heart of many home server setups. But to truly unlock its potential, especially for demanding tasks, the right storage drives are paramount. While traditional HDDs offer vast capacity, Solid State Drives (SSDs) are increasingly becoming the go-to choice for those seeking speed, responsiveness, and efficiency. But which SSDs are best for a home NAS?

This comprehensive guide will help you navigate the world of SSDs for your home NAS, ensuring you make an informed decision that perfectly balances performance, longevity, and budget. Let’s get started!

Why Choose SSDs for Your Home NAS?

Before we dive into specific recommendations, let’s quickly recap why SSDs are such a compelling choice for a home NAS, especially for users on the OpenClaw platform:

• Blazing Fast Performance: This is the most obvious benefit. SSDs offer significantly higher read and write speeds compared to HDDs, leading to quicker file transfers, faster application loading, and a snappier overall NAS experience.
• Improved Responsiveness: For tasks like virtual machines, database operations, or serving multiple users simultaneously, the lower latency of SSDs is a game-changer.
• Silent Operation: Unlike HDDs with their spinning platters, SSDs are completely silent, making them ideal for a NAS located in a living space or office.
• Lower Power Consumption: SSDs generally consume less power than HDDs, which can contribute to a lower electricity bill over time, especially for always-on devices like a NAS.
• Enhanced Durability: Without moving parts, SSDs are more resistant to shocks and vibrations, making them potentially more reliable in certain environments.

While SSDs come with a higher cost per gigabyte, their benefits often outweigh this for performance-critical NAS roles.

Understanding SSD Types for NAS

When selecting an SSD, you’ll encounter a few key types and form factors. Knowing the differences will help you choose wisely:

• SATA SSDs: These are the most common and often most affordable SSDs. They connect via a standard SATA 3.0 port and offer speeds up to around 550 MB/s. They come in a 2.5-inch form factor, making them direct replacements for laptop HDDs and compatible with most NAS enclosures.
• NVMe (M.2) SSDs: These are significantly faster, utilizing the PCIe bus. They offer speeds several times that of SATA SSDs (e.g., 3,500 MB/s for PCIe Gen3, 7,000+ MB/s for PCIe Gen4). NVMe drives come in a compact M.2 form factor. While not all home NAS devices support NVMe directly for primary storage, many higher-end models or DIY OpenClaw builds will have M.2 slots for caching or dedicated storage pools.
• QVO vs. EVO vs. PRO (Samsung Example): Many manufacturers, like Samsung, categorize their SSDs by endurance and performance. QVO drives typically use QLC (Quad-Level Cell) NAND, offering high capacity at a lower price but with lower endurance. EVO drives (TLC – Triple-Level Cell) strike a good balance of performance and endurance, making them popular for consumers. PRO drives (often MLC – Multi-Level Cell) offer the highest endurance and performance, ideal for heavy-duty workloads, but at a premium. For a home NAS, EVO-level drives are usually sufficient, with PRO drives being overkill unless you have specific, extremely demanding use cases.

Key Considerations When Choosing SSDs for Your Home NAS

Beyond raw speed, several factors are crucial for NAS longevity and performance:

1. Endurance (TBW – Terabytes Written)

Endurance measures how much data can be written to an SSD before it potentially fails. It’s expressed in Terabytes Written (TBW). NAS devices, especially those running services, logging, or frequent backups, can generate a lot of writes. Look for SSDs with a higher TBW rating. While consumer SSDs are often sufficient, enterprise-grade or NAS-specific SSDs offer significantly higher endurance, which can be beneficial for 24/7 operation.

2. DRAM Cache

A DRAM cache acts as a buffer for writes, improving sustained performance and extending the lifespan of the NAND flash. Drives without a DRAM cache (DRAM-less SSDs) are cheaper but can experience performance degradation under heavy, sustained loads, which is common in a NAS environment. For critical NAS roles, always opt for SSDs with a DRAM cache.

3. Power Loss Protection (PLP)

While more common in enterprise SSDs, some higher-end consumer or NAS-specific SSDs include hardware-based power loss protection. This feature uses capacitors to provide enough power for the SSD to complete any data in its volatile cache and write it to NAND in the event of a sudden power outage, preventing data corruption.

4. NAS Compatibility and Firmware

Some SSD manufacturers, like Western Digital and Seagate, now offer SSDs specifically optimized for NAS environments. These drives often feature firmware tweaks for better compatibility with RAID controllers, enhanced endurance, and features like vibration resistance (though less critical for SSDs). While not strictly necessary, they can offer peace of mind.

5. Capacity and Over-provisioning

Don’t just fill your SSDs to the brim. Over-provisioning (leaving some space unallocated) can improve performance and endurance. Many SSDs already have factory over-provisioning, but leaving 10-15% of the drive empty can further help, especially for consumer drives. For a home NAS, consider your current and future storage needs. It’s often better to buy slightly larger drives than you think you need.

Top SSD Recommendations for Your Home NAS

Based on the above considerations, here are some excellent SSD choices for your OpenClaw-powered home NAS:

1. Samsung 870 EVO (SATA)

The Samsung 870 EVO series is a perennial favorite for good reason. It offers an excellent balance of performance, reliability, and endurance at a competitive price point. With a robust DRAM cache and Samsung’s proven V-NAND technology, these TLC drives are perfect for primary storage pools in most home NAS setups, offering solid sustained performance for media streaming, file serving, and even light VM usage. They come in capacities up to 4TB, making them versatile for various needs.

2. Crucial MX500 (SATA)

Another strong contender in the SATA SSD space is the Crucial MX500. It’s often slightly more affordable than the Samsung 870 EVO while still delivering impressive performance and reliability with a DRAM cache. Its endurance ratings are competitive, making it a fantastic value proposition for those looking to outfit their NAS with reliable, fast storage without breaking the bank. Great for RAID configurations.

3. Western Digital Red SA500 NAS SSD (SATA)

Specifically designed for NAS environments, the Western Digital Red SA500 NAS SSD is an excellent choice if you want drives optimized for 24/7 operation and RAID arrays. These drives feature firmware tailored for NAS workloads, higher endurance ratings than typical consumer drives, and are built to handle sustained transfers. While they might carry a slight premium, the peace of mind and optimized performance for NAS use cases are often worth it, especially for more critical data.

4. Samsung 970 EVO Plus (NVMe – for Caching/Tiering)

If your NAS supports NVMe M.2 slots (either for caching or a dedicated high-performance pool), the Samsung 970 EVO Plus is an outstanding option. While not ideal for every drive bay in a typical NAS due to their form factor and heat considerations in some enclosures, they are perfect for accelerating your NAS. Use

Frequently Asked Questions

Building a homelab? See our roundup of the best mini PCs for homelab use →

How to Set Up Nginx Proxy Manager at Home: Your Ultimate Guide to Self-Hosting Success

Welcome, fellow homelab enthusiasts and self-hosting adventurers! If you’re anything like us at OpenClaw, you love the freedom and control that comes with running your own services. But let’s be honest, managing multiple services on different ports, dealing with SSL certificates, and exposing them securely to the internet can quickly become a tangled mess. That’s where Nginx Proxy Manager (NPM) swoops in like a superhero, simplifying your entire setup.

In this comprehensive guide, we’ll walk you through exactly how to set up Nginx Proxy Manager at home, transforming your homelab into a streamlined, secure, and easily accessible powerhouse. Get ready to ditch those complex Nginx config files and embrace a user-friendly web interface!

What is Nginx Proxy Manager and Why Do You Need It?

At its core, Nginx Proxy Manager is a reverse proxy management system built on Nginx, featuring a beautiful and intuitive web interface. Think of it as the traffic cop for your homelab. Instead of directly exposing your services (like a Plex server, Nextcloud instance, or Home Assistant dashboard) to the internet, you expose NPM. NPM then intelligently forwards requests to the correct internal service based on the domain name.

Here’s why NPM is an absolute game-changer for your self-hosting journey:

• Simplified SSL/TLS: Automatically obtain and renew free SSL certificates from Let’s Encrypt for all your services. No more manual certbot commands!
• Centralized Management: Manage all your proxy hosts, redirections, and streams from a single, easy-to-use web interface.
• Security: By acting as a reverse proxy, NPM hides your internal network structure and can add an extra layer of security.
• Custom Domains: Easily use custom domain names for your internal services, making them much more memorable and professional.
• Access Control: Implement basic authentication for services if needed.
• WebSockets Support: Essential for many modern web applications like Home Assistant.

Prerequisites for Your Nginx Proxy Manager Setup

Before we dive into the installation, let’s ensure you have a few things in place:

• A Server/Device: This could be a dedicated Raspberry Pi, an old PC running Ubuntu Server, a Proxmox LXC container, or a Docker-enabled NAS like a Synology DiskStation. We highly recommend using Docker for NPM as it simplifies deployment and updates.
• Docker and Docker Compose: If you’re going the Docker route (which we strongly advise), ensure Docker and Docker Compose are installed on your server.
• Domain Name: A custom domain name (e.g., yourdomain.com) is crucial for leveraging NPM’s SSL capabilities. You can get one from registrars like Namecheap or Google Domains.
• Port Forwarding: You’ll need to forward ports 80 (HTTP) and 443 (HTTPS) from your router to the internal IP address of the server running NPM. This allows external traffic to reach NPM.
• DNS Management: You’ll need access to your domain’s DNS settings to create A records or CNAME records pointing to your home’s public IP address. Dynamic DNS (DDNS) is essential if your home IP changes frequently. Services like DuckDNS or No-IP are great for this.

Step-by-Step: Installing Nginx Proxy Manager with Docker Compose

This is the recommended and most straightforward method for installing NPM.

1. Prepare Your Server and Docker Environment

Ensure Docker and Docker Compose are installed. If not, refer to Docker’s official documentation for your specific OS. Create a dedicated directory for NPM:

mkdir nginx-proxy-manager
cd nginx-proxy-manager

2. Create Your docker-compose.yml File

Inside the `nginx-proxy-manager` directory, create a file named `docker-compose.yml` (or `docker-compose.yaml`) and paste the following content. This configuration sets up NPM and a PostgreSQL database for its data.

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: always
    ports:
      - '80:80'
      - '443:443'
      - '81:81'
    environment:
      DB_MYSQL_HOST: db
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: npm
      DB_MYSQL_PASSWORD: npm_password_secure # CHANGE THIS!
      DB_MYSQL_NAME: npm
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    depends_on:
      - db

  db:
    image: 'mariadb:latest'
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: npm_db_root_password_secure # CHANGE THIS!
      MYSQL_DATABASE: npm
      MYSQL_USER: npm
      MYSQL_PASSWORD: npm_password_secure # CHANGE THIS!
    volumes:
      - ./data/mysql:/var/lib/mysql

Important: Change the `npm_password_secure` and `npm_db_root_password_secure` values to strong, unique passwords!

Note: While the environment variables mention `DB_MYSQL_HOST`, NPM actually supports both MySQL and MariaDB. The `mariadb:latest` image works perfectly here.

3. Start Nginx Proxy Manager

From within the `nginx-proxy-manager` directory, run the following command:

docker compose up -d

This command will download the necessary Docker images and start your NPM and database containers in the background.

4. Access the Nginx Proxy Manager Web Interface

Open your web browser and navigate to `http://YOUR_SERVER_IP:81`. Replace `YOUR_SERVER_IP` with the actual IP address of the server running NPM.

You should be greeted by the Nginx Proxy Manager login screen.

Default Credentials:

• Email: `admin@example.com`
• Password: `changeme`

Immediately log in and change these default credentials! You’ll be prompted to do so on your first login.

Configuring Your First Proxy Host

Now that NPM is up and running, let’s configure your first service.

1. Update DNS Records

Go to your domain registrar’s DNS management page. Create an A record (or CNAME if using DDNS) for the subdomain you want to use. For example, if your domain is `yourdomain.com` and you want to expose your Home Assistant instance, create an A record for `homeassistant.yourdomain.com` pointing to your home’s public IP address.

If you’re using a DDNS service like DuckDNS, configure your router or a script on your server to keep your public IP updated with the DDNS provider.

2. Create a New Proxy Host in NPM

In the NPM web interface, navigate to “Hosts” > “Proxy Hosts” and click “Add Proxy Host”.

• Domain Names: Enter the subdomain you just configured (e.g., `homeassistant.yourdomain.com`).
• Scheme: Usually `http` for internal services.
• Forward Hostname / IP: The internal IP address of your service (e.g., `192.168.1.100`).
• Forward Port: The internal port your service is listening on (e.g., `8123` for Home Assistant).
• Block Common Exploits: Enable this for added security.
• Websockets Support: Enable if your service uses WebSockets (e.g., Home Assistant, Jellyfin).

3. Enable SSL (Let’s Encrypt)

Go to the “SSL” tab:

• SSL Certificate: Select “Request a new SSL Certificate”.
• Force SSL: Enable this to automatically redirect HTTP traffic to HTTPS.
• I Agree to the Let’s Encrypt Terms of Service: Check this
  

  Frequently Asked Questions

  What is Nginx Proxy Manager and why should I use it at home?

  Nginx Proxy Manager (NPM) is a user-friendly interface for managing Nginx reverse proxies. It simplifies exposing local services to the internet securely with SSL, making self-hosting accessible without complex Nginx configurations.

  What are the essential prerequisites for setting up Nginx Proxy Manager?

  You’ll need a server (e.g., Raspberry Pi, NAS, VM) running Docker, a registered domain name, and port forwarding configured on your home router for ports 80 and 443 to your server’s IP address.

  Is it safe to expose my home services to the internet using Nginx Proxy Manager?

  While NPM provides SSL for secure connections, exposing services always carries risk. Ensure your backend applications are secure, use strong passwords, and keep all software updated. Implement a firewall and consider VPN access for sensitive services.

  Written by: Alex Torres, Editor at OpenClaw Resource

  Last Updated: May 2026

  Our Editorial Standards | How We Review Skills | Affiliate Disclosure

  Building a homelab? See our roundup of the best mini PCs for homelab use →

Keeping Your Homelab Healthy: Monitoring Your Home Server with Uptime Kuma

For anyone embracing the world of self-hosting and homelabs, the thrill of running your own services – whether it’s a Plex server, a Nextcloud instance, or a home automation hub – is undeniable. But with great power comes great responsibility, and that responsibility includes ensuring your servers are actually running. Nothing is more frustrating than discovering your services have been down for hours (or even days!) because you weren’t actively monitoring them. This is where a robust and user-friendly monitoring solution like Uptime Kuma comes into play. On OpenClaw Resource, we’re all about empowering your self-hosting journey, and Uptime Kuma is an essential tool in that arsenal.

In this comprehensive guide, we’ll dive deep into what Uptime Kuma is, why it’s a fantastic choice for your homelab, and walk you through the process of setting it up to keep a watchful eye on your precious home server infrastructure.

Why is Monitoring Your Home Server Crucial?

Before we jump into Uptime Kuma, let’s briefly touch upon why monitoring is non-negotiable for a healthy homelab. Imagine the following scenarios:

• Your media server goes offline, and your family can’t stream their favorite shows.
• Your automated backups fail silently, and a drive crash means lost data.
• Your smart home hub stops responding, leaving you in the dark (literally).
• A critical service like your VPN or DNS resolver experiences intermittent outages, causing frustration and wasted time troubleshooting.

Proactive monitoring helps you catch these issues early, often before they become major problems. It gives you peace of mind and ensures the services you rely on are always available.

Introducing Uptime Kuma: Your Homelab’s Watchdog

Uptime Kuma is an open-source, self-hosted monitoring tool that’s quickly gained popularity in the homelab community. Why? Because it strikes the perfect balance between powerful features and incredible ease of use. Think of it as your personal digital watchdog, constantly checking the status of your servers and services.

Key Features That Make Uptime Kuma Stand Out:

• Beautiful and Intuitive UI: Uptime Kuma boasts a modern, responsive, and easy-to-navigate web interface. You don’t need to be a seasoned sysadmin to understand what’s going on.
• Multiple Monitor Types: It supports a wide array of monitoring types, including HTTP(s), TCP Port, Ping, DNS, Docker Containers, Game Servers, and even Push monitors. This flexibility allows you to monitor almost anything in your homelab.
• Flexible Notification Options: Get alerted when something goes wrong! Uptime Kuma integrates with dozens of notification services, including Telegram, Discord, Email, Slack, Pushbullet, ntfy, and many more.
• Status Pages: Easily create public or private status pages to share the health of your services with family, friends, or even the wider community.
• Proxy Support: Useful for monitoring services behind a reverse proxy like Nginx Proxy Manager or Traefik.
• Lightweight: It’s designed to be efficient and not consume excessive resources, making it ideal for running on even modest homelab hardware like a Raspberry Pi.

Setting Up Uptime Kuma: A Step-by-Step Guide

The easiest and most recommended way to deploy Uptime Kuma in your homelab is using Docker. If you haven’t already, make sure you have Docker and Docker Compose installed on your server. We often recommend a dedicated server for core services, perhaps a mini PC running Proxmox VE or a bare-metal Ubuntu Server installation.

Step 1: Create a Directory for Uptime Kuma

First, create a dedicated directory on your server for Uptime Kuma’s configuration and data. This makes management and backups much easier.

mkdir -p /opt/uptime-kuma

Step 2: Create a Docker Compose File

Inside the newly created directory, create a docker-compose.yml file using your favorite text editor (like nano or vi):

nano /opt/uptime-kuma/docker-compose.yml

Paste the following content into the file:

version: '3.8'
services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    container_name: uptime-kuma
    volumes:
      - ./data:/app/data
    ports:
      - "3001:3001"
    restart: unless-stopped
    networks:
      - default

networks:
  default:
    driver: bridge

Let’s break down this file:

• image: louislam/uptime-kuma:1: Specifies the Docker image to use. We’re pulling the latest stable version.
• container_name: uptime-kuma: Gives your container a readable name.
• volumes: - ./data:/app/data: This is crucial! It maps a local directory (./data relative to your docker-compose.yml file) to the container’s /app/data directory. This ensures your Uptime Kuma configuration, database, and logs persist even if you recreate the container.
• ports: - "3001:3001": Maps port 3001 on your host machine to port 3001 inside the container. This is the port you’ll use to access the Uptime Kuma web interface. You can change the host port (the first 3001) if it conflicts with another service.
• restart: unless-stopped: Ensures Uptime Kuma automatically restarts if the server reboots or the container crashes.

Step 3: Deploy Uptime Kuma

Save the docker-compose.yml file (Ctrl+O, then Enter, then Ctrl+X in nano). Now, navigate to the directory where your docker-compose.yml file is located and run the following command:

cd /opt/uptime-kuma
docker compose up -d

The -d flag runs the container in detached mode, meaning it will run in the background. Docker will pull the image and start the container.

Step 4: Access Uptime Kuma and Initial Setup

Open your web browser and navigate to http://your_server_ip:3001 (replace your_server_ip with the actual IP address of your server). You’ll be greeted with the Uptime Kuma setup page. Create an admin username and a strong password.

Adding Your First Monitors

Once logged in, the dashboard will be empty. Click on “Add New Monitor” to start adding your services.

Monitoring a Web Service (HTTP/HTTPS)

This is perfect for checking if your websites or web applications are accessible. For example, to monitor your OpenClaw Resource blog if it were self-hosted:

1. Monitor Type: HTTP(s)
2. Friendly Name: OpenClaw Resource Blog
3. URL: https://your-blog-domain.com (or http://your-server-ip:port if local)
4. Interval: How often Uptime Kuma should check (e.g., 60 seconds).
5. Retries: How many times to retry before marking as down.
6. Push to Status Page: (Optional) Check this if you want it to appear on a public status page.
7. Notifications: Select your preferred notification service.

Monitoring a Local Service (TCP Port)

Use this for services that don’t have a web interface but listen on a specific port, like an SSH server, a database (e.g., PostgreSQL or MySQL), or a specific Docker container’s exposed port.

1. Monitor Type: TCP Port
2. Friendly Name: SSH Server
3. Host: localhost (if monitoring the server Uptime Kuma is on) or the IP of another server.
4. Port: 22 (for SSH) or the relevant port.

Monitoring a Docker Container

Uptime Kuma can directly monitor the health of your Docker containers. This is incredibly useful for homelabs running many services via Docker Compose.

1. Monitor Type: Docker Container
2. Friendly Name
   

   Frequently Asked Questions

   What is Uptime Kuma and why use it for a home server?

   Uptime Kuma is an open-source, self-hosted monitoring tool. It tracks the uptime and status of your home server and services, providing real-time alerts so you can quickly address any downtime or performance issues.

   What types of services can Uptime Kuma monitor?

   Uptime Kuma can monitor various services including HTTP/S, TCP ports, Ping, DNS, Docker containers, and even push metrics. This allows comprehensive oversight of your home server’s applications and network devices.

   How does Uptime Kuma notify me of server issues?

   Uptime Kuma supports a wide range of notification methods, including email, Telegram, Discord, Slack, Webhooks, and many more. You’ll receive instant alerts when your server or a monitored service goes down or recovers.

   Written by: Alex Torres, Editor at OpenClaw Resource

   Last Updated: May 2026

   Our Editorial Standards | How We Review Skills | Affiliate Disclosure

   Building a homelab? See our roundup of the best mini PCs for homelab use →