Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] Linuxserver.io - Nextcloud

Featured Replies

  • Replies 7.1k
  • Views 1.7m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Here's my list of instructions....    Use them at your own risk.....   If upgrading to v12 please see here:   ##Turn on maintenance mode docker exec -it nextcloud occ m

  • When i did enter the docker container with ssh and did run the following command the error message was gone   sudo -u abc php /config/www/nextcloud/occ db:add-missing-indices   Onl

  • gustomucho
    gustomucho

    After tinkering with this for a while, it seems the solution is much simpler than I thought. For some reason, the only step required is to modify the config.php file. No need to install ffmp

Posted Images

hey uldise after you saw that guide do you have any idea where can i add this line, i ben checking online and trying different thinks but i cant get it working

<VirtualHost *:80>
   ServerName cloud.nextcloud.com
   Redirect permanent / https://cloud.nextcloud.com/
</VirtualHost>

thanks

1 hour ago, mata7 said:

hey uldise after you saw that guide do you have any idea where can i add this line, i ben checking online and trying different thinks but i cant get it working


<VirtualHost *:80>
   ServerName cloud.nextcloud.com
   Redirect permanent / https://cloud.nextcloud.com/
</VirtualHost>

thanks

as per guide you are using ngix web server, so correct code will be something like this:

server {
       listen         80;
       server_name    my.domain.com;
       return         301 https://$server_name$request_uri;
}

and per guide you just append to this file at the end:

"In your letsencrypt container "appdata" go to /config/nginx/site-confs/ and create a file called nextcloud containing this code below. Make sure you change server.com to your actual domain name."

Edited by uldise

man thanks for all you help, for some reason is no working, please check if this is right

 

server {
       listen         80;
       server_name    nextcloud.mata7.com;
       return         301 https://$server_name$request_uri;
}

this is what i have and not working the http to https

Edited by mata7

Have you opened port 80 on your router and forwarded it to whatever port your using on the LetsEncrypt docker container?

sorry you mean open port 80 to unraid ip server?

Post your docker run command.  Like this (you can copy and paste the text and edit out your personal info)

UWyrTcL.png

here, thanks for you help

 

 

 

Edited by mata7

So port forward 80 on your router to port 81 on your Unraid box.  Otherwise how else can Nginx respond to http requests and redirect them to https.

wow bingo everything is working now, thank you very much for you help

 

and thanks uldise for all you help to

20 hours ago, mata7 said:
here, thanks for you help
 
 
 

 


I installed the Nextcloud 12 beta3 successfully but there is an error that shows up...

 

https://help.nextcloud.com/t/nextcloud-12-beta-2-php-opcache-is-not-properly-configured/12519/2

Can this docker have the php.ini changed from:

opcache.enable=On
to
opcache.enable=1

This was a change made for the new version but I cannot find the php.ini to change this line?

Any help would be awesome!!

Thanks


Sent from my iPhone using Tapatalk

 

Edited by airbillion

1 hour ago, airbillion said:

Can this docker have the php.ini changed from:

opcache.enable=On
to
opcache.enable=1

 

Not until we update it to V12.

 

php.ini is in the container 

docker exec -it nextcloud bash

Then it's in /etc/php7/

 

Any changes you make won't survive a docker update.  Although you could 

 

cp /etc/php7/php.ini /config/php.ini

Then mount the file in your docker run command/template

 

-v /config/php.ini:/etc/php7/php.ini

 

Edited by CHBMB

 

Not until we update it to V12.

 

php.ini is in the container 

docker exec -it nextcloud bash

Then it's in /etc/php7/

 

Any changes you make won't survive a docker update.  Although you could 

 

 

cp /etc/php7/php.ini /config/php.ini

Then mount the file in your docker run command/template

 

 

 

-v /config/php.ini:/etc/php7/php.ini

 

 

 

Good idea...I'll give that a shot...I forgot that you could mount files in docker...

 

 

Sent from my iPhone using Tapatalk

On ‎12‎.‎05‎.‎2017 at 1:26 PM, Diggewuff said:

I'm having a little problem, but I'm not sure if it is triggered by the container or Next Cloud itself.

I mounted a share (Media) with read and write privileges to the Next Cloud Docker, and bindet it into Next Cloud as Local storage over the External Storage option, granting my own (admin) user Joscha Read and write access.

When I'm adding content e.g. folders or files to that share, the permissons for that folders and files are set to drwxr_xr_x / rwxr_xr_x, owner Nobody, so that only the user Nobody could make changes to those folders and files.

The UnRaid user (joscha) cannot write anyting into that folder or make changes to that file. Deleting them is no problem.

 

Any ideas how to change that behavior?

Does anyone has an idea how to change that behavior?

Edited by Diggewuff

2 hours ago, Diggewuff said:

Does anyone has an idea how to change that behavior?

i think you misunderstand unRAID OS users and unRAID share/smb users.. 

unRAID OS level have user root only, and all files on your shares are writen to Nobody:nogroup.

On 5/11/2017 at 2:50 AM, ufo56 said:

Everything is ok, but when someone downloads file through shared link then download speed is going zero after 1gb or even completely stops.

wget error

 


HTTP request sent, awaiting response... 206 Partial Content

Letsencrypt nginx shows in error log


*3262 upstream prematurely closed connection while reading upstream, client: xx.xx.xx.1xx, server: xxxx.tld,

Using letsencrypt nginx docker proxy and nextcloud.

 

nginx configs

 

https://pastebin.com/RuF2BnRb

 

Anyone ?

Edited by ufo56

Nextcloud docker php did give me this error.

WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

I raised it to 25.

 

Now i get 

 

[18-May-2017 21:44:31] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 5 total children
[18-May-2017 21:44:34] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 6 total children
[18-May-2017 21:44:35] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 7 total children
[18-May-2017 21:44:36] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 8 total children
[18-May-2017 21:44:37] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 9 total children

Raised min/max_spare_servers. Lets see what now...

 

EDIT: Now i don't get that php-fpm error, but download still disconnects after 1,01 GB exactly every time.

 

EDIT2: Only error now what stays is at letsencrypt nginx log. Some reason nextcloud php/nginx closes the connection

upstream prematurely closed connection while reading upstream

 

 

EDIT3: Seems to be answer is here. People who download stops after 1024mb.

 

Add that line in your proxy config (/mnt/user/appdata/letsencrypt/nginx/site-confs/default)

 

location / {
...
proxy_max_temp_file_size 0;
...
}

 

Edited by ufo56

I am having an issue with adding my outgoing email to Nextcloud

 

Gmail, with the correct settings from Google. https://support.google.com/mail/answer/7126229?hl=en

 

I also allowed "Allow less secure apps" in the google account.

 

The error I keep receiving:

 

A problem occurred while sending the email. Please revise your settings. (Error: Failed to authenticate on SMTP server with username "[email protected]" using 1 possible authenticators)

 

 

 

On 18.5.2017 at 11:43 AM, uldise said:

i think you misunderstand unRAID OS users and unRAID share/smb users.. 

unRAID OS level have user root only, and all files on your shares are writen to Nobody:nogroup.

No. I understood that, but folder permissions have to be drwxrwxrwx in order to make ist possible for UnRaid to make them accessable for different share users. NextCloud creates  folders with permission drwxr_xr_x. They have no write permission for group, as the Folders do whitch I create using smb. 

Edited by Diggewuff

Hi.

 

Im quite new at Unraid in general and have found a problem.

I run NextCloud and it worked fine until i updated it from the WebGui, i then read that was a bad idea.

I have removed the docker and installed again but im still stuck in maintenance mode.

 

I also tried to force update Nextcloud and it says its successful but when i try the webgui i get the maintenance mode again.

 

I need help.

Thx.

Hello,

 

I have faced issues with my nextcloud setup. My container runs according the tutorial behind a reverese proxy:

 

This is the entry in my error log:

2017/05/19 23:30:44 [crit] 338#338: *827 open() "/var/lib/nginx/tmp/proxy/8/01/0000000018" failed (13: Permission denied) while reading upstream, client: 87.174.234.100, server: nextcloud.homer-s.my-wan.de, request: "GET /apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b HTTP/1.1", upstream: "https://192.168.100.10:4432/apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b", host: "nextcloud.homer-s.my-wan.de"

2017/05/19 23:30:44 [crit] 338#338: *827 open() "/var/lib/nginx/tmp/proxy/8/01/0000000018" failed (13: Permission denied) while reading upstream, client: 87.174.234.100, server: nextcloud.myserver.de, request: "GET /apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b HTTP/1.1", upstream: "https://192.168.100.10:4432/apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b", host: "nextcloud.myserver.de"

any idea what to do?

 

 

 

 

23 hours ago, Homer-S said:

Hello,

 

I have faced issues with my nextcloud setup. My container runs according the tutorial behind a reverese proxy:

 

This is the entry in my error log:

2017/05/19 23:30:44 [crit] 338#338: *827 open() "/var/lib/nginx/tmp/proxy/8/01/0000000018" failed (13: Permission denied) while reading upstream, client: 87.174.234.100, server: nextcloud.homer-s.my-wan.de, request: "GET /apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b HTTP/1.1", upstream: "https://192.168.100.10:4432/apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b", host: "nextcloud.homer-s.my-wan.de"


2017/05/19 23:30:44 [crit] 338#338: *827 open() "/var/lib/nginx/tmp/proxy/8/01/0000000018" failed (13: Permission denied) while reading upstream, client: 87.174.234.100, server: nextcloud.myserver.de, request: "GET /apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b HTTP/1.1", upstream: "https://192.168.100.10:4432/apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b", host: "nextcloud.myserver.de"

any idea what to do?

 

 

 

 

No, as other than a cryptic error message I have no idea what your issue is.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.