Do a fresh NC installation.
NextCloud Installation Q & A
-
- OMV 3.x
- tinh_x7
-
-
Yes, you need to create a MySQL user for nextcloud. Either way is OK, cli or MySQL plugin. However I suggest to create a dedicated one especially for nextcloud and not to use a root user.
Thanks. It's works.
-
Do a fresh NC installation.
I did a fresh OMV 3 installation and I followed the steps.
Step 7 fails with 404 Not found. Attaching screens.
-
-
Did you install it in the right directory ?
-
Activate the nginx server before creating the php pool.
Check the path and privileges of the directory used as webroot. ACL/privileges should be www-data:www-data with 755 or less
-
Hello All,
After I upgraded from OMV3 to OMV4, I struggle to log into OMV web page.
I couldn't find any solution.
So, I start a fresh installation.Ensure you install: redis-server php-redis
This is for OMV4 PHP7 only:
I've spent 40 mins. to found out the issue that many users have 502 Bad Gateway error at the installation process due to the Nginx code.
Change this: fastcgi_pass $socket; to this: fastcgi_pass unix:/run/php/php7.0-fpm.sock;
Restart your Nginx service: sudo service nginx restart
And try again. -
-
Ok i do have a question: this guide seems to be geared toward having nextcloud running on the root directory of the listed website. I would like for it to run in a subdirectory. I did review the subdir code on the nextcloud page but for some reason I cannot get it to work. I get a login page but when I click logon, it doesn't work.
I guess I can start over but I would like some advice for whomever attempted this
EDIT: I tried following this https://docs.nextcloud.com/ser…l/installation/nginx.html and I used those SubDir settings from add_header X-Content-Type-Options nosniff; on down, and its working now. I used the gzip off and fast-cgi settings from @tinh_x7 guide. Also the server is pointing to www instead of nextcloud.
I swear I did this already and It was working, but then broke. So I'll see how long it lasts
EDIT2: I guess if i do have a question, it would be how can i get the URL to point to openmediavault.local:{port}/nextcloud instead of it being localhostopenmediavault.local:{port}
-
You can change the NextCloud URL in the config.php
-
Did you install it in the right directory ?
This is before nextcloud installation, step 7
-
-
-
That's what I'm saying, I cannot even start the installation.
-
You can change the NextCloud URL in the config.php
So you mean to say, i can change the url in the attached image location, from the nextcloud config.php?
The reason I am asking, is that with the settings i have used (from my prior post) I am serving that on
http://192.168.1.23/nextcloud
but the nginx websites is showing
http://192.168.1.23:80 -
-
No, I'm talking about your domain URL.
Leave the local IP alone. -
Hi. Im running OMV3 on AMD e-350 2 cores 2 threads 1,6GHz, 15W TDP, 4GB of RAM and 2x500GB mirror ZFS pool. 82% of RAM is taken by ZFS and services (samba, nfs and transmission). I have public but variable external IP (binded with noip.org to some domain). Also i can have free domain on some hosting server (my sister has 2 sites there).
1. How much ram Nextcloud needs? I can change the ammount of RAM ZFS takes (now it takes 2,5GB).
2. Im more familiar with apache but nginx is less resource hungry, wont need proxy module and AFAIK OMV is using it. Should i stick with it or choose apache anyway for NC?
3. (Nginx choice) Did anyone try those configs? If not do you know any nginx configs that work on OMV?
https://docs.nextcloud.com/ser…l/installation/nginx.html
4. Is PHP 7 neccesary for NC 11?
5. I self-signed SSL enough for some basic security (im the only one who will use this cloud)?
6. I know the answer but ill ask anyway to be 100% sure: is there any way to use this free domain i have (on my sisters hosting server) instead of ddns domain i got from noip.org and use some SSL for it? -
1.
CodeMemory requirements for running an Nextcloud server are greatly variable, depending on the numbers of users and files, and volume of server activity. Nextcloud needs a minimum of 128MB RAM, and we recommend a minimum of 512MB
2. OMV using Nginx, so it would be easy to use the same engine.
Nginx uses less resource than Apache.3. The vhost config is already posted in this forum.
4. No. However, Nextcloud v14 will require PHP 7.
5. yes
6. Yes
-
-
6. Yes
Hmm, really? Because as far as i heard DDNS is the only good way. Otherwise you will have to make some scripts similar to DDNS service and put them into CRON.
-
Ive installed Nextcloud with SSL. And i have questions about OPcache.
Here you suggested to put it in main php.ini in fpm module.
But each php module have its conf.d directory with its config files. And each of them have opcache.ini file with this content.
Code: 05-opcache.ini; configuration for php ZendOpcache module ; priority=05 zend_extension=opcache.so
So ...
1. Is there a good reason to put opcache settings in fpm/php.ini when there is separate config file in fpm/conf.d/05-opcache.ini for it?
2. Or wont be better to put those settings in separate ini file AFTER existing file. For example in 06-opcache.ini. -
I have created a 10-opcache.ini
nano /etc/php/7.0/fpm/conf.d/10-opcache.ini
at the end i addedopcache.enable=1
opcache.enable_cli=1
opcache.interned_strings_buffer=8
opcache.max_accelerated_files=10000
opcache.memory_consumption=128
opcache.save_comments=1
opcache.revalidate_freq=1then
service php7.0-fpm restart
service nginx restartdone
-
-
Hello All,
After I upgraded from OMV3 to OMV4, I struggle to log into OMV web page.
I couldn't find any solution.
So, I start a fresh installation.Ensure you install: redis-server php-redis
This is for OMV4 PHP7 only:
I've spent 40 mins. to found out the issue that many users have 502 Bad Gateway error at the installation process due to the Nginx code.
Change this: fastcgi_pass $socket; to this: fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
Restart your Nginx service: sudo service nginx restart
And try again.I ran into this issue very recently (502 Bad Gateway). I started over with my nextcloud install and could not understand why i suddenly was getting this. the fastcgi_pass was set as fastcgi_pass $socket but the socket variable (above in the /etc/nginx/sites-available/zzz-omv-nginx) was now set to a non-existent .sock file.
I located my sock file (/var/run/php5-fpm.sock;) and set my code to that
Like I said it did work at first, but for some reason when I started over (deleting everything) it broke, as the $socket variable was not set accurately.
Does anyone know why that is?
-
set $socket "unix:/var/run/fpm-xxxxxxxxxxxx.sock
+
fastcgi_pass $socket;should work for OVM4... either a bad gateway error occurs or nginx won't start if there are problems in your conf file. That doesn't have to be related to sock
I'll attach my conf for you to try (spent some time as well till I got it working, afterwards I've found that thread )
Code
Alles anzeigenserver { listen 443 ssl; listen [::]:443 ssl; ssl_certificate /etc/ssl/certs/openmediavault-ebc8f928-92d8-4c17-a344-f2565cb3cb76.crt; ssl_certificate_key /etc/ssl/private/openmediavault-ebc8f928-92d8-4c17-a344-f2565cb3cb76.key; set $root_path "/srv/dev-disk-by-label-hdddata/@Nextcloud/nextcloud"; root $root_path; index index.php; set $socket "unix:/var/run/fpm-bab6bd38-ed2d-41a6-a959-c428f826348a.sock"; access_log /var/log/nginx/d6f706c6-0e3b-46cd-bb1c-c6a6bdc6f48b-access.log; error_log /var/log/nginx/d6f706c6-0e3b-46cd-bb1c-c6a6bdc6f48b-error.log; large_client_header_buffers 4 16k; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; client_max_body_size 10G; # set max upload size fastcgi_buffers 64 4K; rewrite ^/caldav(.*)$ /remote.php/caldav$1 redirect; rewrite ^/carddav(.*)$ /remote.php/carddav$1 redirect; rewrite ^/webdav(.*)$ /remote.php/webdav$1 redirect; error_page 403 /core/templates/403.php; error_page 404 /core/templates/404.php; location = /robots.txt { allow all; log_not_found off; access_log off; } location ~ ^/(data|config|\.ht|db_structure\.xml|README) { deny all; } location / { rewrite ^/.well-known/host-meta /public.php?service=host-meta last; rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json last; rewrite ^/.well-known/carddav /remote.php/carddav/ redirect; rewrite ^/.well-known/caldav /remote.php/caldav/ redirect; rewrite ^(/core/doc/[^\/]+/)$ $1/index.html; try_files $uri $uri/ index.php; } location ~ ^(.+?\.php)(/.*)?$ { try_files $1 = 404; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$1; fastcgi_param PATH_INFO $2; fastcgi_param HTTPS on; fastcgi_pass $socket; } # Optional: set long EXPIRES header on static assets location ~* ^.+\.(jpg|jpeg|gif|bmp|ico|png|css|js|swf)$ { expires 30d; # Optional: Don't log access to assets access_log off; } }
adapt certs path/ and name + root path etc
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!