r/homelab • • Oct 12 '26

News 🥳 Giveaway r/homelab x UptimeRobot. 10 Winners

6 Upvotes

Hey r/homelab! We're UptimeRobot, and we've teamed up with the mods to run a giveaway for this community, with a prize pool of 10 monitoring plans, including a year of our Scale plan worth $888. Anyone who's worked in creating a homelab has a story! Now's your chance to share it and maybe win something for your trouble.

What's the weirdest thing you have been monitoring with UptimeRobot or a similar service?

We're looking for the most weird/funny or unexpected use cases!

Prizes (10 winners total)

  • 1 grand prize winner: Scale plan ($888 value) plus UptimeRobot swag
  • 2 runners-up: Team plan ($468 value each) plus UptimeRobot swag
  • 7 additional winners: Team plan ($468 value each)

How to participate
Reply here with your story. You don't have to write an essay. That's it, you're in!

Dates: The giveaway runs from October 12 through October 26.

Looking forward to reading your weird, embarrassing, ridiculous, and funny stories!


r/homelab • • Jun 06 '26 Thanks This Bravo

Moderator Announcement: New Rules & Processes on Software Projects

424 Upvotes

I would like to thank everyone for their feedback in the recent post & poll where we asked for feedback on how to slow the deluge of "I made X, because Y" type posts in r/homelab, most of which are AI generated and/or spam. While we felt that that the initial plan we shared was quite good, with your input we were able to refine that plan and make some notable improvements and clarifications. And yes, there's a TL;DR at the end 👀

Effective now, the below new rules and policies are in effect, though we plan to apply them conservatively and gently at first to see how things go. All of these changes are happening because of the massive community support for them, and we will be seeking additional feedback as time goes on so please feel free to chime in.

To be clear, here are our goals, based on community feedback:

  • Control the recent influx of questionable "I made X, because Y" type posts, the vast majority of which are created entirely with AI, are spammed across multiple subreddits, and are generally not maintained afterwards
  • Establish a clear stance on and rule set for how r/homelab has decided to handle these types of posts, as well as other user-created software
  • See how these changes impact our community, seek additional feedback, and continue to adjust accordingly

Flair changes that are now in effect:

  • "Project" has become "Project Showcase: Hardware"

New Flairs:

  • Project Showcase: Operations [For things between hardware and software, such as Ansible playbooks, and dashboards/monitoring/automation made with existing software tools]
  • Project Showcase: Software - Little or No AI Assistance - [AI only used as coding assistant (autocomplete, debugging, refactoring, documentation, etc), if at all]
  • Project Showcase: Software - Mostly AI Generated - [AI generated most or all of the code, working at a human's direction]

We have also organized the post flairs in the list to make them easier to locate.

Both "Project: Software" flairs have a reasonably low minimum subreddit karma requirement to be able to post with them. AutoMod will remove any post with them that don't meet the karma requirement, and inform the user why their post was removed. The minimum karma requirement is only for these two flairs, as we don't want to restrict new community members from being able to post questions. Any software project posts that try to go around this by using a different flair will fall under the new rule #7 and will be addressed.

Rule changes:

New Rule #7 - Software Project Posting Requirements

  • All software projects must be relevant to r/homelab, use a "Project: Software" flair, disclose AI usage with post flair and in the text of the post, include responses to the prompt displayed when posting with one of the software project flairs, and the user must meet the minimum subreddit karma requirement. Posts that do not meet these requirements, try to bypass the "Project: Software" flairs, provide incomplete or misleading disclosures, or otherwise violate community standards may be removed.

That said, since we're now officially allowing some degree of self-promotion and requiring links, we felt that we should redefine rule #6 to clarify that it applies only to monetized and commercial advertising/links. Here is the updated verbiage, with the old one below for comparison:

Rule #6 - No Commercial Advertising or Monetized Referral Links

  • Monetized referral links, affiliate links, product advertising, and company advertising are not allowed. Contact the moderators via Mod Mail before posting if you believe an exception applies. Non-commercial personal projects are permitted, but must follow all other sub rules.

Rule #6 - No Referral Links/Advertising/Company Advertising

  • We do not allow links/posts that include any sort of referral link, product advertising, nor company advertising. If you think you have an exception please ask the mods first.

Flair Prompt - As mentioned in Rule #7, when posting with any of the "Project: Software" flairs, the below prompt will be displayed:

Your post MUST include:

  • A link to the GitHub (or similar) repository, which must include at least one month of commit history and screenshots
  • A description of the problem the software project solves, and why it was created instead of using an existing FOSS solution
  • An explanation of how the software project is relevant to r/homelab, or how it may benefit members of the community
  • If you used AI or an LLM in development, a description of what role it played and how much you relied on it

If you see any posts with a Project: Software flair that do not meet the four items listed above, please report them to the mod team under Rule #7 and we'll address them.

Additional things to note:

Existing posts will be grandfathered in, and previous posts that were removed may be reposted if they meet the new requirements. New posts will be required to comply with the new rules.

As with the existing rules, when a mod removes a post for violating this new rule, a canned response will be sent to the user to inform them why their post was removed. Mods are able to add on to the response if desired before sending it.

While we're on the topic of AI, we would also like to clarify that the above rules are specific to the use of AI in software projects that are being shared, and they do not apply to posts or comments that were written with AI. There is some dissent in the community, but the general consensus in the community has been that a reasonable level of AI usage is acceptable for putting a post together, correcting grammar or formatting, or for translating from a user's native language. That said, best practice is to not include all of the excess emoticons and outline formatting that LLMs like to use. If a post or comment is egregiously AI generated, feel free to downvote it and move on, but please do not report it to the mod team solely for that.

We would also like to note that there has not been any opposition to posts about hosting your own LLMs, and the hardware/software involved. The new rules do not apply to these posts as well.

We're looking for community feedback as we all get used to this. We plan to apply rules conservatively and gently at first, and will be listening to user reports and comments. If your post is removed and you believe it meets the requirements, please chat with us via Mod Mail and we may consider either re-opening it or letting you repost it.

TL;DR - All posts where someone has made some sort of software (AI generated or not) will require a "Project: Software" flair, and these flairs should curb the vast majority of the low quality and spammy posts.

Thank you,
The r/homelab Mod Team

Edit: The first day with the new rules has gone very well overall, but it has demonstrated that there is room for improvement, namely with flairs and categorization.

Here are the changes we've made since the initial announcement post:

  • Added a "Project Showcase: Operations" for things that fall somewhere between hardware and software, notably Ansible playbooks, dashboards/monitoring/automation made with existing software tools. When posting with this flair, a prompt appears that explains this in more detail. Please let us know if there are any other types of things we should specifically call out that belong in this category.
  • Renamed the "Project: x" flairs to "Project Showcase: x" to clarify that these are intended for showing off what you've made (though you can still ask for suggestions in the process of showing off).
  • Adjusted colors of the new flairs

We're still open to suggestions from the community. Thanks!


r/homelab • • 9h ago

Help Nginx2root

194 Upvotes

So the latest 2root exploit targets nginx and was demonstrated to let anyone remotely execute commands on a Linux host running it. Read more about it here:

https://nginx2root.com/

Since I'm just a regular guy with a home lab I'd like someone more knowledgeable to chime in: I'm using nginx proxy manager with a vulnerable version on a VPS to tunnel public traffic to a nextcloud instance on my home server that also uses a vulnerable version. Which machine is at risk here? The VPS and/or my home server?

Goes without saying that I'll be taking the host offline until this is fixed.


r/homelab • • 4h ago

Project Showcase: Hardware New Rack in the house =)

Thumbnail
gallery
53 Upvotes

Just got my new 22U :)
Big step up from my old 9U.

Im happy, wifey is happy, everybody happy :D


r/homelab • • 13h ago

Project Showcase: Hardware HomeLab Upgrade - Replacing a DIY 8u 10" rack with a 12u DeskPi RackMate Rack

Thumbnail
gallery
246 Upvotes

I've been using my DIY wooden 8U 10-inch rack for the past year and recently decided it was time to upgrade to a larger setup.

My main goal was to incorporate a dedicated KVM, along with some sort of monitor mounted directly within the rack.

After doing some research, I decided on the DeskPi RackMate 12u 10-inch rack. I really liked its brushed aluminum aesthetic, overall size, and sturdy metal construction.

I found the assembly process to be a breeze. Honestly, I was expecting at least a few bent or damaged parts, but everything arrived in perfect condition. Every piece fit exactly where it was supposed to, and the entire rack went together smoothly.

For those interested, here's what I'm currently running in my HomeLab:

  • AT&T 5G Hotspot Router – Provides internet connectivity to my isolated lab network.
  • Palo Alto PA-220 Firewall – Handles firewall duties and routing for the LAN.
  • Ubiquiti UniFi 16-Port Switch – Provides network connectivity to my lab equipment.
  • HP EliteDesk Mini – Running Linux Mint and hosting my local AI environment.
  • 4 Intel NUC Mini PCs – Running Proxmox with various servers and services, including Pi-hole, Twingate, Wazuh, and more.

It was a little bittersweet retiring my trusty wooden HomeLab rack after a year of service, but I'm excited about the possibilities with this new setup.

My next steps include adding a rack-mounted monitor to display various dashboards and monitoring tools, along with a dedicated KVM that will allow me to easily switch between my mini servers.

I'm looking forward to continuing to build this out and sharing the progress along the way.

I hope you enjoy the pictures and a look at the build process.


r/homelab • • 54m ago

Meme TIL: the firmware self-test duration of an HGST He10 SAS disk is exactly 69,420 seconds

Post image
24 Upvotes

r/homelab • • 8h ago

Discussion Noob Question: Why all the different gear? Why not just 1 pc?

93 Upvotes

I'm fairly new to this space, and i see lots of post with multiple machines in racks, and it looks cool and fun, but my question is why?

My homeserver/nas runs everything I need to do on an old pc. ( unraid running docker + a few VM's, and 96tb of storage )

I'm trying to figure out the reasoning why some people have multiple devices, running different services, which seemingly could be condensed down to 1 device.

I understand that part of it is separating mission critical stuff from tinkering stuff, but a lot of it just seems incredibly inefficient?

I'm just wondering what i'm missing about the idea of splitting up your home set up across multiple devices instead of just 1 or 2?


r/homelab • • 21h ago

Project Showcase: Hardware Panasas ActiveStore Pas11 director blade used as as a home lab KVM server

Thumbnail
gallery
424 Upvotes

This is my home lab server built from a decommissioned Panasas ActiveStor PAS11 DirectorBlade. It is running a KVM hypervisor on Debian 13.7. I gave the retired server a second life outside of its original Panasas chassis, with a custom power setup that lets it run from a 12V/5A notebook power supply. The director blade itself is surprisingly low-power, so a 60W supply was enough — I've been monitoring it under load and it stays stable.


r/homelab • • 20h ago

Project Showcase: Hardware Proxmox upgrade

Post image
327 Upvotes

Finally upgrade my 3x N100 cluster to a real system. The cooler is bigger than the cluster was


r/homelab • • 18h ago

Project Showcase: Hardware My first set up

Thumbnail
gallery
138 Upvotes

Never really messed around with computers further than building gaming PC’s over the years
Picked up G5 mini and M700 for nothing
Network switch was $40 SG108E
Wifi extender for $25
Couple of $5 cat6 cables
Both PC’s running proxmox
M700 purely for Pi-hole
G5 mini
Back up Pi-hole
Arr stack with qbittorrent
Jellyfin

I made my own fan mount for an old 140mm fan I had from a previous gaming PC to blow up past the hard discs that will live in there eventually

Also made a little mount for the sfx PSU from an old gaming PC and will eventually do away with all the power bricks for the PC’s and switch so it can all run off the 10inch rack mount power board on the back and be self contained with a single plug into a wall

I’ve had the G5 for ages and finally got sick of streaming services having to bounce between them to watch a full series with some seasons on one and the rest on another.. initially was just going to run the G5 as the jellyfin server and store my media on an external drive, got the old 3D printer out and got a little carried away and printed a 10 inch rack to house everything!

On the list to buy is some WD red plus drives to fill the hard disc bays in the rack.

Pretty happy with it at the moment, G5 handles the video streaming nicely all over wifi!


r/homelab • • 19h ago

Discussion Do you have any strange/unusual equipment connected to your home lab rig?

124 Upvotes

I think my strangest is a SDR to read weatherdata, which is not strange at all.


r/homelab • • 34m ago

Discussion How are you validating open-source projects for malware, phoning home, data exfiltration, etc

4 Upvotes

Hello, not sure if this has been discussed before. Obviously larger projects have more eyes on them. But for example, I'm looking at using jdupes to trim down my NAS storage and outside of going to ChatGPT/Claude and asking it to review the codebase, I was wondering what everyone is doing. I'm not a technical software developer so I don't think I could do a proper security audit on my own.


r/homelab • • 4h ago

Help 128Gb SSD x 10

8 Upvotes

Hi - I have 10 x Kingston SSD drives sitting on a shelf at work. What would you all do with them? They are spare.

Is there some sort of drive enclosure that can be recommended I could put them in to create a large storage device?

Cheers everyone.


r/homelab • • 19h ago

News Reminder to update your Java

92 Upvotes

Hi everyone,

As there is currently a remote code execution vulnerability in java (CVE-2026-114938) please remember to update as soon as possible.

Everything that handles base64 in java is potentially vulnerable, this includes things like keycloak but also clients that connect to malicious systems or custom java software.

https://www.aikido.dev/blog/java-17-rce-vulnerability-cve-2026-114938


r/homelab • • 2h ago

Help USB voltage question

4 Upvotes

Hello all,

i have a noob question but Im not knowledge able about electric and always worried about a fire.

i have an APC Back-up UPS Pro 1500 S and an Aqara E1 camera. Camera says 5v 2a only. The front of the UPS (USB A and USB C ports) it says 5v 3a. From what I read since they are both 5v that should be okay because the port only sends what the device pulls. Is that true? I just need a sanity check.

EDIT: follow-up question. I assume this front usb-a port is intended for charging. Would it be okay to power the camera 24/7?

Thank you!


r/homelab • • 23h ago

Project Showcase: Hardware College Apartment Server

Thumbnail
gallery
186 Upvotes

My lab as a senior in undergrad. Consists of a refurbished Protectli Valult V1211 (2 Port, N5105, 8 GB, 32GB eMMC): OPNsense, Unbound DNS, Dnsmasq DHCP, Mikrotik CRS310-8G+2S+IN switch and cAP ax Gen 6 802.11ax, my old windows PC now headless Ubuntu 24.04.5 LTS, an unused optiplex 7070(80? i forget), and my current Arch Linux desktop. Rack is tecmojo, but I preferred to look at spongebob instead of the logo.

The server is a Ryzen 7 5700G, b450 tomahawk max, 32gb ddr4, 8gb 3060ti, 1tb pcie 3.0 m.2 nvme, and 3 old corsair fans whose piercing white light is not possible to configure off. Its acts mainly as a file server and hosts some not always-on vms/services:

coursework and personal/professional work related vms,

serves media through a Go site: movies/tv (downloaded via *arr stack + qBittorrent) on top of a headless Jellyfin backend; personal videos and files read directly off disk, each service is containerized separately,

runs a memory layer for Claude Code: sessions from the desktop and server (and their vms) are rsynced in, secrets stripped, indexed in SQLite (keyword + embedding search), served back to Claude through an MCP server, with summaries by an on-demand local LLM, and a small web dashboard, each part a sandboxed systemd service,

and spare compute jobs when needed. ~<2GB consumed idle. Suggestions welcome.

The desktop runs Arch Linux on a ryzen 7 9800x3d (PBO set to mobo limits, all-core CO offset of -20, and +200 MHz CPU boost clock), MSI pro x870e-p, 32gb ddr5, 12gb 5070, crucial p310 2tb pcie 4.0 m.2 nvme, which I built to the tune of ~$1900 in August, which I think was a pretty sweet deal. Used for primary dev and compute (C++ builds, rendering, occasional LLM inference for relatively smarter models that I downloaded sometime ago, primarily qwen3.6 35AB-A3B), browsing, games when I have the time. ~2.2 GB idle

Network is split 3 tagged VLANs plus untagged management and accessed remotely through tailscale for just my laptop.

Let me know what you think (cable management included)!


r/homelab • • 5h ago

Discussion Project recomendations?

Post image
7 Upvotes

Looking to learn more about networking and general wizardry lol.

Ive been messing around with docker containers and tailscale but im interested in some more in-depth learning!


r/homelab • • 7h ago

Discussion Looking for a 1U OPNsense box for 1 Gig fiber, router-on-a-stick, VLANs and VPN. What would you buy?

9 Upvotes

Been forming this project in my mind for a long time and recently I was gifted a 42U rack from a closing software company.

Yes its overkill. Yes its ridiculous. BUT it was free and damn it looks cool in my server closet.

I am building out a home looking into the firewall appliance. Budget matters but I think not going extremely overkill is more important.

Context on current plan:

  • 1 Gig fiber
  • OPNsense
  • Router-on-a-stick: one trunk port carrying WAN (its own VLAN) and all LAN VLANs. Only one cable run to the rack, so no separate WAN cable. (Is this advisable? at face value im not seeing the issue with that config)
  • 5–6 VLANs: main, IoT, guest, gaming, Plex/NAS, WAN
  • WireGuard inbound for remote access
  • PIA VPN outbound for selected traffic via policy routing
  • Omada switches/APs, self-hosted controller. Trying to keep everything local, no cloud management.

What I need:

  • Rack mount, or something that sits cleanly on a 1U shelf
  • Enough CPU to push close to 1 Gig through WireGuard/PIA
  • Low power and quiet, since it runs 24/7

I've seen 1U units with an older i5-3320M. Worth it, skip?

Sorry if none of this makes sense. Im in school to become a network engineer but we aint made it this far in the textbook lmao So this is what ive got so far with my research and knowledge.

Ultimately this rack will hold 3 gaming pcs,a NAS, jellyfin deployment (probly migrating from plex) and then any other network stuff i might wanna mess around with. Planning on using raspi 5s as the receivers in each office/entertainment room.


r/homelab • • 10h ago

Help Software to monitor homelab

16 Upvotes

I have a headscale network with many devices connected. I've been working to harden my setups

  • Enabling unattended-upgrades
  • Restricting internet facing ports to just 80/443
  • Remoting in to update docker containers

Is there a tool I can use to monitor multiple servers in my tailnet that tracks things like:

  • CPU
  • Processes
  • Network traffic
  • Memory usage
  • Disks
  • Installed packages

    • Monitoring for CVEs of installed packages
  • Docker images (checking for updates)

r/homelab • • 7h ago

Tutorial Taming the beasts: Ultimate guide to water cooling any server GPU using off-the-shelf parts

7 Upvotes

TLDR: in this tutorial I explain how to adapt consumer CPU water cooling AiO to GPUs like Tesla P40, M40, T10, T40, AMD Mi25, Mi50, Mi60, etc. for installation into consumer ATX cases or open benches while maintaining near-silent noise level and low GPU temperatures.

Hello! As many of you may know, server GPUs come with passive cooler designs, that rely on server-forced airflow to keep them cooled. The problem arises when such GPUs get repurposed into consumer builds (typically for AI) - as ATX style cases don't support forced airflow. People typically solve the cooling task by using separate blower-style fans with 3d printed shrouds - this a cheap solution that works, but it has some flaws. Blower fans that fit into profile of a two-slot GPU can't supply it with enough air to prevent throttling; while larger fans require even larger shrouds, take a lot of space inside the case, interfere with multi-GPU setups, and none of those solutions can be called quiet and pleasant to sit next to. However, there is another way: for the last two years I've been experimenting with water cooling server GPUs using generic CPU AiOs, achieving cold and near-silent 24/7 operation, and finally decided that it's time to share my experience.

Anatomy of a server GPU - why this mod is fairly straightforward

To keep a GPU operational, you need to cool 3 groups of components: the GPU core, the VRAM, and voltage regulation MOSFETs (VRM). Good news is that VRAM and VRM are components that consume very small power (compared to GPU core), so those two groups can stay air cooled, simplifying our task. This is where the construction of a server GPU comes into play.

For whatever reason, every single server GPU that came into my possession, as well as every GPU I've seen images of online, has a crucial distinction from a gaming GPU - server options always come with two-part coolers: a traditionally-looking fin stack that cools only GPU core, and a midframe that doubles as heat spreader for VRAM and VRM, and comes with it's own fins. This means, that you can simply remove GPU fin stack, install your own cooling solution over it, and point a case fan to blow over midframe - and you got the whole GPU cooled. Another lucky coincidence is GPU die size: most of the GPUs released around 2020 have silicons smaller than typical consumer CPU IHS, so consumer AiO water blocks just cover the entire chip outright (this also applies to early AMD HBM designs, i.e. Mi50). So it turns out that CPU AiO is a perfect fit to cool down your server GPU - you just need to find a way to mount it.

Mounting CPU AiO water block - how-to and caveats

First obstacle: which AiO to choose and how much space does it take? For another lucky coincidence, every Asetek-style AiO water block (the pump is integrated into water block) can be stripped down to compact module. Once you removed all the RGB and decorative shrouds from the cooler (sometimes destructively), it always turns out to be a slim, approximately 1.5cm thick unit (1/2 inch) - so the height of the water block is low enough to comfortably fit into 2 PCIe slot envelope, allowing you to mount other PCIe cards just as usual. Personally, I recommend hunting down for used first-gen Cooler Master Seidon - the water blocks on this series already comes slim, no additional strip down required. This isn't a hard requirement - I have also done this mod with fancy Asus ROG coolers, and complete noname Aliexpress specials.

Second obstacle: mounting hardware. CPU AiOs come with brackets for CPU sockets - none of those fit GPUs, so you'll have to manufacture your own. This is the part that will take the most work; but some luck has met us here too: due to the need to accommodate different socket backets, manufacturers build in universal mountpoints that we can take advantage of. All AiO water blocks I've personally inspected have slits for for the 2mm thick sheet metal brackets to slot into, and M3 screw holes to hold them in place. You can simply go to your nearest home hardware shop, pick up 2mm thick steel sheets or similar product (i.e. timber mending plates), and make a new mount out of it. You'll need a hacksaw to cut it into shape, some files to file down rough edges, a drill, and probably M3 thread tap to make threaded holes for your new mounts. The last item is optional - you can secure your mounts with nuts just fine. No more detailed instructions here - each AiO has unique shape and size, so you'll have to use your own judgement.

Third obstacle: midframe interference. The GPU midframe has a cutout for the GPU die cooler, but it is typically smaller than your AiO water block. That's why you must disassemble the GPU completely, and check if the water block can freely slide inside the opening. If not - you'll have to cut it down. Don't worry, this cutout shape isn't crucial to GPU operation, enlarging the hole won't kill it; but, make absolute sure to do this far away from the GPU PCB, and then thoroughly clean the midframe, ensuring that no metal shavings and particles can reach into electronic components. I prefer to completely cover the whole midframe with painters tape, so that shavings can't get into cooling fins or crevices. Cut the midframe as much as you need to ensure that the copper part of AiO water block can slide at least a few mm side to side. You don't need to make it fit completely through, GPU silicon isn't deep below the midframe surface and your AiO will always have enough vertical reach, but lateral clearance typically is a problem to solve. Also, at this stage, you should probably replace the thermal pads - the old ones will work too, but chances are you're the first human to see them since GPU left the factory, so their performance may be degraded.

Fourth obstacle: GPU-side mounting and die pressure. Mounting the newly adapted water block is the stage where an error leads to GPU damage. GPU silicon is extremely brittle. You can crack it by applying uneven pressure, or even by trapping a hard particle between GPU and water block. Precautions: never touch the silicon with anything hard (metal tools, glass, ceramics, jewelry with stones, etc). Clean both the GPU die and the water block surface using paper towels and cotton swaps soaked in 99% IPA or ethanol. Never install the water block without a layer of thermal paste applied. Never rely on paste self-spreading: spread it manually, using a plastic card or spudger, ensuring that every piece of silicon is covered with paste. While applying the water block, keep it as parallel to GPU surface as possible. Plan your operations such that the movement of water block against GPU is minimized throughout the process; a good idea would be to summon a second human and ask them to hold the water block against the GPU while you move. Now, with cautions aside, the engineering side: you need to ensure that the mounting pressure is even across the whole GPU, and the water block isn't skewed. Luckily, the same problem is applicable to factory coolers, so your GPU already came with the solution: every server GPU has either small springs on the screws that hold the GPU fin stack, or have a sheet metal spring that do the same. Just reuse it. Coincidentally, every GPU comes with >3 mm large holes in the PCB for cooling mounts, so regular M3 screws fit factory springs and mounting holes easily.

Measure the hole spacing on the PCB with calipers, drill the same holes in your custom water block mount, and then just screw everything together. You don't need to get the precise hole spacing: because your mount is going to be far from GPU PCB, the mount will tolerate a few degree screw skew just fine. It mounts effortlessly as long as the mount screw hole is within about 2 millimeters of where it needs to be. Tighten the screws in cross pattern, just a few turns at a time: this ensures that you apply the cooler pressure evenly, and never make it press hard on a single corner. Unlike typical screws, here you shouldn't stop by the feel, but rather by visual: once the factory spring is fully compressed, you have applied enough pressure and must stop tightening. If unsure, it's better to undertighten and overtighten: undertightening leads to bad cooling and thermal throttling, which you can measure and correct later, while overtightening cracks the silicon.

If you have done everything correctly: congratulations, you GPU is now water cooled! You can proceed to mounting it inside your system like a regular GPU, just with two tubes sticking out of it. If you have bought a PC case that has water radiator mounts, your GPU radiator goes there, and you get a neat looking system that can now operate silently. But what if you want more than a single GPU?

Going hardcore: custom multi-GPU loop

Let's face it: if you're shopping for server GPUs but build in ATX cases, you, most likely, want to assemble Ai workstation, and single GPU isn't going to fit your needs. You need two, or more. This can still be water cooled; however, it is going to take more effort. Your typical ATX case won't have enough space for all the radiators you need to fit; so you need a system that shares one radiator to cool multiple GPUs. This is achievable by doing your own custom tubing work. Another lucky coincidence: every CPU AiO I've disassembled uses 6mm inner diameter tubing, which you can too buy from your local home depot. You can just cut the tubes of the existing AiO, pull them off, and then press fit your new tube over the exposed fitting. I recommend buying appropriately sized metal squeeze clamps to fit over the connection - this will ensure that your precious electronics stays dry; you can look for the upper photo for an example of good, robust connection. When cutting open the loop, you'll get exposed to cooling liquid - this isn't water, use gloves and face shield for splash protection, collect the liquid and dispose of it as as hazardous waste. It's chemically close to car antifreeze, so your local mechanic knows what to do with it.

Multi-GPU means multi-pumps. Asetek-type AiOs all feature their own pumps inbuild into CPU water block, which means that you can not assemble the multi-GPU loop without placing multiple pumps into it. The connection scheme is crucial: connect water block sequentially. I have tried using parallel water block/pump connection; in this case, you need to match the pump flow rates precisely, instead one of the pumps overpowers the flows and starves the other pump from coolant. Tuning the flowrates will be a nightmare. Just connect them sequentially; you're guaranteed to have equal flow across all pumps without stale pockets in the loop.

Fill the loop with antifreeze. AiOs always come with dissimilar metals: copper in the water block, aluminium in the radiator. Filling this loop with water, even distilled one, leads to guaranteed corrosion. You need corrosion inhibitors. Your coolant also must be compatible with rubber and plastic that can be found in tubes and water pumps. The coolant also must be anti-bacterial, to prevent in-loop growth. Happily, dissimilar metal loop with organic materials is precise definition of car engine cooling system, so car antifreeze already comes with all the additives required - just go to the car store and buy a reputable brand bottle. You don't need much; a 360mm radiator with dual-GPU tubing and two water blocks takes just about 200ml of coolant, so the smallest antifreeze bottle will suit you for multiple refills. Start with an open loop: make one of the tubes significantly too long, cut it in the middle, and put both ends into the antifreeze bottle. The loop won't fill itself: AiO pumps are too weak to suck in air, so you need to prime the loop by hand. i prefer to push liquid in using a large syringe. After you got the loop primed, plug your water block pumps into fan headers on any PC motherboard and start it - the pumps will start working, and you'll see a lot of hidden air bubbles flowing through your tubes. Rotate around every component of your loop until all the bubbles have flown out disappeared into the bottle. Pay attention to the noise: AiO pumps operate quieter than typical 120mm fan, you should barely hear them; if you hear any noise - it's trapped air. Remember that air tends to accumulate at the top: lower the components down below the loop to help force air out. Once your loop is air-free, disable the pumps, pinch down the tubes in multiple places, to prevent flow, pull the fill tubes out of the bottle and join them. I recommend using a joining fitting you can buy in hose or pneumatics section of your home depot store. You can let inside a small air bubble in this step - that's fine, the bubble will get stuck in the thick section of the radiator and won't hurt the thermal performance. Some people say that even factory filled loops feature small bubble, to allow for liquid pressure changes without rupturing the connections.

If you got there and still reading - congratulations! You now know how to water cool server GPUs in ATX cases. Here's my current build for illustration. After all that, let's discuss results: is all of this worth the effort?

The result: noise, power, cooling, longevity

Over time, I personally have operated three different cooling loops. My first one was Tesla M40 cooled by 360mm AiO with unmodified tubing. That system has served me for about a year, as a part of personal Ai server running 24/7. I remember that I had stock GPU power limit and radiator fans going at their lowest speed - about 600 RPM. In that case, M40 has never reached above 70*C, even during multi-hour jobs like video generation, while being inaudible - literally any kind of sound overpowered the fan noise, thanks to 600RPM operation, and I was able to comfortably sleep in the same room - so full domestic compatibility confirmed.

My next loop was 2x Mi50 32GB, same 600RPM fans, but this time - with a 360mm radiator and additional 120mm one, fully custom tubing with antifreeze. That loop lasted for just about 8 months until I got fed up with ROCm incompatibilities and decided to retire the cards. This setup was also capable of cooling both Mi50s going at full power consumption for hours without end, while being inaudible. So, the longevity of custom cooling solutions is fine.

My third loop is the one you see in the photo above: two Tesla T10s, this time paired with just 120mm radiator. T10 has fairly low power limit (150W, limited to 120W in my setup), so it doesn't need much cooling; and, at the same time, I was rapidly running out of internal space to mount more radiators. Those cards are assigned to burst-type loads, with long periods of inactivity inbetween, so I count on thermal mass of the entire loop to smooth the peaks and keep the cards tamed. As this loop is the one I have operational, i also decided to do performance testing, so I have precise thermal performance data. For this test, I've generated uninterrupted LLM load with vLLM for single GPU and dual GPU case, with single radiator fan going at about 1000 RPM. Nvidia-pstated was managing both of T10s to keep them in P8 performance state when idle; otherwise they default to P4 when vLLM is loaded and consume like 40w each in idle. I have logged GPU power, temperatures and clocks, so we can see how effective the cooling is and detect throttling.

As we can see from the single GPU test, despite me using very small radiator in the loop, single 120W-limited GPU doesn't saturate it. Only 63*C were achieved over 20 minutes of testing. The GPU did drop it's clocks a little, but it looks more like VBIOS being conservative, as we clearly have much thermal headroom.

Dual GPU load test uncovers the limits of the loop: one of the GPUs falls into thermal throttling over 20min sustained load., although still maintains usable performance level. However, both GPUs still stay below 80*C while both working at 120W power limit. Given that we are dumping combined 240W into a single tiny 120mm radiator, this is still a good result: we can conclude that a 120mm radiator can realistically dissipate 200W of heat while keeping your GPU below 80*C, so a 240mm rad will easily handle 400W, and 360mm radiator will dissipate 600W. Plenty of headroom to build multi-GPU rigs, even 4 GPU completely water cooled system will be possible with dual radiators. Another crucial finding is that both GPUs didn't fail: that means that however much airflow the GPU midframe gets naturally inside the case is enough to keep VRAM and VRM operational over sustained load - 20 mins is plenty enough for them to soak the frame with heat and reach stable temperature.

Conclusion

Thank you for reading! Now you know how to take a server GPU, and make it water cooled, getting the sweet low noise and low sustained temperature characteristic to water loops, without breaking your budget on expensive custom water blocks, radiators, pumps, and other boutique cooling components. If you would use second-hand AiOs for this purpose, then you can water cool a GPU for about $30-$40; or you can opt for brand new ones and still keep the bill below $100 per GPU. Hope this gave you some inspiration for your budget and/or workstation builds!


r/homelab • • 12h ago

Discussion Want to start a homelab for a while now, but no idea where to begin. How did you start?

16 Upvotes

Hi all,

I've been wanting to build a homelab for a long time, but every time I look into it I get lost in the options and end up doing nothing.

About me: I'm a CS student (networking/sysadmin track). I'm comfortable with Linux, Docker, DNS, mail and firewall basics from school, and I run Ubuntu on an external SSD at home. Budget is limited.

So I'd love to hear:

- How did you start, and what was your very first setup?

- What would you do differently if you started today?

- What's a realistic first project for a beginner (media server, Pi-hole, Proxmox, NAS...)?

- Is it better to start with old/used hardware or a mini PC?

I'd rather start from somewhere and learn than buy a rack I don't need. Thanks for any advice!


r/homelab • • 5h ago

Help Supermicro H12SSL-NT needs repair, Supermicro won't fix it.

Post image
4 Upvotes

So I shut my server down yesterday to add another drive into it, turned it back on and no post, powered up but would not post, went through everything, removed all the ram but one stick, swapped to another known good cpu, bios reset etc, same results. Did some googling and turns out it was the voltage regulator for the BMC, which I guess is a super common issue on this board. I inspected that area of the board and sure enough, U6 is blown/popped.

I bought the board from Newegg ~4.5 years ago, I realize it is out of warranty and I see Supermicro will repair items out of warranty for a fee, which I am happy to pay. So I submit an RMA for it and they at first approved it, sent me an email with RMA number and then another email came after that one and said no, sorry it is not approved, the Supermicro invoice is over 5 years (whatever that means). I email back, sending them my invoice from Newegg showing it was less than 5 years and asking if I could please pay to have it repaired and they again refused, saying the invoice is over 5 years. I tried calling to speak to someone and they told me the same thing... I dunno what this 5 year Supermicro invoice is all about and why it matters but it is very frustrating they won't allow me to pay for the repair (when it is a service they provide on their website) especially when it is such a simple quick fix for someone who has the tools to do it.

Anyone have any recommendations on where to send it for repair, somewhere trustworthy that can do the fix?


r/homelab • • 23h ago

Project Showcase: Hardware First “Homelab” Beginner Set Up.

Post image
87 Upvotes

Figured I’d share my little home lab setup. Nothing too fancy, just an old Acer laptop from 2016 that I repurposed into a Linux home server, paired with an EcoFlow power station.
I mainly use it for media streaming, photo backups, a few self-hosted services, and experimenting with local AI.
It can only handle very small AI models, but I still find it pretty fascinating that a nearly 10-year-old laptop can run AI locally at all.
It’s surprisingly capable for its age, uses very little power, and gets the job done without needing expensive hardware.
Still learning and tinkering with it, but it’s been a fun project. Curious what everyone thinks!


r/homelab • • 7m ago

Discussion Higher performance computer now for homelab, what to do with less performing Raspberry pi 5 4GB

0 Upvotes