Question Install Nextcloud on the Plesk??

cliccasu · Feb 7, 2022

Hi, I should install "Nextcloud" with NGINX.
Apache o NGINX?

Did I find these two guides on the internet? Which one to follow:

Nextcloud unter Plesk installieren - Foxly - IT-Blog
How to install Nextcloud 17 within Plesk with nginx only – Markus' Blog

Which directives additional to use for NGINX?
NGINX configuration — Nextcloud latest Administration Manual latest documentation

Thank you

IgorG · Feb 7, 2022

Why don't you install Nextcloud as a standard Plesk extension?

Nextcloud

Nextcloud is an open source, self-hosted file share and communication platform. Access & sync your files, contacts, calendars & communicate and collaborate across your devices. You decide what happens with your data, where it is and who can access it!

www.plesk.com

cliccasu · Feb 7, 2022

Thanks, but I prefer to install manually

IgorG · Feb 7, 2022

cliccasu said:
Thanks, but I prefer to install manually

Can I ask about the reason for the refusal of extension and choosing a manual installation?

cliccasu · Feb 7, 2022

I don't like the app. I tried it, but I prefer the manual method. Thanks again

cliccasu · Feb 7, 2022

Directives additional to use for NGINX. what do you say, okay? Thank you

# Adding the cache control header for js, css and map files
# Make sure it is BELOW the PHP block
# Add headers to serve security related headers (It is intended to
# have those duplicated to the ones above)
# Before enabling Strict-Transport-Security headers please read into
# this topic first.
#
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;

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

# 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.
# 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;

# 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 rules in this block are an adaptation of the rules
    # in the Nextcloud `.htaccess` that concern `/.well-known`.

    location = /.well-known/carddav { return 301 /nextcloud/remote.php/dav/; }
    location = /.well-known/caldav  { return 301 /nextcloud/remote.php/dav/; }

    location /.well-known/acme-challenge    { try_files $uri $uri/ =404; }
    location /.well-known/pki-validation    { try_files $uri $uri/ =404; }

    # Let Nextcloud's API for `/.well-known` URIs handle all other
    # requests by passing them to the front-end controller.
    return 301 /nextcloud/index.php$request_uri;
}

# Rules borrowed from `.htaccess` to hide certain paths from clients
#
location ~ ^/nextcloud/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)    { return 404; }
location ~ ^/nextcloud/(?:\.|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
# `/nextcloud/index.php` to the URI, resulting in a HTTP 500 error response.
#
location ~ \.php(?:$|/) {
    # Required for legacy support
    rewrite ^/(?!index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+|.+\/richdocumentscode\/proxy) /nextcloud/index.php$request_uri;

    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_intercept_errors on;
    fastcgi_request_buffering off;
    fastcgi_max_temp_file_size 0;
}

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

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

# Rule borrowed from `.htaccess`
location /nextcloud/remote {
    return 301 /nextcloud/remote.php$request_uri;
}

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

mudassar · Aug 27, 2022

IgorG said:
Why don't you install Nextcloud as a standard Plesk extension?

Nextcloud

Nextcloud is an open source, self-hosted file share and communication platform. Access & sync your files, contacts, calendars & communicate and collaborate across your devices. You decide what happens with your data, where it is and who can access it!

www.plesk.com

does this still exist? it does not show in my extensions?

Maarten · Aug 27, 2022

mudassar said:
does this still exist? it does not show in my extensions?

What is your OS version and Plesk version?

https://support.plesk.com/hc/en-us/articles/213949665

mudassar · Aug 30, 2022

plesk
Version 18.0.44 Update #3

windows 2019.

Is it because I am not linux?

IgorG · Aug 30, 2022

mudassar said:
Is it because I am not linux?

Yes, Platform is defined as Unix only here: Nextcloud

Question Install Nextcloud on the Plesk??

cliccasu

Basic Pleskian

IgorG

Plesk addicted!

Nextcloud

cliccasu

Basic Pleskian

IgorG

Plesk addicted!

cliccasu

Basic Pleskian

cliccasu

Basic Pleskian

mudassar

Basic Pleskian

Nextcloud

Maarten

Golden Pleskian

mudassar

Basic Pleskian

IgorG

Plesk addicted!

Similar threads