Introduction
OpenMediaVault (OMV) is a versatile, open-source NAS platform perfect for self-hosted workflows. By combining it with Docker, you can deploy powerful tools like DeepSeek—a state-of-the-art AI model optimized for coding, mathematics, and logical tasks—directly on your hardware. This guide walks you through running DeepSeek on OMV using Docker Compose, Ollama (for local AI management), and Open WebUI (a user-friendly interface), bypassing cloud dependencies and keeping your data private.

Why Host DeepSeek on Your OMV Server?

1. Full Data Control:
   Avoid sending sensitive code, financial data, or proprietary information to third-party servers.
2. Offline Accessibility:
   Use DeepSeek even without an internet connection—ideal for labs or remote workspaces.
3. Hardware Flexibility:
   Scale resources based on your needs. Run smaller models on modest hardware or leverage GPU acceleration for complex tasks.

Step-by-Step Installation Guide

Prerequisites

• OpenMediaVault (v6.x+) with OMV-Extras and Docker installed.
• A shared folder for Docker data (e.g., docker).
• At least 8GB of RAM (16GB+ recommended for larger models).

Step 1: Prepare Docker Directories

1. In the OMV web interface, go to Storage > Shared Folders.
2. Create subfolders for Ollama and Open WebUI under your existing Docker shared folder:
   • ollama (to store AI models)
   • open-webui (to store UI settings and chat history)

Step 2: Create the Docker Compose File

1. Navigate to Services > Compose > Files in the OMV interface.
2. Click Create, name the file deepseek.yml, and paste the following configuration:

version: "3.8"
services:
  ollama:
    image: ollama/ollama
    ports:
      - "11434:11434"
    volumes:
      - /sharedfolders/docker/ollama:/root/.ollama  # Use your shared folder path
    restart: unless-stopped

  open-webui:
    image: ghcr.io/open-webui/open-webui:main
    ports:
      - "8080:8080"
    environment:
      - OLLAMA_BASE_URL=http://ollama:11434
    volumes:
      - /sharedfolders/docker/open-webui:/app/backend/data
    depends_on:
      - ollama
    restart: unless-stopped

Notes:

• Replace /sharedfolders/docker with your actual Docker shared folder path (visible under Storage > Shared Folders).
• The ollama service hosts the AI models, while open-webui provides the chat interface.

Step 3: Deploy the Stack

1. In the OMV Compose plugin interface, select the deepseek.yml file.
2. Click Up to start the containers.
3. Verify the status under Services > Compose > Containers—both ollama and open-webui should show as “Running.”

Step 4: Access Open WebUI

1. Open http://<your-omv-ip>:8080 in a browser.
2. Create an admin account (disable public sign-ups later via Settings > Authentication).

Step 5: Download the DeepSeek Model

1. Option 2: Via Open WebUI:
   • Go to the Models tab.
   • Search for deepseek-coder:33b and click Download.

Option 1: Via OMV’s CLI (SSH or Services > SSH > Terminal):

docker exec -it ollama ollama pull deepseek-coder:33b

Step 6: Start Using DeepSeek

Select the deepseek-coder:33b model from the dropdown and ask questions like:

• “Write a script to back up my OMV shared folders to an external drive.”
• “Optimize this Python code for memory efficiency.”

Conclusion & Pro Tips

You’ve now transformed your OpenMediaVault server into a private AI workstation. To optimize your setup:

1. Integrate with OMV Workflows:
   Use Ollama’s API (port 11434) to connect DeepSeek to automation scripts or cron jobs.
2. Monitor Resource Usage:
   Check OMV’s System > Performance Statistics to ensure RAM/CPU stays within limits.
3. Update Containers:
   Periodically refresh your Docker images via the Compose plugin:
   • Click Pull for the deepseek.yml stack, then Down and Up to restart.
4. Experiment with Models:
   Try smaller models like deepseek-coder:6.7b for faster responses or quantized versions for lower RAM usage.

Final Checklist:

• [ ] Verify shared folder permissions match Docker’s requirements.
• [ ] Set up OMV’s firewall (Network > Firewall) to restrict external access to port 8080 if needed.
• [ ] Explore Open WebUI’s prompt templates for coding or math-specific tasks.

With DeepSeek running locally on OMV, you’re equipped to tackle complex challenges while maintaining full ownership of your data. Happy coding!

In today's fast-paced world, artificial intelligence (AI) has become an integral part of our daily lives. From enhancing productivity to providing entertainment, AI apps are revolutionizing the way we interact with technology. In this blog post, we'll explore some of the best free AI apps available for your phone, based on personal experiences and user feedback.

ChatGPT: The Versatile AI

ChatGPT is a multi-functional AI app that has gained popularity for its versatility. With the addition of the o3-mini model to the free package, ChatGPT has become a must-have app. It can assist with various tasks, from answering questions to generating creative content. Users appreciate its ability to provide accurate and relevant information, making it a valuable tool for both personal and professional use.

DeepSeek: A Strong Contender

DeepSeek is another free AI app that rivals ChatGPT Plus in terms of functionality. It offers a range of features that make it a top choice for users concerned about security. While there are some concerns about data privacy, DeepSeek's capabilities make it a strong contender in the AI app market. Its ability to perform complex tasks and provide insightful responses has earned it a loyal user base.

Perplexity: The Google Replacement

Perplexity is an AI app that aims to replace traditional search engines like Google. It offers intelligent and free search capabilities, making it a convenient tool for finding information quickly. Users have expressed a desire for a shortcut to access Perplexity on their phones, highlighting its popularity and usefulness. Whether you're looking for quick answers or in-depth research, Perplexity is a reliable choice.

Notion AI: Basic Note Management

Notion AI is designed for basic note management and synchronization across different platforms, including Apple and Windows devices. It helps users organize their thoughts and tasks efficiently, making it a valuable tool for productivity. While it may not have all the advanced features of other AI apps, its simplicity and ease of use make it a favorite among users who need a straightforward note-taking solution.

Meta AI: The Facebook Specialist

Meta AI, integrated into the Messenger app, provides free AI assistance for Facebook-related queries. Although it may not be as advanced as other AI apps, it excels in providing accurate information about Facebook. Users find it particularly useful for navigating the platform and getting quick answers to their questions. If you're an avid Facebook user, Meta AI is a handy tool to have.

Monica AI: The Multi-Purpose Assistant

Monica AI is a versatile and easy-to-use AI app that offers 40 free tokens daily. It can assist with a wide range of tasks, from answering questions to providing recommendations. Users appreciate its user-friendly interface and the variety of functions it offers. Whether you need help with daily tasks or want to explore new ideas, Monica AI is a reliable companion.

Copilot: The All-Rounder

Copilot is a free AI app that, despite its limitations, can perform a variety of tasks. Users have found it to be a helpful tool for different purposes, from generating content to providing support. While it may not be the most advanced AI app, its ability to handle multiple tasks makes it a valuable addition to your phone.

Gemini: The Compact Powerhouse

Gemini is a small but powerful AI app that offers a range of features. Despite its compact size, it provides a comprehensive set of tools for users. From answering questions to providing recommendations, Gemini is a reliable and efficient AI app. Its ability to deliver results quickly and accurately makes it a favorite among users who need a compact yet powerful AI assistant.

Conclusion

AI apps have become essential tools in our daily lives, offering a range of functionalities that enhance productivity and provide entertainment. Whether you're looking for a versatile assistant like ChatGPT or a specialized tool like Meta AI, there's an AI app out there to meet your needs. Explore these free AI apps and discover how they can make your life easier and more efficient.

Home Assistant is a powerful open-source platform for smart home automation. Running it on Proxmox VE, a robust virtualization environment, offers flexibility and efficiency. This guide will walk you through the process of setting up Home Assistant on Proxmox VE.

1. Creating and Setting Up a Virtual Machine (VM)

First, let's create a new VM specifically for Home Assistant:

• CPU: Allocate at least 2 cores.
• RAM: Assign a minimum of 2GB.
• Storage: Allocate at least 32GB of storage.
• Network: Use the default network settings.

Steps:

Log in to your Proxmox VE web interface. Click on "Create VM" in the top right corner and fill in the VM details (e.g., VM ID, Name).

On the OS tab, choose "Do not use any media".

On the System tab, choose OVMF (UEFI) for the BIOS, local-lvm for EFI Storage and Uncheck the Pre-Enroll keys.

On the Disks tab, delete the default one:

Configure the settings of CPU to 2 cores, and Memory to 2048 MB as recommended.

Under the "Network" tab, choose vmbr0 (depend on your network system).

Then click Next, and click Finish.

2. Download Home Assistant OS image and attach to HomeAssistant VM

First, download the Home Assistant OS image to your Proxmox server:

Go to the Home Assistant OS image from the official Home Assistant website. Right click on the KVM/Proxmox and Copy link.

In the Proxmox web interface, click on the pve and open Shell, then type in wget <space> <paste copied link>, then hit Enter.

wget https://github.com/home-assistant/operating-system/releases/download/13.2/haos_ova-13.2.qcow2.xz

Wait a litte time for the downloading to finish. After that, type "ls" to list the file. Use your mouse to select and copy filename (haos_ova-13.2.qcow2.xz). After that, run this command to unzip it:

unxz haos_ova-13.2.qcow2.xz

Wait a moment for the command completed and list the file using "ls" command again, you will see the file haos_ova-13.2.qcow2.

Now import the qcow2 image to Home Assistant VM as a disk using the command: qm importdisk <HA VM id> haos_ova-13.2.qcow2 local-lvm

qm importdisk 104 haos_ova-13.2.qcow2 local-lvm

Wait for the command finish, head back to Proxmox interface and you will see Unused Disk 0 under Hardware tab of the Home Assistant VM.

Click on Edit button, and because my disk is a SSD so I check on Discard check box, if you run a a HDD then just leave it unchecked.

Then click Add, and this will create a Hard Disk (scsi0)

3. Configuring the VM for Home Assistant

Now, let's configure the VM to ensure compatibility with Home Assistant:

Head to Option tab, double click on the "Boot Order" to open it, uncheck ide2 cdrom, net0, and check scsi0 disk the prioritize the Home Assistant OS disk to boot from. Then click OK to save setting.

Under "Options", enable "QEMU Guest Agent".

4. Installing Home Assistant OS on Proxmox

With the VM configured, it's time to install Home Assistant OS. Start the VM and open the console. Wait for Home Assistant OS installtion finish and you can see IP and port to access Home Assistant on the screen.

5. Accessing and Setting Up Home Assistant

Once the installation is complete, access the Home Assistant UI by open a web browser and navigate to http://<your_vm_ip>:8123. You may need to wait about 20 minutes for preparing Home Assistant.

After the preparing process finish, now you can complete the initial setup by click on "Create My Smart Home" button to start creating an account and configuring your home.

You also may need to secure your Home Assistant instance by setting up SSL and enabling two-factor authentication.

6. Additional Tips

To optimize your Home Assistant setup, consider the following tips:

• Automated Backups: Set up automated backups to ensure your data is safe.
• Adjusting VM Resources: Monitor and adjust the VM resources as needed for optimal performance.
• Adding Integrations: Explore and add integrations for various smart devices to enhance your smart home experience.

Conclusion

Running Home Assistant on Proxmox VE provides a flexible and efficient way to manage your smart home. With this setup, you can easily scale resources and take advantage of Proxmox's powerful features. For more advanced configurations, check out the Home Assistant documentation and the Proxmox VE wiki.

I hope this helps! If you have any questions or need further assistance, feel free to ask.

Today, I grabbed my laptop and a book and headed to a cafe. It's been a while since I've felt like going to a cafe alone, and as usual, I encountered some really sweet people and heartwarming moments that made my day.

I met a woman and her 5-6 year old daughter at the cafe. The woman took out her laptop and some books for her daughter and set them up on the table. She guided her daughter on which exercise to do, how many pages to write, and pointed out the difficult words first. Once they were done, she said to her daughter: "Now, let's each do our own thing."

And so, mother and daughter sat there working for over a few hours. Every now and then, the little girl would look up and ask her mom if she had written a word correctly, then she would go back to writing diligently.

Near the end, the mom asked:

• Would you like to eat vegetarian food?
• Yes, please.
• Okay, let's go to our usual place.
• Yes, mom.

Then, the mother and daughter moved to sit outside and read for a while before going home.

Wow, it was the first time I've seen a 'work date' between a mother and her child. Now I understand what it means to be friend with your children. Seeing their deep connection, I longed to be the kind of mother who could sit side-by-side with my child, exploring new things together, and feeling the warmth of family.

Installing OpenMediaVault (OMV) on a USB flash drive might seem unconventional at first, but it's a practice that's not only possible but also offers several advantages, especially for home server setups. Many professional-level servers boot from USB drives, and OMV is no exception. This article explores the key considerations, recommendations, and practical tips for setting up and maintaining a USB flash drive as an operating system (OS) drive for OpenMediaVault, covering important aspects like plugins, storage size, performance, and backup strategies.

1. Choosing the Right USB Drive

When using a USB flash drive for OMV, selecting the right drive is crucial for long-term stability and performance. Here are the main factors to consider:

Storage Size

While it’s technically possible to install OMV on an 8GB flash drive, this is not recommended. Although some users might try it, the limited space can quickly lead to problems, such as running out of storage for system updates or configurations. Users in forums often report issues when using 8GB flash drives for OMV installations, with many recommending a minimum of 16GB to avoid these problems. Ideally, a 32GB flash drive is a safe bet, providing ample room for the system and future updates without causing space constraints. Some experienced users even suggest going as large as 64GB, though this might be overkill unless you plan to run a large number of services directly from the USB drive.

USB Version

The speed of your USB drive has a direct impact on the performance of OMV. Using USB 2.0 can result in sluggish performance, particularly when it comes to system responsiveness and boot times. For optimal performance, you should use at least USB 3.0 or higher. USB 3.0 offers significantly faster read and write speeds compared to USB 2.0, which is critical when the operating system is being loaded and run directly from the drive. If you have access to USB 3.2, even better—though in most setups, USB 3.0 is more than sufficient.

2. Essential Plugins: Flash Memory Plugin

One of the key concerns when using a USB flash drive as the OS drive is the potential for excessive wear due to constant read/write operations. Flash drives have a limited number of write cycles, and frequent writes can degrade the drive over time, shortening its lifespan. To mitigate this risk, it is highly recommended to install the openmediavault-flashmemory plugin.

This plugin optimizes how data is written to the flash drive, minimizing wear by shifting frequently written data to RAM, thereby reducing the number of writes to the USB drive. This can significantly extend the lifespan of the flash drive while maintaining system performance. Without this plugin, you run the risk of prematurely wearing out the USB drive, which could lead to data loss or the need for a costly replacement.

3. Performance Considerations

Running OpenMediaVault from a USB drive, particularly with the right hardware, does not significantly impact system speed, as much of the data is handled in RAM. However, the performance of USB storage drives—especially older models—can vary widely. USB 3.0 or higher versions, as mentioned earlier, are essential for smooth operation. Many users report that their OMV setups, even when running from a USB flash drive, perform comparably to setups running on SSDs.

Moreover, if you plan to run Docker containers on OMV, it’s wise to use the USB flash drive for the OS while storing Docker data on a faster SSD or NVMe drive. This setup helps separate system operations from resource-intensive storage tasks, ensuring better overall performance.

4. Setting Up OMV on a USB Drive

Setting up OMV on a USB flash drive is relatively straightforward. Once you have your USB drive (preferably 16GB or larger) and the necessary plugins installed, you can proceed with the installation. Here’s a general outline of the process:

• Install OMV on the USB drive: You can use tools like Raspberry Pi Imager or Etcher to create a bootable OMV image on your USB drive.
• Configure the system: Once OMV is installed, boot from the USB and begin configuring your system.
• Install the flashmemory plugin: After setting up OMV, make sure to install the flashmemory plugin immediately to prevent unnecessary writes to the USB drive. This will optimize performance and prolong the life of your drive.
• Transfer OMV Configuration: If you have an existing OMV installation, you can use the omv-regen tool to move your configuration to the new USB setup, making migration simple and hassle-free.

5. Backup and Maintenance

One of the biggest advantages of using a USB flash drive for OMV is ease of backup and restoration. Since the entire OS is contained on a single USB drive, it’s incredibly easy to back up or clone. A tool like usbimager can be used to create an exact image of the drive, allowing for quick restoration in the event of a failure.

Backup Tips:

• Regular Backups: Periodically create an image of your USB drive to ensure you can quickly restore OMV to its previous state if necessary. It’s also a good idea to store backups in multiple locations (e.g., an external hard drive or cloud storage) for added security.
• Monitoring Drive Health: Keep an eye on the health of your USB flash drive. Some utilities can monitor the wear level of flash storage and alert you when the drive is nearing its limits.

6. Practical Considerations for Long-Term Use

Using a USB drive for OMV is a practical solution for home servers or small-scale deployments, but it’s important to keep in mind a few long-term considerations:

• Physical Placement: If your server case has limited USB ports, ensure the flash drive is securely fastened to avoid accidental disconnection. Some users recommend using adapters or zip ties to ensure the drive stays in place.
• Keep It Cool: USB drives can heat up, especially when under load. Ensure your case has adequate ventilation, or consider using a USB extension cable to place the drive in a cooler spot.

Conclusion

Using a USB flash drive as an OS drive for OpenMediaVault can offer excellent performance and convenience when set up properly. By choosing the right drive size, ensuring you’re using a USB 3.0 or higher, installing the flashmemory plugin, and maintaining regular backups, you can enjoy a stable and efficient system without the need for expensive SSDs or NVMe drives. This setup is ideal for users seeking an affordable, easily maintained, and flexible storage solution for their OMV-based home server.

Komga is a free and open-source media server for your comics, manga, magazines, and books. It supports comic book archives such as CBZ and CBR (except solid archives, for RAR5 see below); eBooks in EPUB format; and PDF files.

This article provides a concise guide on how to install Komga in OpenMediaVault (OMV) using Docker Compose.

Prerequisites

• OpenMediaVault installed and running
• Docker and Docker Compose installed on OMV
• Basic knowledge of using the OMV web interface

Step-by-Step Guide

1. Create Necessary Folders

1. Go to Storage > Shared Folders.
2. Create another folder named komga for Komga’s configuration and data.

2. Create Docker Compose File

Navigate to Services > Compose > Files and add the following content to the file:

version: '3.3'
services:
  komga:
    image: gotson/komga
    container_name: komga
    volumes:
      - /path/to/komga/config:/config
      - /path/to/komga/data:/data
    ports:
      - 25600:25600
    restart: unless-stopped

Remeber to replace /path/to/komga/config and /path/to/komga/data with the actual paths to your komga folder.

In my case, because I have already add global environment file for OpenMediaVault docker, so my compose file is simple as the picture below:

After carefully finish editing all the parameters, Save the compose file and click Up button to deploy Komga container.

3. Initial login and setup

Open your web browser and starting to use Komga. At this time, Komga should now be running and accessible at http://<your-OMV-IP>:25600.

At the first step, Komga will ask you to create a user account. Choose an email and password, then click on Create User Account and start using Komga.

Conclusion

You have successfully installed Komga on OpenMediaVault using Docker Compose. You can now start adding your comics, manga, and books to Komga and enjoy your media library.

qBittorrent is a popular, open-source BitTorrent client that offers a clean interface and a wide range of features. It is designed to be a lightweight alternative to other BitTorrent clients while providing the same level of functionality. With qBittorrent, users can manage their torrent downloads efficiently, thanks to features like an integrated search engine, RSS feed support, and remote control via a web user interface. In this blog post, we will go through step-by-step to install qBittorrent on OpenMediaVault using Docker Compose, as well as some initial setting for it.

Step-by-Step Guide to Install qBittorrent on openmediavault Using Docker Compose

Prerequisites:

• openmediavault installed and running
• OpenMediaVault Extras installed. You can find the full guide to install omv-extras here.

Step 1: Prepare Your Environment

1. Log in to openmediavault: Access your openmediavault web interface.
2. Enable Docker Repo: Navigate to System > omv-extras and enable the Docker repository. Click Save and then Apply.
3. Install Docker and Docker Compose: Go to System > Plugins, search for docker and openmediavault-compose, and install both plugins.

Step 2: Create a Docker Compose File

Go to Services -> Compose -> Files, then click New to create new docker-compose.yaml file for qBittorrent.

For me, I use the docker-compose content from linuxserver: https://hub.docker.com/r/linuxserver/qbittorrent

---
services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
    volumes:
      - /path/to/qbittorrent/appdata:/config
      - /path/to/downloads:/downloads #optional
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    restart: unless-stopped

Paste the above content to Remember to change the parameters according to your system. Then click Save.

Step 3: Deploy the qBittorrent Container

Click "Up" button to pull the docker image and deploy the container. Wait for it's status change to "Up".

Step 4: Access the qBittorrent Web Interface

1. Open Your Browser: Navigate to http://<your-server-ip>:8080 to access the qBittorrent web interface.
2. Login: The default username is admin and the default password is automatically generated. You can get the password by SSH into OpenMediaVault and run the following command to read to qBittorrent container log and get the password there.

docker logs qbittorrent

Make sure to change these credentials after your first login for security reasons.

Recommended First-Time Settings for qBittorrent

Change Default Credentials: Go to Options > Web UI and change the default username and password.

Set Download Locations: Configure your download locations under Downloads to ensure your files are saved in the correct directories. For me I also config other settings as below:

Config OpenTracker: udp://tracker.opentrackr.org:1337/announce

Configure Bandwidth Limits: Set appropriate upload and download speed limits under Speed to manage your network usage.

Enable IP Filtering: For added security, enable IP filtering under Connection.

By following these steps, you should have a fully functional qBittorrent setup on your openmediavault server using Docker Compose. Enjoy your efficient and powerful torrent management system!

Homelab enthusiasts often face the challenge of securely exposing their services to the internet. Whether it's a self-hosted website, a personal media server, or an automation system, making these services accessible from outside your local network requires careful consideration. Two popular solutions for this are Reverse Proxies and Cloudflare Tunnels. Each has its own advantages and drawbacks, making it essential to understand their differences to choose the most suitable one for your homelab setup.

Introduction to Reverse Proxy

A reverse proxy is a server that sits between the client and your web server, forwarding client requests to the appropriate server and returning the server's response to the client. This setup is commonly used to balance the load across multiple servers, provide caching, enhance security, and simplify access to internal resources.

When setting up a homelab, reverse proxies play a crucial role in managing and securing web traffic. Several popular reverse proxies are widely used in the homelab community due to their versatility and powerful features:

1. NGINX: Known for its performance and scalability, NGINX is a popular choice for both web servers and reverse proxies. It's highly configurable, supports load balancing, SSL termination, and caching, making it ideal for complex homelab setups.
2. Apache HTTP Server: As one of the oldest and most reliable web servers, Apache also functions as a robust reverse proxy. It offers extensive modules for various functionalities, including security, URL rewriting, and content delivery, making it a flexible option.
3. Traefik: Traefik is a modern reverse proxy designed specifically for dynamic environments. It integrates seamlessly with containerized services, such as Docker and Kubernetes, automatically managing routes and SSL certificates, making it perfect for homelabs that rely on microservices.
4. Caddy: Caddy is known for its simplicity and automatic HTTPS management. It’s a user-friendly reverse proxy that requires minimal configuration, making it an excellent choice for beginners or those looking for a straightforward setup with secure defaults.

These reverse proxies cater to different needs, offering a range of features that can enhance the performance, security, and manageability of your homelab services.

Pros of Reverse Proxy

• Increased Control: With a reverse proxy, you have complete control over your configuration, including SSL certificates, access rules, and load balancing.
• Flexibility: Reverse proxies can handle complex setups, allowing you to route different subdomains or paths to specific services.
• Performance Optimization: By caching content and compressing data, reverse proxies can improve performance and reduce bandwidth usage.

Cons of Reverse Proxy

• Complex Setup: Configuring a reverse proxy requires knowledge of networking and server management. You'll need to manage DNS records, SSL certificates, and firewall settings.
• Security Risks: Exposing a reverse proxy to the internet can introduce security vulnerabilities if not properly configured and maintained.
• Maintenance: Regular updates and monitoring are required to keep the reverse proxy secure and functional.
• Can not expose your services if your network is behind Carrier-Grade NAT (CGNAT).

Introduction to Cloudflare Tunnel

Cloudflare Tunnel is a service provided by Cloudflare that creates a secure tunnel between your local network and Cloudflare's network, allowing you to expose your services to the internet without opening any ports on your router. This is achieved by installing a small client on your local machine that maintains a persistent connection to Cloudflare, which then routes incoming traffic to your services.

Pros of Cloudflare Tunnel

• Simplicity: Cloudflare Tunnel requires minimal setup. There's no need to configure DNS, manage SSL certificates, or open ports on your router.
• Security: Since the tunnel is initiated from within your network, there’s no need to expose your network to the internet, reducing potential attack vectors.
• Global CDN and DDoS Protection: Cloudflare provides additional benefits like DDoS protection and content delivery network (CDN) integration, which can enhance the security and performance of your services.
• When your network is behind Carrier-Grade NAT (CGNAT), Cloudflare Tunnel offers a significant advantage over a reverse proxy. With CGNAT, it's often impossible to directly expose your services to the internet because you don't have a public IP address. Cloudflare Tunnel bypasses this limitation by establishing an outbound connection from your network to Cloudflare's servers, allowing you to securely expose your services without needing to configure port forwarding or deal with the complexities of CGNAT. This makes Cloudflare Tunnel a seamless and hassle-free solution for users in CGNAT environments.

Cons of Cloudflare Tunnel

• Limited Control: While Cloudflare simplifies setup, it also limits the amount of control you have over your configuration. Custom routing and advanced features may require a higher-tier plan or may not be available at all.
• Dependency on Cloudflare: Your service’s availability becomes dependent on Cloudflare’s infrastructure. If Cloudflare experiences downtime or issues, your services may be affected.
• Potential Costs: While Cloudflare Tunnel is free for many use cases, certain features or high-traffic scenarios may incur costs, especially if you need advanced functionality.

How to Choose the Right Solution for Your Homelab

When deciding between a reverse proxy and Cloudflare Tunnel for your homelab, consider the following factors:

1. Technical Expertise:
   • If you have experience with server management, networking, and DNS, a reverse proxy might be the better option for you. It offers more control and flexibility but requires more hands-on work.
   • If you prefer a simpler solution that requires minimal configuration, Cloudflare Tunnel is a great choice. It’s easier to set up and manage, especially if you’re not comfortable with advanced networking concepts.
2. Security Considerations:
   • If security is a top priority and you want to avoid exposing your network to the internet, Cloudflare Tunnel is the safer option. It minimizes the attack surface by not requiring open ports.
   • However, if you’re confident in your ability to secure a reverse proxy (e.g., through regular updates, SSL certificates, and strict firewall rules), a reverse proxy can be just as secure, with the added benefit of more granular control.
3. Cost and Resources:
   • Cloudflare Tunnel is cost-effective for most small-scale homelab projects, but if your usage scales up or you need premium features, costs can add up.
   • A reverse proxy, on the other hand, typically only involves the cost of running your server (e.g., electricity, domain name, etc.), but you’ll need to invest more time and effort in maintenance.
4. Performance Needs:
   • If you need global CDN support and DDoS protection, Cloudflare Tunnel provides these out of the box, which can be beneficial for publicly accessible services.
   • A reverse proxy can also be optimized for performance, but it requires more manual configuration and management.

My Personal Setup: Combining Cloudflare Tunnel and Wireguard VPN

In my homelab, I use a combination of Cloudflare Tunnel and Wireguard VPN to manage access to my services. Cloudflare Tunnel handles the public-facing web services, offering a simple and secure way to expose these services without opening any ports on my router. This setup leverages Cloudflare’s global network for performance and security, making it a robust choice for web services.

For accessing my local network services that I prefer to keep private, I use Wireguard VPN. This allows me to connect securely to my internal network from anywhere, accessing services like file shares, automation systems, and other resources that I don’t want exposed to the broader internet. This hybrid approach provides both the security and simplicity I need while maintaining control over how my services are accessed.

Conclusion

Choosing between a reverse proxy and Cloudflare Tunnel depends largely on your technical skill level, security needs, and the scale of your homelab project. A reverse proxy offers greater control and flexibility, making it ideal for those with technical expertise who want to customize their setup. In contrast, Cloudflare Tunnel provides simplicity and robust security features with minimal effort, making it a perfect fit for those who prefer a hassle-free solution.

Ultimately, both solutions are viable for exposing homelab services to the internet, and your choice should align with your specific requirements and comfort level. For those looking to balance security and ease of use, combining Cloudflare Tunnel for public services with a VPN like Wireguard for private network access could be the ideal approach.

Docker networking is a crucial aspect of containerization, enabling communication between containers and external applications. This tutorial covers the different Docker network drivers and their specific use cases, along with commands to create each type of network.

Bridge Network

The default network mode, the bridge network, connects containers on the same host. It creates a virtual network allowing containers to communicate with each other using IP addresses. However, it has limitations, especially in production environments. Creating a user-defined bridge network allows for DNS-based communication between containers, enhancing flexibility and ease of use. These are the advantages of user-defined bridge network in docker:

1. Automatic DNS Resolution: Containers on a user-defined bridge network can resolve each other by name or alias, making it easier to manage and connect services.
2. Better Isolation: User-defined bridges provide better isolation as only containers attached to the same user-defined network can communicate with each other.
3. Attach/Detach Flexibility: Containers can be attached or detached from user-defined networks on the fly without needing to stop and recreate them.
4. Configurable Settings: Each user-defined network creates a configurable bridge, allowing customization of settings like MTU and iptables rules.

Command to create a Bridge network:

docker network create --driver bridge my_bridge_network

None Network

The none network mode completely isolates the container from the host and other containers. Only the loopback interface is created, making it ideal for running batch jobs or data processing pipelines where network isolation is required.

Command to create a None network:

docker network create --driver none my_none_network

Host Network

In host network mode, the container shares the host’s networking namespace, appearing as a regular application on the host. This mode is used to optimize performance and is suitable for applications requiring high port usage. However, it lacks network isolation, which can be a drawback in certain scenarios.

Command to create a Host network:

docker network create --driver host my_host_network

IPvlan Network

IPvlan is a lightweight network virtualization technique that assigns IP addresses from the same CIDR range as the host. It eliminates the need for port mappings, making it easier to provide access for external-facing services. This mode is beneficial for applications requiring direct network access without additional complexity.

Command to create an IPvlan network:

docker network create -d ipvlan \
  --subnet=192.168.1.0/24 \
  --gateway=192.168.1.1 \
  -o parent=eth0 my_ipvlan_network

Macvlan Network

Macvlan assigns a unique MAC address to each container’s virtual network interface, making it appear as a physical network interface. This mode is suitable for legacy applications or those monitoring network traffic, providing direct connectivity to the physical network.

Command to create a Macvlan network:

docker network create -d macvlan \
  --subnet=192.168.1.0/24 \
  --gateway=192.168.1.1 \
  -o parent=eth0 my_macvlan_network

Overlay Network

The overlay network driver creates a distributed network among multiple Docker daemon hosts, allowing secure communication between containers on different hosts. It is commonly used with Docker Swarm but can also connect individual containers. This mode is ideal for managing containers at scale, especially in production environments.

Command to create an Overlay network:

docker network create -d overlay my_overlay_network

Conclusion

Understanding Docker networking modes is essential for optimizing container communication and performance. Each network driver has its unique advantages and use cases, making it crucial to choose the right one based on your application’s requirements.

AdGuard Home is a powerful tool for blocking ads and tracking across your network. If you manage multiple instances of AdGuard Home, keeping their settings synchronized can be challenging. Using Portainer and AdGuardHome-Sync, you can automate this process efficiently. In this blog post, we’ll guide you through the steps to sync your AdGuard Home settings using a Portainer stack.

Prerequisites

Before we start, ensure you have the following:

• Multiple instances of AdGuard Home running.
• Docker and Portainer installed on your system.
• Basic understanding of Docker, Portainer, and YAML configuration files.

Step-by-Step Guide

Step 1: Create a Portainer Stack for AdGuardHome-Sync

AdGuardHome-Sync is a tool designed to synchronize settings between multiple AdGuard Home instances. To deploy it using a Portainer stack, follow these steps:

• Open Portainer and navigate to the Stacks section.
• Click on Add stack and name it adguardhome-sync.

Step 2: Paste the docker-compose content to the Web Editor form, as below. Remember to change origin and destination IP, port, username and password accordingly to your actual system.

---
version: "2.1"
services:
  adguardhome-sync:
    image: quay.io/bakito/adguardhome-sync
    container_name: adguardhome-sync
    command: run
    environment:
      - ORIGIN_URL=http://192.168.1.26:3000 #Your origin Adguard Home instance -> change as necessary
      - ORIGIN_USERNAME=username #change as necessary
      - ORIGIN_PASSWORD=password #change as necessary
      - REPLICA_URL=http://192.168.1.27 #Your destination Adguard Home instance change as necessary
      - REPLICA_USERNAME=dbtech #change as necessary
      - REPLICA_PASSWORD=password #change as necessary
      # Replicate to other instances if needed
      - REPLICA1_URL=http://192.168.1.4 #change as necessary
      - REPLICA1_USERNAME=username #change as necessary
      - REPLICA1_PASSWORD=password #change as necessary
      - CRON=*/1 * * * * # run every 1 minute
      - RUNONSTART=true
    ports:
      - 9876:8080 #change as necessary
    restart: unless-stopped    

Step 3: Deploy the Stack

• Click on Deploy the stack in Portainer.
• This will start the AdGuardHome-Sync container with the specified configuration.

Step 4: Verify Synchronization

Check the container logs to ensure that the synchronization is working correctly.

Tips and Tricks

• Security: Ensure that your AdGuard Home instances are secured with strong passwords.
• Monitoring: Regularly check the logs to monitor the synchronization process.
• Updates: Keep your Docker images up to date to benefit from the latest features and security patches.

By following these steps, you can easily keep your AdGuard Home instances synchronized, ensuring consistent ad-blocking and DNS filtering across your network. Happy syncing!

AdGuard Home is a comprehensive network-wide software that blocks ads and tracking services, enhancing privacy and security for all devices connected to a network. It operates as a DNS server, filtering out unwanted content before it reaches your devices, similar to a local version of a public DNS service like AdGuard DNS.

Here's a brief overview:

1. Ad-Blocking: AdGuard Home blocks ads across all devices on your network, including smartphones, tablets, and smart TVs. This is especially useful for devices where traditional ad blockers may not work as effectively.
2. Privacy Protection: By blocking tracking scripts and analytics systems, AdGuard Home prevents third parties from collecting your data, offering a higher level of privacy.
3. DNS-Based Filtering: As a DNS server, AdGuard Home filters requests at the network level. This means that ads and trackers are blocked before they even reach your devices, reducing the amount of data downloaded and speeding up your internet connection.
4. Customizability: Users can create custom filters, blocklists, and allowlists to tailor the blocking to their needs. It also supports parental control features, allowing users to block access to adult content.
5. Open Source: AdGuard Home is open-source, allowing users to inspect the code, contribute to its development, and ensure that it operates transparently.
6. Cross-Platform: It can be installed on various devices, including Raspberry Pi, Linux, Windows, macOS, and even in Docker containers, making it highly versatile.

In summary, AdGuard Home provides a robust, customizable, and privacy-focused solution for blocking ads and tracking across your entire home network.

In this guide, we’ll walk you through the steps to install AdGuard Home on OpenMediaVault (OMV) using openmediavault-compose. This setup will help you manage your network’s DNS and block ads efficiently.

Prerequisites

• OpenMediaVault installed and running
• openmediavault-compose plugin installed
• Basic understanding of Docker and networking

Step 1: Create a MacVLAN Network

First, we need to create a MacVLAN network for the AdGuard container. This allows the container to have its own IP address, making it easier to manage ports.

1. Access OMV Compose Plugin: Go to the OMV web interface and navigate to the openmediavault-compose plugin.
2. Create Network: Under the “Services -> Compose -> Networks” tab, create a new network. Name it local-network.
3. Configure Network:
   • Driver: select macvlan.
   • Parent Network: Select your main network interface, in my case it is enp2s0.
   • Subnet: Enter your subnet (e.g., 192.168.1.0/24).
   • Gateway: Enter your gateway (e.g., 192.168.1.1).
   • IP range: Enter your expected IP for Adguard Home (e.g., 192.168.1.200/32).
   • Click Save.

Step 2: Create Docker Compose File

Now, we’ll create a Docker Compose file to configure and run the AdGuard Home container.

1. Create Compose File: Go to Services -> Compose -> Files, create a new compose file and name it adguard.
2. Add Configuration: Paste the following configuration into the compose file. Remember to change the ipv4_address to match your network configuration. Then click Save.

---
services:
    adguardhome:
        container_name: adguardhome
        image: adguard/adguardhome
        networks:
          adguardhome:
            ipv4_address: 192.168.1.200  #Change this to your ip address
        volumes:
            - CHANGE_TO_COMPOSE_DATA_PATH/adguardhome/workdir:/opt/adguardhome/work
            - CHANGE_TO_COMPOSE_DATA_PATH/adguardhome/confdir:/opt/adguardhome/conf
        restart: unless-stopped
        ports:
            - 53:53/tcp
            - 53:53/udp
            - 67:67/udp
            - 68:68/udp
            - 80:80/tcp
            - 443:443/tcp
            - 443:443/udp
            - 3000:3000/tcp
            - 853:853/tcp
            - 784:784/udp
            - 853:853/udp
            - 8853:8853/udp
            - 5443:5443/tcp
            - 5443:5443/udp
networks:
   adguardhome:
      name: local-network  #This is the name of our macvlan
      external: true

Step 3: Deploy AdGuard Home

Deploy the AdGuard Home container using the compose file.

1. Deploy Container: In the openmediavault-compose plugin, select the adguard compose file and click “Up”.
2. Verify Deployment: Ensure the container is running and accessible.

Step 4: Configure AdGuard Home

Finally, configure AdGuard Home through its web interface.

1. Access Web Interface: Open a web browser and go to http://192.168.1.200:3000.
2. Initial Setup: Follow the on-screen instructions to complete the initial setup.
3. Set DNS Server: Point your router’s DNS settings to the AdGuard Home IP address (e.g., 192.168.1.200).

Conclusion

Congratulations! You’ve successfully installed and configured AdGuard Home on OpenMediaVault using openmediavault-compose. This setup will help you manage your network’s DNS and block ads effectively.

Feel free to customize this blog post to better fit your style and audience! If you have any questions or need further assistance, let me know.

OMV-Extras is a powerful plugin for OpenMediaVault (OMV) that significantly expands its capabilities. It offers a range of additional features and tools, making your NAS more versatile and efficient.

2. Why Install OMV-Extras?

• Expand OMV functionality: Access a wider range of plugins and applications.
• Simplify installation: Streamline the process of installing various software packages.
• Enhance performance: Optimize your NAS for specific tasks.

3. Prerequisites:

• An OpenMediaVault server up and running. If you don't have one, you can find out how to install OpenMediaVault in the box below.
• Basic understanding of Linux command line (for command-line method).
• SSH access to your OMV server (for command-line method).

Step-by-Step Guide to Install OpenMediaVault on Proxmox and Enabling SMB Share

A comprehensive guide for installing OpenMediaVault on Proxmox and setting up an SMB share for easy file sharing across your network

KenBin lab - Homelab and techKen Bin

4. Installation of OMV-Extras using command-line:

Step1: Open a terminal window and SSH into your OMV server.

Step2: Execute the following command:

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash

Wait for the installation process to complete.

5. Verifying Installation:

Check if the omv-extras plugin is listed in the "System -> Plugins" section of the OMV web interface to ensure OMV-Extras is installed correctly.

6. Additional Tips:

• Always back up your system before making significant changes.
• Refer to the official OMV-Extras documentation for detailed instructions and troubleshooting.
• Explore the available plugins and tools to maximize the benefits of OMV-Extras.

By following these steps, you should have successfully installed OMV-Extras on your OpenMediaVault server. Enjoy the expanded capabilities and features it brings!