Today I was able to install Pihole as a Virtual Machine (VM) on my Proxmox Server. And boy is that really making a difference in the download speed for my webpages! Now that they are not laden with Advertisements that is!
I may go back thru and document the process and present a “step-by-step” post in the future.
It took a while for my SSD to be delivered, but today I was able to install Proxmox on the Dell PowerEdge Server! Some of my future projects for VMs or Containers:
- Pihole Recursive DNS Server
- pfSense Firewall / Router
- Change hosting from ISP to self-hosting Websites
- Add PLEX Server
- Blue Iris for Surveillence Camera System
- NextCloud for personal Cloud Service.
The one part that I neglected to fully research properly when I bought the Dell PowerEdge R610 Server was the pricing of the SAS 2.5 inch drives. So of course that’s going to be the part that comes back to bite me in the ass. And today, it did!
Today I found out the pricing on 2.5 inch SAS drives is crazy expensive the higher the capacity you try to go! I had originally planned on sourcing some 2TB drives, as those are the highest capacity available for my existing PERC (PowerEdge RAID Controller) 6/i, but those are $180 to $220 each! So I’ll need to research that further and see what my options are…
In the meantime, I’ve already found at least one solid option to help get this server off the ground!
A workaround that I can use is to pull the optical drive and hookup a 2.5 inch SSD to the cable instead. The system will recognize this as a boot drive and I can load Proxmox onto that. I’ll still need to get some drives for the backplane, but this will buy me some breathing room so I can take my time to find a good deal somewhere.
I just recently bought a new (to me) Dell PowerEdge R610 Server from my Green Recycling provider of choice: eWasteGurus in Sacramento. I purchased it with the dual Xeon x5670 CPU package, and 64Gb of ECC Memory! Sweet!
No Hard drives though, so I’ll need to source those on my own, which is no big deal.
This ought to keep me busy in the coming weeks and months as I build out my future ProxMox Virtual Environment Server, along with its VMs and Containers. Woot! So incredibly excited to start down this path!
Two-factor authentication (2FA) is one of the best ways for a consumer to secure account access on pretty much any platform. Accordingly, if 2FA or MFA (Multi-Factor Authentication) is offered on any platform that you currently use, then I strongly recommend that you take advantage of it.
When logging into any platform, your 1st “factor” is your password for that account. For example, if you’ve set up SMS Authentication, email authentication, or use an Authentication App, then the code/link in your SMS/email/App is the 2nd factor, thus the “two-factor” in 2FA. That single EXTRA piece of information alongside your account password goes a long way in helping to secure your account. Some would argue that SMS and E-mail 2FA are bad because they are more readily bypassed by Hackers. This is a TRUE statement, however, in my book, any type of additional “factor” for authentication is a good thing, so even SMS and E-mail is better than nothing!
Sometimes you need to prove that an Ethernet port you want to use is in good working condition, but maybe you’re having problems confirming continuity across the port to the next piece of equipment. A simple solution is to create a Loopback (LPBK) Plug and plug it into the port in question. If the port is in good working condition, then the LNK LED light will light-up to indicate that this port sees the next device and everything is good.
Well, in reality, you merely held-up a mirror for your device to see itself. As long as it was satisfied that connectivity was achieved, then the port itself is in great condition.
We just dug into a major Android Update we received back on June 8th for our AT&T Samsung Galaxy S7s, code-named “Oreo”. This update is truly useful because it resolves some long-standing issues that I’ve had with Wi-Fi over the last few years.
I’d like to discuss a little problem I’ve been having for a few years now, and it’s becoming a real pain, because it’s breaking my “mobile” user experience. In what should be a “seamless” User Experience, I seem to be tripping over the seam between my mobile device’s Mobile Data Plan and any Wi-Fi networks.
Security researchers at Armis, the security research company that had originally discovered the exploit, have identified the eight vulnerabilities — which have been collectively named as “BlueBorne”. It is expected that this set of vulnerabilities in the Bluetooth radio implementation almost certainly affects over 5.3 billion devices.
For those Bloggers like myself who used and loved the Windows Live Writer (latest version was I believe v16.4.3528.0331), it was truly the single greatest piece of code I had on my laptop at the time. I was blogging across three or four active sites at the time, and life was generally good. But then Windows Live Writer’s EOL happened: the End of Life back in August of 2012 when Microsoft decided it didn’t want to continue to support the product. I seem to recall talk of folding the dev crew into Window team. Regardless, it was a critical hit in my ability to Blog efficiently. Of course, I kept using the 2012 version, but there were times when I needed to re-install it, and lost the location of my previous download, or on those occasions in 2016 when it didn’t work very well with Win10.