How to install Cloudreve on Feiniu NAS? It’s too difficult to transfer large files via WeChat. I can open web pages on my mobile phone and computer after installing it.

A while ago, I sent an 8-minute video to my family. I uploaded it on WeChat first, and the person who received it said it was as blurry as a mobile phone from ten years ago. I changed the network disk again, and the speed limit for non-members made me want to smash the keyboard. The Feiniu NAS at home is turned on every day, and most of the hard drive is empty, so I thought: Can I install my own network disk on it and transfer files without going through other people's servers? After struggling for half a night, I finally got Cloudreve plugged in, and I can open it on my mobile phone, computer, and browser. The following is written in the order that I have stepped on it. Follow the instructions and you will not get stuck on the password step.

What exactly is Cloudreve? Think about these three points before installing it.

Simply put, Cloudreve is an open source personal network disk that runs on your own NAS. The file is stored on your hard drive and does not go through WeChat or those speed-limited public network disks. It is not the same thing as the shared folder that comes with Feiniu. The latter is mainly used on your home LAN. Cloudreve is more like a web interface like Baidu Netdisk. You can register multiple accounts, and you can also generate a shared link with a password for a certain file, and send it to others to open it and download it.

But there are three accounts that need to be settled before taking action. First, it uses Docker, not a kit that can be installed with just one click in the Feiniu Application Center. You must at least know what "port mapping" and "directory mounting" are in Docker, otherwise you will not be able to open the web page after installation. I have written an article about this before, you can read it first How to get started with Docker on Feiniu NAS . Second, the default web port of Cloudreve is 5212. After installation, it can only be opened in your home LAN. If you want to transfer files outside, you will need to connect to intranet penetration or public IP later. Third, it is a network disk itself, not an automatic synchronization disk. Mobile phone photos will not flow there by themselves. To synchronize, you need to install a separate WebDAV client.

The machine I used this time is Feiniu fnOS N100, with 8G memory, 128G system disk, and a 2T mechanical disk. There is no pressure at all when running Cloudreve with this configuration. The free memory consumes more than 100 MB, and the CPU usually hovers in single digits. If you are Synology, the process is the same, but the Docker interface looks different.

I used Compose to run it once. Don’t copy the wrong port and directory.

In Feiniu's Docker management, I use Compose directly, which is less likely to leak than parameter by parameter point. First create the directory. I am used to putting it under docker in two layers. The command is as follows:

mkdir -p /vol1/1000/docker/cloudreve/data mkdir -p /vol1/1000/docker/cloudreve/uploads

The first data contains the configuration and database, and the second uploads contains the files you passed in. You can change the directory name, but the two directories must be separated. For later upgrades and moves, the files you really care about will be in uploads. Then create a new Compose and post the content.:

services: cloudreve: image: cloudreve/cloudreve:latest container_name: cloudreve restart: unless-stopped ports: - "5212:5212" volumes: - /vol1/1000/docker/cloudreve/data:/cloudreve - /vol1/1000/docker/cloudreve/uploads:/cloudreve/uploads

I have kept the port 5212 unchanged. If other services in your home already occupy 5212, change the one before the colon to something else, such as 5213, and the browser will open 5213. Don't change the 5212 in the container after the colon, it's hard-coded by Cloudreve. I use the absolute path for directory mounting, don’t write it as ./data This kind of relative path, otherwise Feiniu updates the container directory and changes someday, and the files you upload will not be found.

After saving, start the container and it will initialize itself for the first time. Don't rush to log in with the browser at this time, because the initial account password is not on the interface and is hidden in the log.

The initial password is not on the page and I got stuck here the first time.

After the container starts, I open 192.168.31.11:5212 , I was confused when I saw the login box, and no account or password was given. There is no registration button either. Later, I checked in the container log and found that the password was in it. Click the container log on the Feiniu Docker interface, or SSH in and type:

docker logs cloudreve

There will be a paragraph in the log similar to "Admin user name: admin@cloudreve.org ”and "Admin password: a string of random characters" prompt. The password is generated every time it is initialized. After you log in for the first time, immediately go to the backend to change the password to one you remember, and then change your email address. The password I had at that time contained uppercase and lowercase letters and numbers. I entered it incorrectly three times and almost thought my password was broken.

The first thing you do after logging in is not to transfer files, but to go to the management backend to look at the storage policy. Cloudreve will put files into the uploads directory by default. You can see that the "Default Storage Policy" in the personal settings shows local storage. If it displays red or the capacity is 0, go back to Docker and check whether the uploads mount is written correctly. This is where most people turn over.

How to upload large files without failure? First change these two numbers.

On the day it was installed, I uploaded a 4.2G video, but it got disconnected halfway through. I came back to check the logs and found that it was not a hard disk problem, but that the default upload size and timeout had not been adjusted. You can change the upper limit of single file size in the "Parameter Settings" in the Cloudreve backend. I directly set it to 0, which means no limit at first. If the Nginx or Feiniu anti-generation layer is also stuck, it is often because it limits the upload size to tens of MB, so you need to go to the anti-generation configuration separately. client_max_body_size Turn it up.

There is another problem with transferring files through the browser: The computer goes to sleep, the network shakes, and the task is interrupted. Small files don’t matter, but for materials of dozens of gigabytes, I recommend using WebDAV to hang them on your computer and drag them. To open WebDAV in Cloudreve, you need to create an account in the background "WebDAV" and remember the path and password it gives. Windows can use RaiDrive and Mac to directly access the Dalian server. After it is mounted, it will be a network disk, and you can drag folders into it, which is much more stable than a web page.

I tried it on a Gigabit LAN, and the webpage upload speed was around 90MB/s. WebDAV was about the same, and it basically filled up the continuous writing of the mechanical disk. Don't think about this number when you are on the external network. Your home uplink may only be 30M, but if you reduce it to more than 3MB/s, send a link to let people outside download. The speed is mainly stuck in the uplink provided by the operator, and it is not Cloudreve's fault.

If you want to be able to drive it outside, don’t connect 5212 directly to the public network.

After Cloudreve can be used in the LAN, the next step is the external network. I don’t have a public IP address at home, it’s a telecom intranet, so I didn’t use port forwarding. You can first check whether you have a public IP. If so, transfer a certain port on the external network to 5212 on the NAS in the router, and then bind a DDNS to use it. But I don’t recommend running around naked. It is equivalent to exposing a network disk backend to the public network. If the password is scanned, it will be troublesome. If you really want to enable it, use at least one layer of HTTPS and don’t use plaintext HTTP to transfer files.

People who don’t have a public IP can just use the intranet to penetrate. I already have a set of frp at home to connect to the NAS, so Cloudreve is hung directly under the same tunnel, and one more subdomain name is mapped to the intranet 5212. This article explains the construction ideas in more detail.: How to connect to the NAS at home without a public IP? . If you only need to send files occasionally, you can temporarily use Feiniu's built-in remote access to send files. You don't need to connect Cloudreve to the external network every day, which is more worry-free.

Regarding the security related to external network access, I paid the tuition alone, and the port was scanned after running naked for a week. The experience in this article can be copied directly.: How to enable secure external network access to NAS . The same goes for Cloudreve: If you can't enable it, don't enable it. If enabled, add a password, add HTTPS, and don't use the default port.

These types of people will be very happy after pretending. I advise you not to bother with these types of people.

It is suitable for people who install Cloudreve. The first category is those who often send large files to others, but do not want to use WeChat to compress the image quality or become a network disk member. The second type is that the NAS at home is open 24 hours a day, and they want to control the data themselves, so they have multiple web version network disk entrances. The third category is those who have multiple devices and want more detailed grouping and sharing permissions. Cloudreve can share a directory with family members individually, and can also set passwords and expiration dates.

On the other hand, if you just back up your own mobile phone photos, Feiniu's own photo album and Synology Photos are both more convenient than Cloudreve, so there is no need to add an extra layer. If you are already using Feiniu's own FN Connect or Synology QuickConnect to transfer files remotely, and your need is to "pull a file occasionally", Cloudreve can also be considered a redundant construction. It is suitable for "sharing and multi-person file exchange", not a replacement for automatic backup and synchronization. The difference between these two functions, I have used it before: How do you connect to your home NAS from outside? , How to send files in NAS to others , it will be easier to judge which one you should pretend to be after reading it.

Finally, string the process together: First create two directories, data and uploads, and use Compose to run the container port 5212. ； The initial password is in docker logs cloudreve Please change it immediately after logging in. ； Before transferring large files, increase the upper limit of a single file and the size of the reverse generation, and use WebDAV for stable transfer. ； For external network access, priority is given to the existing internal network penetration, and do not use 5212 to go to the public network naked. Cloudreve itself is not difficult. What is difficult is to avoid the four pitfalls of "port, directory, password, and external network" in order. If you pass these four, your NAS will truly have its own network disk.