手动安装nextcloud

新入手了VPS后，一直琢磨着倒腾个网盘，工作用。 从seafile、owncloud到其它一系列的尝试了不少，最后决定使用nextcloud。被这个nextcloud折磨了三四天，我都有点佩服自己的毅力了。

趟过的坑

• 最开始是自己配置的nginx，被404反复虐待。
• 后来怀疑是自己安装的lnmp环境有问题，于是手动安装各种修改，或者使用一键安装脚本，来回折腾。
• 后来隐约觉得问题出在rewrite，于是使用官方的推荐的nginx配置，但是一直没有安装证书，所以将配置中的证书部分删除了，觉得我暂时不使用证书，对整体应该没有影响吧。结果还是被404虐着。后来灵光一现，继续重置vps的硬盘，重新来过，先安装上证书，然后再使用官方的推荐配置，可算是可以了。

安装LNMP环境

参考ubuntu手动安装LNMP环境完成安装。

配置nginx并安装SSL证书

新建文件夹，用来存放网站文件：

mkdir /var/www/file.zimohan.com

在nginx配置文件所在位置（/etc/nginx/sites-enabled/）下新建网站的配置文件（file.zimohan.com.conf）：

vi file.zimohan.com.conf

粘贴如下内容：

server {
        root /var/www/file.zimohan.com;
        index index.html index.htm index.nginx-debian.html;
        server_name zimohan.com;
        location / {
                try_files $uri $uri/ =404;
        }
}

这是一个基本的nginx网站配置文件，完成后使用nginx -s reload使刚才新建的配置文件生效，然后输入我们的域名，应该就能正常访问了。
接着添加SSL证书，这一步很重要，我就是因为忽略了这一步，结果折腾了两三天。参考免费的HTTPS证书-Let's Encrypt添加免费的SSL证书。

修改nginx配置文件

要成功运行nextcloud，需要对nginx网站的配置文件做些改动，官方也有推荐的配置，我这里对官方的配置文件做了些微改动：

#upstream php-handler {
    #server 127.0.0.1:9000;
    #server unix:/var/run/php/php7.4-fpm.sock;
#}

server {
    listen 80;
    listen [::]:80;
    server_name docs.zimoapps.com;

    # Enforce HTTPS
    return 301 https://$server_name$request_uri;
}

server {
    listen 443      ssl http2;
    listen [::]:443 ssl http2;
    server_name docs.zimoapps.com;

    # Use Mozilla's guidelines for SSL/TLS settings
    # https://mozilla.github.io/server-side-tls/ssl-config-generator/
    ssl_certificate     /etc/letsencrypt/live/zimoapps.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/zimoapps.com/privkey.pem;

    # HSTS settings
    # WARNING: Only add the preload option once you read about
    # the consequences in https://hstspreload.org/. This option
    # will add the domain to a hardcoded list that is shipped
    # in all major browsers and getting removed from this list
    # could take several months.
    #add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;

    # set max upload size
    client_max_body_size 512M;
    fastcgi_buffers 64 4K;

    # Enable gzip but do not remove ETag headers
    gzip on;
    gzip_vary on;
    gzip_comp_level 4;
    gzip_min_length 256;
    gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
    gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;

    # Pagespeed is not supported by Nextcloud, so if your server is built
    # with the `ngx_pagespeed` module, uncomment this line to disable it.
    #pagespeed off;

    # HTTP response headers borrowed from Nextcloud `.htaccess`
    add_header Referrer-Policy                      "no-referrer"   always;
    add_header X-Content-Type-Options               "nosniff"       always;
    add_header X-Download-Options                   "noopen"        always;
    add_header X-Frame-Options                      "SAMEORIGIN"    always;
    add_header X-Permitted-Cross-Domain-Policies    "none"          always;
    add_header X-Robots-Tag                         "none"          always;
    add_header X-XSS-Protection                     "1; mode=block" always;

    # Remove X-Powered-By, which is an information leak
    fastcgi_hide_header X-Powered-By;

    # Path to the root of your installation
    root /var/www/docs.zimoapps.com;

    # Specify how to handle directories -- specifying `/index.php$request_uri`
    # here as the fallback means that Nginx always exhibits the desired behaviour
    # when a client requests a path that corresponds to a directory that exists
    # on the server. In particular, if that directory contains an index.php file,
    # that file is correctly served; if it doesn't, then the request is passed to
    # the front-end controller. This consistent behaviour means that we don't need
    # to specify custom rules for certain paths (e.g. images and other assets,
    # `/updater`, `/ocm-provider`, `/ocs-provider`), and thus
    # `try_files $uri $uri/ /index.php$request_uri`
    # always provides the desired behaviour.
    index index.php index.html /index.php$request_uri;

    # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
    location = / {
        if ( $http_user_agent ~ ^DavClnt ) {
            return 302 /remote.php/webdav/$is_args$args;
        }
    }

    location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
    }

    # Make a regex exception for `/.well-known` so that clients can still
    # access it despite the existence of the regex rule
    # `location ~ /(\.|autotest|...)` which would otherwise handle requests
    # for `/.well-known`.
    location ^~ /.well-known {
        # The following 6 rules are borrowed from `.htaccess`

        location = /.well-known/carddav     { return 301 /remote.php/dav/; }
        location = /.well-known/caldav      { return 301 /remote.php/dav/; }
        # Anything else is dynamically handled by Nextcloud
        location ^~ /.well-known            { return 301 /index.php$uri; }

        try_files $uri $uri/ =404;
    }

    # Rules borrowed from `.htaccess` to hide certain paths from clients
    location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)  { return 404; }
    location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console)              { return 404; }

    # Ensure this block, which passes PHP files to the PHP process, is above the blocks
    # which handle static assets (as seen below). If this block is not declared first,
    # then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
    # to the URI, resulting in a HTTP 500 error response.
    location ~ \.php(?:$|/) {
        fastcgi_split_path_info ^(.+?\.php)(/.*)$;
        set $path_info $fastcgi_path_info;

        try_files $fastcgi_script_name =404;

        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $path_info;
        fastcgi_param HTTPS on;

        fastcgi_param modHeadersAvailable true;         # Avoid sending the security headers twice
        fastcgi_param front_controller_active true;     # Enable pretty urls
        fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;

        fastcgi_intercept_errors on;
        fastcgi_request_buffering off;
    }

    location ~ \.(?:css|js|svg|gif)$ {
        try_files $uri /index.php$request_uri;
        expires 6M;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    location ~ \.woff2?$ {
        try_files $uri /index.php$request_uri;
        expires 7d;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    location / {
        try_files $uri $uri/ /index.php$request_uri;
    }
}

下载并安装nextcloud

剩下的就是下载安装报并安装了，其实到这里已经很简单了，因为前面我们做的铺垫工作已经到位。
由于我这里是国内的vps，服务器端下载安装包很慢，所以到官网下载安装包再上传到我们的服务器。解压后得到nextcloud文件夹，将文件夹内的文件复制到网站所在目录（file.zimohan.com），或者干脆删除该目录，将nextcloud重命名为file.zimohan.com：

mv nextcloud file.zimohan.com

同时，还需要注意权限问题。赋予网站文件夹相应的权限，具体权限要给到啥程度才行，我也不知道，先给个777权限跑起来再说：

chmod -R 777 /var/www/file.zimohan.com

接下来就是见证奇迹的时刻了，访问我们的域名，开始安装。过程很简单，输入账号密码，配置好数据库的用户名和密码，稍等片刻就转到登录地址，登录使用吧。