Introduction
Hello everyone! Recently, I built a “small server” at home that allows for remote downloading, remote media streaming, and remote Windows access, saving me the cost of a cloud Windows server. It’s quite comfortable to use, so I want to share my experience.
Yes, it’s the small mini host in the picture above that fulfills my “small server” needs. If you think it’s something like a high-end server setup, please scroll past, as this setup might seem “low-end” to the experts, but it’s accessible to everyone.
After all, most friends, like me, have ordinary needs, or simple cloud server requirements. Or you can think of it as how to enable remote access and NAS storage on your server, thus achieving the goal of becoming a “home small cloud server”. Since I have a long-term need for cloud hosts, I often buy small hosts from Alibaba Cloud or Tencent Cloud to use Windows as a dedicated server. This led me to set up this “small cloud server” at home to meet my needs, eliminating the need to renew cloud host fees.
Likewise, since I treat it as a cloud server, I can let it perform more functions. In addition to the Windows system, I also transformed this “small cloud server” into a remote NAS, remote media server, remote monitoring server, and remote Docker machine, offering a variety of functions. For example, using Jellyfin to connect to this server for remote viewing, and it also allows for remote downloading of resources, which has been working very well for over half a month.
In this article, I will share the complete process of building my own “small server”, including hardware selection, the reasons behind my choices, as well as the system selection and the methods I used to turn this “small server” into a remote download machine and media server. I will also explain how to set up and choose remote access solutions, providing many reference solutions for friends with similar needs. Since I’m not good at writing theoretical content, I hope to share my practical experience in a way that is easy for beginners to understand. Let’s get into the main content.
Determining Hardware
Initially, I decided to deploy this “small server” at my hometown because the area where I currently live often experiences power outages. Considering various factors, this was my decision. Before the New Year, I had already improved the network at home, making it suitable for this setup.
Home network transformation! Achieving full-house WiFi coverage and surveillance monitoring, insights from the entire renovation and purchasing process!
Since it’s set up at my hometown, I only visit occasionally, so this machine needs to meet the following conditions:
1. Supports power-on self-start and WOL wake-up 2. Silent, passive cooling, energy-saving 3. Compact size, mini is best; I only consider adding one or two solid-state drives, not mechanical drives
Power-on self-start is essential; otherwise, if there’s a sudden power outage, it would be troublesome to ask my elderly family members to turn it on. I aim to minimize maintenance and manual operations. Supporting power-on self-start is related to the BIOS, and most motherboards support it. Thus, even after a sudden power outage, the machine will automatically start when power is restored, ensuring it’s online. Another feature is WOL wake-up, which might be less frequently used. As long as you don’t shut down the system, if you accidentally shut it down, you can use WOL to wake it up. I have integrated a PuGongYing X1 box into my hometown network, which supports WOL wake-up, making this feature necessary. If I accidentally shut it down, I can wake it up using WOL.
60 yuan! A one-time solution for remote access, an overview of the advantages and disadvantages of the PuGongYing X1 networking box! As for the machine size, I considered placing it on top of the weak current box shown above, so it needs to be compact and space-saving. Otherwise, my elderly family members would find it too big and complain. I opted for all solid-state drives instead of mechanical drives because I’ve told my parents that if the network lags, they can just cut off the main power to restart the network, which is simple and convenient. If I add a mechanical drive, I fear it might get damaged during a power outage. With solid-state drives, I can play around without worry. So, I followed these principles to find the right hardware. I searched extensively and considered options like the N5105 mini host, which costs around 6-7 hundred, but I read that it generally generates a lot of heat, so I abandoned it.
I also looked on second-hand platforms, but many were relics, and I couldn’t find what I wanted. In the end, I decided to use my idle 3865U mini host from when I was playing around with soft routing. It still performs decently for my needs, even if it’s considered low-end by experts.
For those pursuing miniaturization, there are plenty of other types of mini hosts to consider!
The 3865U machine can only accommodate one SATA and one mSATA drive. Considering solid-state drives, I went with a 1TB solid-state drive, which is sufficient for my needs. After all, there is a proper NAS in my long-term residence, and solid-state drive prices are currently very low, costing less than 300 yuan with a five-year warranty from Dongge, so I feel safe using it.
I directly opted for 8GB of memory, which is adequate for my current needs.
Of course, my mini host’s performance is still weak. If you have high-performance needs, feel free to choose better options according to your requirements. I’m just sharing my hardware selection considerations.
System Solutions
Next up is determining the system solution. There are various systems available for servers. If you want to play with multiple systems, consider PVE, ESXI, and other virtualization systems, which are mainstream options. I have previously provided tutorials on creating AIO setups using PVE and ESXI. Interested friends can check those articles.
Installing OpenWRT + Synology NAS + Windows on PVE, creating an AIO, including PVE network card and hard disk passthrough
Installing OpenWRT + Synology NAS + Windows on ESXI, creating an AIO host, including hard disk and network card passthrough tutorial
As for me, I’m accustomed to using NAS, so I have a preference for the Synology system. I directly decided to install the Synology system as my base layer. Synology also supports virtualization, and since I only need one Windows virtual machine, the built-in virtual machine support is sufficient for my needs.
Additionally, I am familiar with Synology Docker, and I often consider deploying Docker containers remotely, which is more user-friendly than SSH command operations.
Of course, you can choose PVE or ESXI as the base for your small server; both options work well. Ultimately, you can install whatever system you want, as long as it meets your needs. I also considered some remote media needs, which is why I decided to install Synology as the base. I won’t go into too much detail about the installation guide for Synology, but interested friends can refer to my article on that.
Beginner-friendly guide to installing Synology, turning idle computers into NAS~
Local and Remote Access Solutions
Of course, a cloud server has remote access solutions. For mainstream cloud servers, after purchasing, you get a public IP that allows for direct remote access. For example, I bought a Tencent Cloud host and installed Windows, so I can access it via its public IP for remote desktop.
However, since I’m deploying it at home with mobile broadband, which is notoriously behind in public IPv4 applications, I couldn’t apply for a public IPv4 IP. However, I do have a public IPv6 assigned. Currently, almost all newly installed broadband supports both IPv4 and IPv6, and the government is actively promoting IPv6. Therefore, the first choice for remote access is public IP. If I don’t have IPv4, I use public IPv6 for remote access. I have previously written articles on remote access via IPv6; interested friends can check them out!
Solving the difficulty of accessing Synology externally! Using IPv6 + DDNS for full remote access to internal devices + enabling HTTPS access!
Common solutions for NAS and internal device remote access and penetration, there’s always one that suits you~ Including references for QNAP public IPv6 remote access settings
For Windows, you can install remote desktop applications like Todesk, which allows for easy P2P connections with very fast speeds in the presence of IPv6.
Since I’m using Synology as the base, I can install containers like DDNS-GO in Synology Docker, along with a domain name that costs a few bucks a year to implement IPv6 DDNS resolution, allowing remote access to the Synology backend and remote desktop operations.
As shown in the picture above, this is the DDNS interface, which binds IPv6 to the domain name. This way, when I’m remote, I can access this domain to get to the NAS and all its services, achieving remote access and thus achieving “cloud” functionality. If using a mobile optical modem, if you conduct all operations over IPv6, you can obtain the super password and then turn off the IPv6 SPI in the security-firewall settings of the optical modem to enable external remote access to this “small server”.
Additionally, to ensure everything runs smoothly, I added a PuGongYing X1 networking box. As long as there’s internet, I can achieve remote access through remote networking. This acts as a backup solution, so as long as there’s internet, I can remotely access the NAS backend for maintenance. Besides public remote access, you can also consider remote networking solutions like Zerotier and Tailscale. I recommend Tailscale, as Zerotier often fails to connect on mobile networks, while Tailscale is very stable. I’ve also deployed Tailscale on the NAS, which can be set up in Docker or various operating systems, and it’s very simple and fast. I have a 30 Mbps upload speed, and it can exceed 20 Mbps, which I highly recommend.
Currently, my main remote access solution for this “small server” is primarily based on IPv6, supplemented by Tailscale, with the PuGongYing networking box as a backup. I don’t have to worry about maintenance issues.
What Can the Small Server Do?
Now, let’s talk about what I use this “small server” for. It’s really about practical needs, not some impractical uses.
Usage 1: NAS Storage, Online Cloud Storage
Since I chose to install Synology as the base, I can use it as a proper NAS, setting up remote access, IPv6, etc., to enable remote access.
However, with an upload speed of only 30 Mbps, this means the remote download speed is about 3 MB/s (conversion: 8 Mbps equals 1 MB). Occasionally calling and downloading, I think this speed is still quite good, unlike some cloud storage where the speed is only over 100 KB.
Additionally, if you use other bases like PVE or ESXI, you can similarly install Synology or other NAS systems to achieve remote NAS functionality. There are many paths to the same destination. After all, I also use it as a remote media server, so storage needs are fundamental.
Usage 2: Installing Windows and Linux Systems
If you use PVE or ESXI as the base, you can freely install various systems. Common cloud servers usually run on Linux or Windows systems, allowing for customizable selection. The premise of a small server is that you can install various virtual machine systems. For example, you can install a Linux system for learning purposes. The reason I wanted to set up a small server was that I had this kind of need. Previously, I had purchased student hosts from Alibaba Cloud and Tencent Cloud for three years.
360 yuan for three years with a bandwidth of 1 Mbps, just enough for remote desktop to run smoothly. I used it to install Windows, which needed to run 24/7, which is why I purchased it. As of the end of this year, my three-year term will be up, and the main reason for deploying this “small server” at my hometown was to install a virtual Windows system, eliminating the need to renew cloud host fees. Thus, I installed the Windows system on the Synology virtual machine. Initially, I planned this way, and I’ve tested the 3865U. It runs reasonably well with a Windows system. After all, the cloud host’s smoothness isn’t that great, but at least it’s better than the cloud host. So, I considered a larger memory from the start, opting for 8GB, with 4GB allocated to the virtual system and the remaining 4GB for running Docker and NAS smoothly.
Having installed Windows, I also needed to set up remote desktop. I didn’t experiment too much with remote desktop solutions, directly considering options like Sunlogin or Todesk. Ultimately, I chose Todesk because of the IPv6 connection, allowing for a very smooth remote desktop experience.
With this setup, I no longer need to renew the cloud host; I can operate everything using my “small server”. I’ve been running the software I need on the virtual Windows system for about a month now, and it’s been very stable, similar to my previous cloud host experience.
Usage 3: Online Cloud Sync Tools
Another way I use it is to sync files with online cloud storage using Synology’s built-in Cloud Sync tool. Although some online cloud storage is slow, I can simply drop some non-urgent files into it, and this “small server” will automatically sync them locally. Coupled with remote access, I can directly download and access them, breaking through the 100 KB speed limit.
With the previously mentioned remote methods, I can achieve download speeds of over 3 MB, making the experience much smoother. This usage may not be common, but it works for me.
Usage 4: Connecting Surveillance Cameras
Another common use is connecting surveillance cameras. NAS systems like Synology and QNAP have corresponding surveillance suites. As long as your cameras support ONVIF protocol, they can be seamlessly integrated into the NAS, using it as a storage space for surveillance recordings.
I have connected several cameras from my home to this “small server”. Although I already have an NVR for recording, having another copy on the NAS is a great way to ensure data safety and redundancy.
For specific camera models and solutions, you can refer to my previous article on home network renovations, which includes detailed descriptions.
After enabling IPv6 remote access, I tried downloading surveillance footage from the NAS without any issues, achieving speeds of 3.2 MB/s, fully utilizing my hometown’s 30 Mbps upload speed. Indeed, public access is the fastest, while other non-public options are merely backups.
Usage 5: Remote Download Machine + Media Server
Another way to utilize this “small server” is as a remote download machine and media server. First, you can install applications like qBit or Transmission for downloading. These downloaders are multi-platform, and if you install other systems, they also have clients available. Since I deployed on Synology, I installed these download applications via Docker or package form.
With the previously mentioned remote access solutions, I can access these applications’ backends anytime, anywhere. If I want to watch a movie, I can just drop the resource into the downloader and let it work quietly.
Moreover, I integrated Jellyfin along with various media organization tools like NASTool. Once these resources are downloaded, they are automatically organized, renamed, and displayed in Jellyfin’s media server with their respective posters. In the image below, I remotely accessed the Jellyfin media server on this small server via IPv6, achieving full public access and utilizing the server’s 30 Mbps upload speed. With real-time transcoding, I can easily watch 1080p resources without any lag.
Additionally, I can install the Jellyfin client on my phone. Nowadays, most broadband connections and mobile data support IPv6, allowing for seamless remote viewing. The combination of download applications and media servers works perfectly together.
The media server can transcode high-bitrate resources into lower-bitrate formats. For instance, when my mobile data is capped at 3.1 Mbps, I can set the video quality to below 3 Mbps, allowing the media server to transcode and stream smoothly at that speed. This is why real-time transcoding is essential. As shown in the image, even if Jellyfin transcodes to 480p at 3 Mbps, it feels comparable to the 720p quality of many major video sites, as they compress their bitrates too low.
Actual Experience
After using it for about half a month, I can say it’s very stable. Coupled with the previously mentioned remote solutions, the experience is smooth. For example, if I want to watch a certain movie, I can find the resource, drop it into the remote qBit, and that’s it.
After a while, I can open the remote Jellyfin and enjoy watching movies, whether on my phone or computer. Whether using IPv6 or Tailscale for remote viewing, it’s all very smooth. I’ve been using it for over half a month, and it’s been quite comfortable. Even with my mobile data capped at 3.1 Mbps, I can set the quality below 3 Mbps, and the server can transcode for smooth viewing. The integrated graphics of the 3865U performs well for real-time transcoding, even supporting 4K transcoding. Therefore, setting up a media server is indeed a great choice.
As for the most crucial aspect, I deployed Windows on the Synology virtual machine, and using Todesk for remote desktop works very smoothly, establishing a point-to-point connection with great comfort.
With this setup, the software I need on the virtual Windows system runs stably for over half a month without issues, requiring minimal maintenance. Currently, I’ve used up most of the space and am considering whether to replace it with a larger hard drive during my next visit home. The smoothness has made it a regular part of my setup, and 1TB of space is starting to feel insufficient.
Additionally, with power-on self-start and WOL remote wake-up, I don’t have to worry about reconnecting after power outages. As long as the broadband is paid, it will run normally.
Final Thoughts
This article briefly shared my journey in building a dedicated “personal server” and the solutions I implemented. There’s no grand server room, just a simple mini host that fulfills my goals. If I have multi-system needs in the future, I might look for a more powerful low-power mini host. For now, the 3865U mini host is sufficient for me. It’s currently placed above the weak current box in my hometown, and since the mini host has a wall-mounted backboard, it fits perfectly and is hidden away. My mom won’t see it and won’t complain, and it doesn’t make any noise.
In summary, hardware is secondary; the key is to find hardware that suits your needs. If you want to build a server room, that’s also fine. Those who build server rooms probably won’t be reading this article, and my setup would seem trivial to them. I will continue to share more interesting setups and solutions in the future, so if you liked this article, please like and follow for more updates!
Previous exciting articles:
69! MS2130 video capture card! True 1080P + USB 3.0!
Is “sleeping income” reliable? The struggles and feelings of running broadband PCDN, discussing the problems encountered and the process, as well as cost calculations.
300 yuan to self-build a NAS with decent performance, an overview of the pros and cons of the Sinoc chassis as an entry-level NAS experience.