<?xml version="1.0"?>
<rss version="2.0"><channel><title>The Server Room</title><link>https://mopar1973man.com/blogs/blog/26-the-server-room/</link><description><![CDATA[<p>Where I keep the computers running and the bad guys out. Home servers, networking and security, explained in plain English.</p>]]></description><language>en</language><item><title>Garage Extension Built! Track all your vehicle fuel needs, budgets and maintenance logs!</title><link>https://mopar1973man.com/blogs/entry/133-garage-extension-built-track-all-your-vehicle-fuel-needs-budgets-and-maintenance-logs/</link><description><![CDATA[<h1>Building a Garage for the Forum</h1><p>Nov 14, 2026 · @Titanium</p><h2>Why the forum needed a garage</h2><p>I've been wrenching since I was 14, and for 23 years I did it for a living. In all that time the best maintenance record I ever kept was a greasy notebook in the truck, and half the time it was the wrong notebook. So I built the Garage: a vehicle log that lives right inside the forum, where the rest of the community already is.</p><p>Every member gets a place for their trucks, tractors and trailers. Log the oil change, the fuel fill, the part you swapped, and the forum remembers what's due next.</p><h2>What it does today</h2><p>The Garage already covers the everyday jobs of keeping a rig alive:</p><ul><li><p><strong>Vehicles:</strong> year, make, model, axle and ratio, tire size, and a photo gallery for each one.</p></li><li><p><strong>Maintenance records:</strong> what was done, when, at what mileage, and what it cost.</p></li><li><p><strong>Reminders:</strong> service schedules that tell you what's coming due.</p></li><li><p><strong>Fuel log:</strong> every fill-up, so you can see real mileage instead of guessing.</p></li><li><p><strong>Modifications:</strong> a running list of what you've bolted on.</p></li><li><p><strong>Trailers:</strong> hitch and unhitch a trailer, and the miles you tow are tracked for you.</p></li></ul><p>It works on a phone, since that's where most of us are standing when we need it.</p><h2>Multiple garages and family sharing</h2><p>One garage wasn't enough. Think of a fire station with several bays: you can set up more than one garage and sort your vehicles into them. Admins set how many each member gets.</p><p>Sharing is set per garage. You pick who gets in and at what level:</p><ul><li><p><strong>Full:</strong> add, edit and delete.</p></li><li><p><strong>Add-only:</strong> log new work but not change what's there.</p></li><li><p><strong>View-only:</strong> look, don't touch.</p></li></ul><p>Only the owner can delete vehicles or change who has access, so a spouse or a kid can log the fuel without being able to wipe the records.</p><h2>Lock-out tag-out and cost of operation</h2><p>Two features come straight from the shop floor. The first is lock-out tag-out: mark a vehicle "DO NOT DRIVE" when it's broken or unsafe, and the only way to clear it is to log the repair. No quietly flipping a switch and hoping.</p><p>The second is cost of operation. The Garage adds up your fuel, maintenance and parts by week, month and year, then works out cost per mile and cost per hour. Truck and trailer combos are figured together, so you see what it really costs to haul that load.</p><h2>How it was built</h2><p>The Garage is a standalone add-on for Invision Community, the software this forum runs on. I developed it on a private test install first, then built it as an installable package and uploaded it to the live site.</p><p>That last step taught me a lesson. An uploaded package brings new code but doesn't change the database, so my first live update broke the garage page until I fixed the missing tables by hand. The next release will carry its own upgrade step, so updates apply cleanly. Every release gets a backup first.</p><h2>What's next, and testers wanted</h2><p>Still coming: photo limits and storage quotas by member group, archiving instead of deleting (with restore), reminder notifications, and a mobile polish pass.</p><p>I need testers. Open My Garage, add a rig, log some work, try sharing a garage with a family member, and tell me what breaks or what's missing. Post your feedback in the forum and I'll work through it.</p><p></p><p><img class="ipsImage ipsRichText__align--block" data-fileid="30997" src="https://mopar1973man.com/storage/attachments/monthly_2026_11/image.png.f48f7a8d5f9410fd172890b1f324d263.png" alt="image.png" title="" loading="lazy"></p>]]></description><guid isPermaLink="false">133</guid><pubDate>Sun, 15 Nov 2026 02:23:25 +0000</pubDate></item><item><title>Members Now Have a Garage for Their Vehicles</title><link>https://mopar1973man.com/blogs/entry/132-members-now-have-a-garage-for-their-vehicles/</link><description><![CDATA[<h1>Members Now Have a Garage for Their Vehicles</h1><p>Nov 13, 2026 · @Titanium</p><p>My 2002 Dodge Ram 2500 SLT, Beast, just rolled past 506,000 miles, and I can tell you exactly when she last got oil, what it cost, and how many miles are left before the next change. That's not memory. That's the Garage I just built for the forum.</p><p>Anybody who's run a high-mileage Cummins knows the problem. You change the oil, scribble it on a shop rag or a scrap of cardboard, and six months later you're standing in the driveway asking yourself if that was 4,000 miles ago or 7,000. Multiply that by fuel filters, coolant, transmission fluid, transfer case, front end and every bolt-on you've ever added, and the paper trail falls apart fast.</p><h2>Why a garage on the forum</h2><p>I've been wrenching since I was 14 and spent 23 years as a field mechanic, so I've seen what a good service history is worth. A truck with records sells faster, diagnoses easier and gets looked after better. The trouble is that spreadsheets get lost, apps want a monthly fee, and none of them know a thing about a diesel guy's life.</p><p>So I built it right here. Every member gets their own private garage. Add your trucks, tractors, quads and whatever else lives in the shop, and keep the whole history in one place. Your garage is yours: other members don't see your rigs unless I add sharing later.</p><p>And it goes where you go. The whole Garage works from your phone, so you can log the oil change from under the truck, punch in a fill-up at the pump, or snap a photo of a new mod in the driveway. Every vehicle you own is tracked in one place, with its maintenance and what it costs to run: service bills, fuel and mods, all on the record.</p><h2>The maintenance log</h2><p>Every job gets a line: miles, date, service and cost, laid out in a clean table like a shop invoice. Beast's latest reads 506,000 miles, 11/13/26, Oil Change, $70.00. Each row has Edit and Delete buttons, so fixing a typo takes seconds.</p><p>Add as many entries as you like. When you ask "when did I do the fuel filter?", the answer is one glance away instead of one afternoon of digging.</p><h2>Reminders you control</h2><p>The Garage doesn't guess your schedule. You set it. For each service you pick the interval: every so many miles, every so many days, or whichever comes first. Kilometers and engine hours work too, so the tractor and the generator get tracked the same way as the truck.</p><p>The reminders page is a table with Status, Service, Days, Miles and Last, so you can see what's coming at a glance. Right now Beast's oil change shows OK with 6,900 miles and 180 days to go. When a service gets close, it flips to soon. When it's due or past, it flips to overdue.</p><p>To keep the numbers honest, the Garage asks for your mileage once a day. Type the odometer reading and hit Enter, or hit Skip if you haven't driven. It takes about five seconds, and every reminder stays accurate.</p><h2>The fuel log: real mileage, not wishful thinking</h2><p>Every truck guy has a number in his head for his mpg, and it's usually generous. The fuel log shows the real one. Log each fill-up with the odometer, the gallons, the date and what you paid, and mark it as a full fill or a partial.</p><p>The best part: you never write a thing down. Standing at the pump, you pull out your phone, open the Garage and punch in your odometer, gallons and price. It's saved to your account on the website, so there's no receipt to lose, no notebook to dig out of the glovebox and no spreadsheet to fill in later.</p><p>It displays like the pump does: price per gallon as $x.xxx and gallons as x.xxx. The economy figure is worked out between full tanks. It counts the distance since your last full fill and all the fuel you added since, partials included, so a splash-and-go doesn't skew the result.</p><p>Towing season versus empty-bed commuting, tire swap, a new tune, a different fuel: now you can actually see what each one did to your mileage.</p><h2>The show page: let the truck show off</h2><p>Every vehicle gets its own page, and this is where Beast gets to strut. A big main photo leads the page, scaled so the whole truck shows, with a gallery of extra shots underneath. Click any picture to open it full size. Pick which photo is the main one with a single click.</p><p>Below the photos come the specs: engine and displacement, transmission, transfer case and drivetrain, current mileage, and a notes box for the extras like axles, tires, fuel type and color. Write down the details that actually matter to the next owner, or to the guy asking you about it at the fuel pump.</p><p>Then the part I'm proudest of: <strong>the mods</strong>. Every modification gets its own page with photos and its own write-up: brand, category, install date, mileage at install and what you paid. On the vehicle page they show up as links, so the turbo, the lift pump, the exhaust or the lift kit each tells its own story. Your most recent maintenance and fuel entries are pulled onto the same page, so it reads like a build sheet that's still being written.</p><h2>What's next, and I want your input</h2><p>The Garage is built and being tested now, and it's coming to the forum soon. A few things are on my list:</p><ul><li><p>A switch to make a vehicle's show page public, so you can brag about your build or link it in a classifieds post</p></li><li><p>Better reminder warnings, with a lead time you choose for each service</p></li><li><p>Email or notification nudges when something's coming due</p></li><li><p>Starter service lists for common diesel jobs, so you don't have to type them all in</p></li></ul><p>Tell me what a garage like this needs to be worth using. What do you track now? What's the one service you always forget? Drop it in the comments and the best ideas go on the list.</p>
<p><img class="ipsImage ipsImage_thumbnailed ipsRichText__align--block" data-fileid="30995" data-full-image="https://mopar1973man.com/storage/attachments/monthly_2026_11/ScreenshotFrom2026-11-1321-40-54.png.ae3a02393964dc8141e97c6b4a429ba3.png" src="https://mopar1973man.com/storage/attachments/monthly_2026_11/ScreenshotFrom2026-11-1321-40-54.png.ae3a02393964dc8141e97c6b4a429ba3.png" height="900" width="1600" alt="Screenshot From 2026-11-13 21-40-54.png" loading='lazy'></p>
<p><img class="ipsImage ipsImage_thumbnailed ipsRichText__align--block" data-fileid="30996" data-full-image="https://mopar1973man.com/storage/attachments/monthly_2026_11/ScreenshotFrom2026-11-1321-40-00.png.b88820d6f495b0d5d7882635b8bf9bf6.png" src="https://mopar1973man.com/storage/attachments/monthly_2026_11/ScreenshotFrom2026-11-1321-40-00.png.b88820d6f495b0d5d7882635b8bf9bf6.png" height="900" width="1600" alt="Screenshot From 2026-11-13 21-40-00.png" loading='lazy'></p>]]></description><guid isPermaLink="false">132</guid><pubDate>Sat, 14 Nov 2026 04:49:16 +0000</pubDate></item><item><title>Checking My Own Work: What I Found When I Audited My Three PCs</title><link>https://mopar1973man.com/blogs/entry/130-checking-my-own-work-what-i-found-when-i-audited-my-three-pcs/</link><description><![CDATA[<h2>The short version</h2><p>I built three computers the same way, and I made the same mistake on all three: both memory sticks went into the same memory channel. The computers worked fine. They were also running their memory at 3600 MT/s instead of 4800, and with half the memory bandwidth on paper. I found it while tuning one of them, fixed two in a single evening, and the third is next on the list. This post covers the mistake, how to check yours in two minutes, and a few other things I cleaned up along the way.</p><h2>What I did wrong</h2><p>All three computers use the same motherboard, an ASUS ROG STRIX X870-A GAMING WIFI, with a Ryzen 5 7600X processor. The board has four memory slots but only two memory channels. The slots are labeled A1, A2, B1 and B2, and when you install two sticks, the board wants them in A2 and B2, one per channel. I put both sticks in the same channel. That limits the system to single-channel memory, and with two sticks sharing one channel, the board also holds the memory speed down at 3600 MT/s.</p><p>How it happened: the paper that came in the box was thin and its slot diagram was hard to follow. I read it wrong, and then I repeated my own mistake on the other two machines because I built them all the same way.</p><h2>The fix</h2><p>Moving one stick to A2 and the other to B2 took a few minutes per machine and a screwdriver. My first boot after the swap looked dead for a bit, with a black screen and an amber warning light, before it came up.</p><p>Afterward, the memory report on both fixed machines shows one stick in channel A and one in channel B, both running at 4800 MT/s. That is a third faster in speed, and now it is dual-channel.</p><p>Did it make the computer feel faster? I tried to measure it, but my benchmark results were too noisy to prove a difference on small jobs. I trust the memory report more than the benchmark numbers, and I would rather tell you that than make up a percentage.</p><p>The better test turned out to be a game I play, Rust. On both fixed desktops it now runs at roughly 80 to 110 frames per second at medium detail. I did not record a before number, so I cannot tell you how much of that came from the memory change. But it is a real-world result, which counts for more than a synthetic benchmark.</p><h2>How to check yours in two minutes</h2><p>On Linux, run this in a terminal:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>sudo dmidecode -t memory | grep -E "^\sSize:|Bank Locator:|Configured Memory Speed:"</code></pre><p>Each slot prints three lines: its size, its channel, and its configured speed. Look at the slots that show a real size. If one is on CHANNEL A and the other on CHANNEL B, you are in dual-channel. If both are on the same channel, you are in single-channel, like I was. On Windows, the free CPU-Z program shows the same thing on its Memory tab, on the line that says Channels.</p><p>Before you move anything, read the slot labels printed on the board next to the sockets. Those are more reliable than the paper in the box.</p><h2>Cleaning up a drive that was almost full</h2><p>One of my computers runs around the clock and stores my nightly backups. When I checked it, the backup drive was nearly full, and so was the system drive.</p><p><strong>The backups.</strong> Each nightly backup is a full copy of about 650 GB. The job that made them kept every copy until it was more than a week old, and it wrote the new copy first and only then deleted the old ones. That meant the drive needed room for eight or nine copies at once. When a night ran out of room, the job left a half-written file of roughly 600 GB behind, and that leftover ate even more space. I checked that nothing was using the leftovers and deleted them, tested the newest good backup, and removed the three oldest copies.</p><p>The permanent fix is one added line in the backup script. Before it writes tonight's copy, it deletes everything except the newest three. I also cut the age limit from seven days to three as a second safety net. The next morning the drive held four copies, 2.6 TB, with 3.9 TB free of its 7 TB limit instead of about 1 TB.</p><p><strong>The system drive.</strong> The main drive was 72% full, and most of it was my own home folder. The biggest single item was a 25 GB folder I had already marked "hold to delete." I did not delete it. I copied it to another computer, ran a checksum comparison to prove every file matched, and only then removed the original. The drive dropped from 72% to 46% full.</p><p>I also ran the delete command on the wrong computer first. The folder did not exist there, so nothing was lost, but it is a good reason to read the prompt before you press Enter on anything that deletes.</p><h2>Making my status panel tell the truth</h2><p>I keep a small status panel on my desktop for each computer (I use Conky on Linux), showing CPU, memory, drives, and more. After the memory fix, it still showed 3600 MT/s. The reason is that Conky cannot read the hardware report without administrator rights, so my script was reading a saved copy of that report from weeks earlier. A saved copy never updates.</p><p>The fix has two parts. A small script, run by the system at every boot, writes a fresh hardware report to a temporary file that any user can read. The panel script now reads that file instead of the old copy, so the memory block shows each stick's real speed.</p><p>Then I added a backup block to the panel for the computer that holds the backups:</p><ul><li><p><strong>Status:</strong> OK in green when the newest backup is under 30 hours old, LATE in yellow up to 54 hours, and STALE in red after that.</p></li><li><p><strong>Details:</strong> when the last backup ran, and how many copies are kept.</p></li><li><p><strong>Stuck files:</strong> a line that says a backup is being written (normal while it runs) or warns when a half-written file has sat for 8 hours or more. That is the failure I missed before.</p></li></ul><p>I made the same changes on a second computer, since its panel works the same way.</p><h2>Chasing a network card that kept dropping</h2><p>Earlier this fall, the network card on two of my computers dropped out and stopped seeing the cable, a day apart. They are the same build, so I suspected the same cause. The chip is an Intel I226-V. People report on Linux mailing lists and forums that it can disappear ("PCIe link lost, device now detached") when a power-saving feature called ASPM is on. The usual fixes are a BIOS update, or turning ASPM off in the BIOS or with a kernel option.</p><p>I am not changing any of that yet, because I do not have evidence that it is my problem. When I went looking, the system logs on my desktop only went back to the last reboot, so anything from October was already gone. The first fix is to make the system keep its logs across reboots, so the next drop leaves a record. Then I wait for the next drop, search the log for "link lost," and only change the power-saving settings if the log points to them. One change at a time, with proof, beats changing five settings and never knowing which one helped.</p><p>While I had the BIOS open, I also noticed two settings that matter on a computer that runs unattended: one that stops the boot and waits for a keypress after an error, and one that decides whether the machine turns itself back on after a power outage. I plan to look at both when I do the memory swap on the computer that runs around the clock.</p><h2>What I would tell anyone building a PC</h2><ul><li><p>Read the slot labels on the board itself, not just the paper in the box.</p></li><li><p>After you build, check that your memory is dual-channel and running at its rated speed. A computer that boots is not the same as a computer that is set up right.</p></li><li><p>Anything that runs on a schedule needs a limit, so it cannot fill a drive.</p></li><li><p>If you trust a number on a screen, make sure it is reading fresh data.</p></li></ul><p>I spent years building custom PCs at Cloud 10 Computers, and I still made this mistake three times. That is the best argument I know for checking your work. If you have a computer or network question, or want help checking your own build, ask in the comments or on the site.</p>]]></description><guid isPermaLink="false">130</guid><pubDate>Thu, 12 Nov 2026 18:02:36 +0000</pubDate></item><item><title>One Reminder, One Long Day: Forum Upgrade, File Cleanup, and a Network Card That Vanished</title><link>https://mopar1973man.com/blogs/entry/129-one-reminder-one-long-day-forum-upgrade-file-cleanup-and-a-network-card-that-vanished/</link><description><![CDATA[<h2>One Reminder, One Long Day: Forum Upgrade, File Cleanup, and a Network Card That Vanished</h2><p>It started with a simple reminder: the forum software needed updating. It turned into a full day of server housekeeping. Here's what I ran into and the commands I used. <strong>Anything in ALL CAPS is a placeholder, so swap in your own values.</strong> Back up before you change anything.</p><h3>1. The upgrade that always failed</h3><p>The one-click Invision upgrade never worked for me, so I'd been uploading updates by hand. The cause was file ownership. Years of unpacking files as the administrator left hundreds of them owned by the wrong user, and the site runs as a normal account that couldn't overwrite them. Check for it:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>ls -ld /PATH/TO/FORUM

find /PATH/TO/FORUM ! -user YOUR_SITE_USER | wc -l</code></pre><p>If that count isn't 0, fix the ownership and look for world-writable (777) folders:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>sudo chown -R YOUR_SITE_USER:YOUR_SITE_USER /PATH/TO/FORUM

find /PATH/TO/FORUM -type d -perm -0002 | head

find /PATH/TO/FORUM -type d -perm -0002 -exec chmod 755 {} \;</code></pre><p>After that, the one-click upgrade ran clean. Test a photo upload afterward.</p><p><em>Lesson: when an auto-updater fails, check file ownership before blaming the firewall.</em></p><h3>2. Cleaning personal files off the server</h3><p>Photos, music, and documents had piled up where they didn't belong. Before deleting anything I made sure it was all safely on the desktop. First, check that no sync program (like Syncthing) is set up on the server, because deleting synced files can delete them everywhere:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>sudo find /home -maxdepth 5 -name config.xml -path '*syncthing*'

sudo grep -hE '&lt;folder |&lt;device id' /PATH/TO/config.xml | cut -c1-200</code></pre><p>Then run a dry run (<code>-n</code> changes nothing) to see what the desktop is missing, and copy only those files:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>rsync -rn --ignore-existing --exclude='.stfolder*' --out-format='%n' YOUR_USER@SERVER_IP:/SERVER/PHOTOS/ /DESKTOP/PHOTOS/ &gt; /tmp/missing.txt

wc -l /tmp/missing.txt

rsync -av --ignore-existing --files-from=/tmp/missing.txt YOUR_USER@SERVER_IP:/SERVER/PHOTOS/ /DESKTOP/PHOTOS/</code></pre><p>For music and documents, I compared filenames anywhere on the desktop:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>export LC_ALL=C

ssh YOUR_USER@SERVER_IP 'cd /SERVER/HOME &amp;&amp; find music documents -type f -printf "%f\n"' | sort -u &gt; /tmp/srv-files.txt

find ~ -type f -printf '%f\n' | sort -u &gt; /tmp/desk-files.txt

comm -23 /tmp/srv-files.txt /tmp/desk-files.txt</code></pre><p>Finally, don't delete. Move the old copies to a hold folder until everyone has looked things over:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>mkdir -p ~/_hold-to-delete-YYYY-MM-DD

mv ~/photos ~/music ~/documents ~/_hold-to-delete-YYYY-MM-DD/</code></pre><p><em>Lesson: verify, copy, hold, then delete.</em></p><h3>3. The network card that fell off the bus</h3><p>A wired network card died and the link showed NO-CARRIER. First, find the card, its driver, and what the log says:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>lspci -k | grep -A3 -i ethernet

ip link

sudo dmesg | grep -i YOUR_DRIVER | tail -20</code></pre><p>My log said "PCIe link lost," which means reloading the driver won't help. Removing the device from the PCI bus and rescanning brought it back without a reboot (use the address from <code>lspci</code>, like 06:00.0):</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>echo 1 | sudo tee /sys/bus/pci/devices/0000:BUS:SLOT.F/remove

sleep 2

echo 1 | sudo tee /sys/bus/pci/rescan

ip link</code></pre><p>Confirm it has an address, and that Wake-on-LAN is still on if you rely on it:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>ip -4 addr show YOUR_INTERFACE

sudo ethtool YOUR_INTERFACE | grep -iE 'wake|link detected'</code></pre><p>To make a repeat less likely, I turned off PCIe power-saving (takes effect at the next reboot):</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>sudo cp /etc/default/grub /etc/default/grub.bak

sudo sed -i 's/^GRUB_CMDLINE_LINUX_DEFAULT="\(.*\)"/GRUB_CMDLINE_LINUX_DEFAULT="\1 pcie_aspm=off"/' /etc/default/grub

sudo update-grub</code></pre><p><em>Lesson: read the kernel log first. It tells you which kind of problem you have.</em></p><h3>4. When the spam filter eats your login code</h3><p>I'd tightened the mail filtering to deal with spam, and it then blocked a verification email I needed. I looked in the mail log to see who the real sender was, then whitelisted that domain, but only for mail that passes authentication:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>grep -hiE 'SENDER_NAME' /var/log/maillog | tail -15

sudo cp /etc/mail/spamassassin/local.cf /etc/mail/spamassassin/local.cf.bak

echo 'whitelist_auth *@SENDER-DOMAIN.com' | sudo tee -a /etc/mail/spamassassin/local.cf

spamassassin --lint &amp;&amp; sudo systemctl restart spamassassin</code></pre><p>File locations vary by mail setup, so adjust the paths for yours.</p><p><em>Lesson: tighten the filter, then whitelist the few services you really use.</em></p><p>Questions or similar war stories? Drop them below.</p>]]></description><guid isPermaLink="false">129</guid><pubDate>Wed, 11 Nov 2026 02:13:25 +0000</pubDate></item><item><title>When the Website Runs Out of Seats</title><link>https://mopar1973man.com/blogs/entry/128-when-the-website-runs-out-of-seats/</link><description><![CDATA[<h2>When the Website Runs Out of Seats: Diagnosing a Slow Site Like a Sick Diesel</h2><p>Tonight the site went down on me. Anyone who has chased a Cummins that "runs fine, then doesn't" knows the feeling. Everything looked healthy, but something was wrong.</p><h2>How I Caught It: The Dash Gauges</h2><p>I didn't find out because a member emailed me. I found out because of the gauges. I run Linux on my desktop, and I use a little monitoring panel called Conky that sits right on my screen and shows the health of the website server around the clock: CPU load, memory, swap, disk, uptime, whether the site is answering, even how many days are left on the security certificate. It's the same idea as a dash full of gauges in a truck. You don't have to go looking for trouble, because the needle moves before the engine quits.</p><p>Tonight the panel showed the site flip to <strong>DOWN</strong>, and a quick look at the load told me the server was struggling to keep up. That early warning is the reason I was already digging in before it turned into a long outage. If you run your own site, I can't recommend a simple monitor like this enough.</p><p></p><p><img class="ipsImage ipsRichText__align--block" data-fileid="30991" src="https://mopar1973man.com/storage/attachments/monthly_2026_11/server-panel-conky.webp.45d855bc777a397d51e684ad358b2e95.webp" alt="server-panel-conky.webp" title="" loading="lazy"></p><h2>The Symptoms</h2><p>Load on the server spiked to 17 on an 8-core machine, but the CPU was only about 20% busy. That's like a truck with the tach pegged and no power at the wheels. Then the site stopped answering.</p><h2>Ruling Things Out, One at a Time</h2><p>Like any diesel diagnosis, I worked down the list:</p><ul><li><p><strong>Bot flood?</strong> A crawler was hitting hard, but its traffic was steady all day and silent during the spike. Not guilty.</p></li><li><p><strong>Disk or memory?</strong> No disk waiting, and swap wasn't thrashing. Not guilty.</p></li><li><p><strong>Mail server?</strong> Quiet. Not guilty.</p></li><li><p><strong>DNS or SSL settings?</strong> Both checked out clean.</p></li></ul><h2>The Clue</h2><p>Timing a single page request showed the connection opened instantly, then sat for 4 to 8 seconds before the secure handshake finished, and the page came right back after that. That's a queue problem, not a power problem. Something was making visitors wait in line.</p><h2>The Answer</h2><p>The Apache error log had been shouting about it the whole time: <em>"scoreboard is full, not at MaxRequestWorkers. Increase ServerLimit."</em> Apache keeps a fixed number of seats for worker processes, and mine was set to 8. When a burst of visitors and bots filled every seat, new connections were accepted but had to stand in the aisle until someone left. The log showed it had been creeping up all week, and it got bad today.</p><h2>The Fix</h2><p>I doubled the seating, from 8 to 16 worker processes and from 200 to 400 total connections. One gotcha: Apache ignores a change like this on a gentle reload, so it takes a full restart. My restart hung for 90 seconds because the old Apache wouldn't shut down, so I also shortened the stop timeout to 20 seconds so it can't hang that long again.</p><h2>The Lesson</h2><p><strong>High load with low CPU means something is waiting, not working.</strong> Don't guess. Check one thing at a time, and read the logs, because the answer was sitting in the error log the whole time. And keep a gauge where you can see it, because the earlier you catch a problem, the cheaper it is to fix.</p><p></p>]]></description><guid isPermaLink="false">128</guid><pubDate>Fri, 06 Nov 2026 05:16:12 +0000</pubDate></item><item><title>Maintenance Oct 30 2026</title><link>https://mopar1973man.com/blogs/entry/123-maintenance-oct-30-2026/</link><description><![CDATA[<h1>Fixing Email and Spam on the Server: What We Repaired Today</h1><p>Today was a long maintenance day on the live <a rel="external" href="http://mopar1973man.com">mopar1973man.com</a> mail server. The main problem was a flood of spam hitting one of my mailboxes. While chasing it I found and fixed several other things, and I'm writing them down in case it helps someone else running their own mail server.</p><h2>1. Spam filtering wasn't working properly</h2><p>SpamAssassin was tagging most incoming mail with a "URIBL_BLOCKED" warning. That means the server couldn't use the blacklist lookups it depends on, because the public DNS resolver it was using was being rate-limited or refused. Real scoring was being skipped.</p><p><strong>The fix:</strong> I pointed the server's DNS lookups at its own local caching resolver first, with the old resolver as a fallback. Then I restarted the SpamAssassin daemon so it picked up the change. Lookups work again, and spam is scored properly.</p><p>I left the spam score thresholds alone for now. Raising them tends to catch real mail, and I'd rather fix the underlying problems first.</p><h2>2. Someone was guessing mail passwords</h2><p>The firewall logs showed an address hammering the SMTP login for one of my support mailboxes, trying password after password. My firewall (CSF/LFD) was set to tolerate far too many failed attempts before blocking.</p><p><strong>The fix:</strong></p><ul><li><p>I lowered the failed SMTP login limit from 100 to 5.</p></li><li><p>I blocked the offending address.</p></li></ul><p>If you run CSF, check <strong>LF_SMTPAUTH</strong>. A high number gives an attacker a lot of free guesses.</p><h2>3. An old "temporary" allow rule was still hanging around</h2><p>While in the firewall I found an address I had manually allowed back in June. It was in both the firewall allow list and the mail panel's trusted networks. I no longer had a reason for it, and a forgotten allow rule is a hole in your defenses. I removed it from both places.</p><h2>4. Email authentication: SPF, DKIM and DMARC</h2><p>I also started making the domain's email authentication airtight. Without it, anyone can forge mail that looks like it came from you.</p><ul><li><p><strong>DMARC:</strong> I published a DMARC record and verified it. It started in monitoring mode, and I've since moved it to a quarantine policy applied to 25% of failing mail. The plan is to raise that to 100%, then to full reject once the reports come back clean.</p></li><li><p><strong>Testing:</strong> I sent a message to Gmail and checked "Show original". <strong>SPF, DKIM and DMARC all passed.</strong></p></li><li><p><strong>DNS location:</strong> The domain's public DNS is hosted at LiquidWeb, not on the server itself, so these records are edited in their portal.</p></li></ul><h2>Still on the to-do list</h2><ul><li><p>Remove the DKIM "testing" flag now that authentication is passing.</p></li><li><p>Move SPF from a soft fail to a hard fail once the DMARC reports look clean.</p></li><li><p>Whitelist the real senders I do business with, so they never get caught by the filter.</p></li><li><p>Block the domains that only ever send spam.</p></li><li><p>Rotate the spam filter's database password.</p></li><li><p>Unsubscribe from the legitimate newsletters site by site, and clean out the mailbox after a backup.</p></li></ul><h2>Takeaways</h2><ol><li><p>Check the logs when something is odd. The blocked-lookup warnings were the real clue behind the spam problem.</p></li><li><p>Tighten your failed-login limits. The defaults are often too generous.</p></li><li><p>Audit your allow lists regularly. Old exceptions pile up.</p></li><li><p>Set up DMARC, but ramp it up gradually and watch the reports before you go to a strict policy.</p></li></ol><p>I'll post a follow-up when the DMARC policy reaches full enforcement.</p>]]></description><guid isPermaLink="false">123</guid><pubDate>Sat, 31 Oct 2026 00:26:22 +0000</pubDate></item><item><title>Give Each Section of Your Invision Site Its Own Look</title><link>https://mopar1973man.com/blogs/entry/122-give-each-section-of-your-invision-site-its-own-look/</link><description><![CDATA[<p>Invision Community has no built-in way to give each section of a site its own colors. A little custom CSS can do it. Here's how I gave the Titanium and Cloud 10 areas of this site their own look.</p><h2>The idea</h2><p>Every page on an Invision site is tagged with its section and its ID number. A blog page, for example, is tagged as the blog app with the blog's number. Pages that sit inside a section, such as a post or a forum topic, link back to their parent section in the breadcrumb at the top. CSS can look for those clues and change the site's colors only when they appear.</p><h2>Where to put it</h2><ol><li><p>In the admin area, open Customization, then Themes.</p></li><li><p>Duplicate your active theme first, so you have a backup.</p></li><li><p>Edit the theme's custom CSS and paste the code in.</p></li><li><p>Save, then hard refresh the page with Ctrl+Shift+R.</p></li></ol><h2>The colors</h2><p>Invision builds its page colors from two theme colors, a primary and a secondary. To recolor a section, change those two values for the pages you pick. The values are set on the top-level page element, not on the page body, because that's where Invision calculates the colors it hands down to everything else. I tested this on Invision Community 5.</p><h2>Example: the Titanium section</h2><p>This block turns the Titanium blog (number 11) and the Titanium forum (number 222) purple and near-black. It also catches posts, topics and gallery pages inside them through the breadcrumb:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>html:has(body[data-pageapp="blog"][data-id="11"]),
html:has(body[data-pageapp="forums"][data-id="222"]),
html:has(.ipsBreadcrumb--top a[href*="/blogs/blog/11-titanium"]),
html:has(.ipsBreadcrumb--top a[href*="/forums/forum/222-titanium"]) {
  --light__i-primary: hsl(262 20% 30%);
  --light__i-secondary: hsl(265 30% 9%);
  --dark__i-primary: hsl(262 20% 30%);
  --dark__i-secondary: hsl(265 30% 9%);
}</code></pre><h2>Template for your own sections</h2><p>Swap in your own numbers and names. The number is in the web address of the blog or forum, such as /forums/forum/224-cloud-10-computers/:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>html:has(body[data-pageapp="forums"][data-id="YOUR-FORUM-NUMBER"]),
html:has(.ipsBreadcrumb--top a[href*="/forums/forum/YOUR-FORUM-NUMBER-name"]) {
  --light__i-primary: hsl(200 28% 22%);
  --light__i-secondary: hsl(210 40% 7%);
  --dark__i-primary: hsl(200 28% 22%);
  --dark__i-secondary: hsl(210 40% 7%);
}</code></pre><p>Use data-pageapp="blog" for blogs, "downloads" for download categories, and so on.</p><h2>Tips I learned along the way</h2><ul><li><p>Pages inside a section don't carry the section's number, so match them through the breadcrumb link instead.</p></li><li><p>Some pages, such as a gallery category, don't link to themselves in the breadcrumb. For those, match the page's canonical address in the page head.</p></li><li><p>Pick colors by changing the hsl numbers. The first number is the hue, the middle is how colorful it is, and the last is how light or dark.</p></li><li><p>If the text in the header becomes hard to read on a dark background, raise the lightness a little.</p></li></ul><h2>Limits</h2><p>This changes colors and accents only. A different layout for each section would need deeper theme work. Keep a copy of your CSS in a text file in case you ever switch themes.</p><h2>Questions?</h2><p>If you try this on your own Invision site and get stuck, post in the comments or in the Servers and Security forum and I'll help you work it out.</p>]]></description><guid isPermaLink="false">122</guid><pubDate>Tue, 27 Oct 2026 21:31:43 +0000</pubDate></item><item><title>Cloud 10 Is Back: Getting the Servers in Shape</title><link>https://mopar1973man.com/blogs/entry/117-cloud-10-is-back-getting-the-servers-in-shape/</link><description><![CDATA[<p>Cloud 10 Computers is back as the home for servers, networking, Linux and security. Here's the first project: a full security check-up on my own servers.</p><p>Cloud 10 Computers started in 1994 as my custom PC building business, and it's returning as the home for everything computer-related on this site. The first project was my own backyard. While the site sat untended, I did a full security check-up and cleaned up the servers. In general terms, here's what that meant.</p><h2>Updates</h2><p>The forum software, PHP and the operating system are all brought current. Old software is one of the easiest ways in for attackers, so this comes first.</p><h2>Locking Down Remote Access</h2><p>I moved to key-based logins, turned off password logins wherever I could, and set up automatic blocking for repeated failed attempts. Servers on the internet get probed constantly, and this is the single best reason not to skip it.</p><h2>Keeping Databases Private</h2><p>Databases now only talk to the server they live on, not the open internet.</p><h2>Cleanup</h2><p>Old accounts, leftover copies of the site and unused files are gone, and the site's files now sit in a cleaner folder layout. The web address didn't change.</p><h2>A Private Tunnel</h2><p>I built an encrypted tunnel so I can reach my servers from anywhere without exposing my home network to the internet. It lets me keep an eye on everything while I'm away from the desk.</p><h2>What's Next</h2><p>In the coming weeks I'll write these up step by step for anyone who wants to do the same on a home server or a small website, along with beginner-friendly guides for moving from Windows to Linux. If there's a topic you want first, tell me in the comments.</p><p>— Titanium</p>]]></description><guid isPermaLink="false">117</guid><pubDate>Mon, 26 Oct 2026 22:51:09 +0000</pubDate></item></channel></rss>
