I'm on version 12.0.0 and tried to update to 12.0.5 but got .rnd error. - See error in picture below.

 

Can I delete the .rnd file and try again or how could I overcome this error? Install the update manually is O.K ?

 

Thanks in advance

 

3 minutes ago, truetype said:

I'm on version 12.0.0 and tried to update to 12.0.5 but got .rnd error. - See error in picture below.

 

Can I delete the .rnd file and try again or how could I overcome this error? Install the update manually is O.K ?

 

Thanks in advance

 

 

Yeah I always use the command line version.

14 hours ago, CHBMB said:

 

Problem is, you're trying to do something that I wouldn't really recommend.  Nextcloud comes with a self-signed certificate, and I'm guessing it's a discrepancy about the SSL certs.  Honestly the best option is to get LetsEncrypt running with valid SSL certs and run Nextcloud behind it, like my guide.

 

OK. I think that as with most of things, it's easiest to start with a clean slate and do things correct from the get go. So, I already have a lot of files in my Nextcloud. What is the best way to wipe out Nextcloud / MariaDB, saving all of the files for all of the users, and starting from scratch? I would like to reinstall MariaDB/Nextcloud/LetsEncrypt and then re-add all of my data.

 

Thank you,

 

Lev

Have a look in your Nextcloud data folder (the one you mapped to /data)  copy all the folders that are called $username somewhere safe.

 

Then delete everything else.  (Check and double check what you're deleting of course)

 

So now you should find your Nextcloud folder is empty.

 

Reinstall.  Then when it's all set up, recreate your users in Nextcloud then copy across your old folders, which should restore the files where they need to be.

 

Then the commands below should scan your files back into the Nextcloud database.

 

docker exec -it nextcloud bash

cd /config/www/nextcloud/ sudo -u abc php7 occ files:scan

 

looks like version 13 is out, I've never updated before, will there be an updated docker container or should I attempt to update in app?

looks like version 13 is out, I've never updated before, will there be an updated docker container or should I attempt to update in app?

Need to update manually, suggest using cmd line, see link from first post.

Sent from my LG-H815 using Tapatalk

Update via WebUI went well. Running Nextcloud 13 now :-)

On 2018-02-05 at 12:14 AM, CHBMB said:

 

Yeah I always use the command line version.

 

Thanks CHBMB. Could you please help a fellow out how to update via command line (SSH)?

 

I found this, but it says apache so I suppose that wont work

https://docs.nextcloud.com/server/12/admin_manual/configuration_server/occ_command.html#command-line-upgrade-label

 

EDIT: Sorry, saw the link now in the first post!!

 

Now on version 13.0.0 all working good so far

Edited February 6, 20188 yr by truetype
idiocy

On 2/4/2018 at 8:06 PM, CHBMB said:

Have a look in your Nextcloud data folder (the one you mapped to /data)  copy all the folders that are called $username somewhere safe.

 

Then delete everything else.  (Check and double check what you're deleting of course)

 

So now you should find your Nextcloud folder is empty.

 

Reinstall.  Then when it's all set up, recreate your users in Nextcloud then copy across your old folders, which should restore the files where they need to be.

 

Then the commands below should scan your files back into the Nextcloud database.

 

docker exec -it nextcloud bash

cd /config/www/nextcloud/ sudo -u abc php7 occ files:scan

 

 

I just upgraded to the 13.0.0 and I no longer see the errors that I was seeing on the 12.0.5. I did not get a chance to wipe all and start from scratch. I was planning it for this weekend.

 

I will keep checking for the next few days, but hope it stays this way.

Edited February 7, 20188 yr by levster

 
I just upgraded to the 13.0.0 and I no longer see the errors that I was seeing on the 12.0.5. I did not get a chance to wipe all and start from scratch. I was planning it for this weekend.
 
I will keep checking for the next few days, but hope it stays this way.

That's because@sparklyballs upgraded the php version as Alpine released a new version.

Sent from my LG-H815 using Tapatalk

I followed your guide CHBMB and the WebUI works for me but I've got still some errors like " Exception: The requested uri(/nextcloud/core/img/favicon.ico) cannot be processed by the script '/core/templates/404.php') at /config/www/nextcloud/lib/private/AppFramework/Http/Request.php#733 " and I also can't connect by the desktop client. It's telling me all the time that it can't find the status.php.

5 hours ago, CreZo said:

I followed your guide CHBMB and the WebUI works for me but I've got still some errors like " Exception: The requested uri(/nextcloud/core/img/favicon.ico) cannot be processed by the script '/core/templates/404.php') at /config/www/nextcloud/lib/private/AppFramework/Http/Request.php#733 " and I also can't connect by the desktop client. It's telling me all the time that it can't find the status.php.

 

Sorry but there's nothing there I can make any sense of,  I've installed this over 40 times, and never had any problems, if you can't connect the desktop client, have you tried the mobile client using cellular data NOT using the same network your server is on, could be incorrect configuration of something in your router/firewall.

Hi, just would like to know where i could look for to get following security and setup warnings corrected.

 

happening here when i change from apache reverse proxy to letsencrypt reverse proxy (apache i cant get the ssl certs renewed so i switched to letsencrypt ...)

 

simple reverse rule in letsencrypt

 

    location / {
       auth_basic off;
       allow all; # Allow all to see content 
        include /config/nginx/proxy.conf;
        proxy_pass http://192.168.1.2:447;
    }

 

its all working as it should, bu i get this security warnings while behind apache simple reverse rule theres all good, may a hint where to look for ?

 

following errors inside nextcloud since then

• Der „X-XSS-Protection“-HTTP-Header ist nicht so konfiguriert, dass er „1; mode=block“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
• Der „X-Content-Type-Options“-HTTP-Header ist nicht so konfiguriert, dass er „nosniff“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
• Der „X-Robots-Tag“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
• Der „X-Frame-Options“-HTTP-Header ist nicht so konfiguriert, dass er „SAMEORIGIN“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.

Hello!

I am having issues installing Nexcloud. When I try to open the WEBUI I get HTTP error 500. When I tried opening with a different browser (edge) I got the same page and an arror message "DLG_FLAGS_INVALID_CA
DLG_FLAGS_SEC_CERT_CN_INVALID"
 

Edited February 9, 20188 yr by Prokie

Hello!

I am having issues installing Nexcloud. When I try to open the WEBUI I get HTTP error 500. When I tried opening with a different browser (edge) I got the same page and an arror message "DLG_FLAGS_INVALID_CA
DLG_FLAGS_SEC_CERT_CN_INVALID"
 

Without lot more info, impossible to say

Sent from my LG-H815 using Tapatalk

Hi, just would like to know where i could look for to get following security and setup warnings corrected.
 
happening here when i change from apache reverse proxy to letsencrypt reverse proxy (apache i cant get the ssl certs renewed so i switched to letsencrypt ...)
 
simple reverse rule in letsencrypt
 
    location / {
       auth_basic off;
       allow all; # Allow all to see content 
        include /config/nginx/proxy.conf;
        proxy_pass http://192.168.1.2:447;
    }
 
its all working as it should, bu i get this security warnings while behind apache simple reverse rule theres all good, may a hint where to look for ?
 
following errors inside nextcloud since then

• Der „X-XSS-Protection“-HTTP-Header ist nicht so konfiguriert, dass er „1; mode=block“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
• Der „X-Content-Type-Options“-HTTP-Header ist nicht so konfiguriert, dass er „nosniff“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
• Der „X-Robots-Tag“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
• Der „X-Frame-Options“-HTTP-Header ist nicht so konfiguriert, dass er „SAMEORIGIN“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.

The guide on the linuxserver website demonstrates how to configure the two together

Sent from my LG-H815 using Tapatalk

9 hours ago, CHBMB said:

The guide on the linuxserver website demonstrates how to configure the two together

Sent from my LG-H815 using Tapatalk
 

thanks, errors now gone

 

now for further usage with other sites i check on letsencrypt topic.

On 2018-02-09 at 1:13 PM, CHBMB said:

Without lot more info, impossible to say

Sent from my LG-H815 using Tapatalk
 

What information do you need me to send you?

1 minute ago, Prokie said:

What information do you need me to send you?

 

As much as you can post.  config.php nextcloud file as starters.

 

Basically any file that you edit during the setup and the mariadb docker logs

Edited February 11, 20188 yr by CHBMB

I have been trying to follow the nextcloud setup guide found here:

https://www.linuxserver.io/2016/07/28/installing-nextcloud-on-unraid/

 

I'm not able to get past the nextcloud install portion.

The log shows this:

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
tar: /tmp/nextcloud.tar.bz2: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
cp: cannot create regular file '/config/www/nextcloud/config/config.php': No such file or directory
chown: cannot access '/config/www/nextcloud/config/config.php': No such file or directory
[cont-init.d] 60-memcache: exited 1.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Could not open input file: /config/www/nextcloud/cron.php

Config files are not getting generated.

 

nginx error log shows this:

2018/02/11 22:08:25 [error] 317#317: *2 directory index of "/config/www/nextcloud/" is forbidden, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:08:25 [error] 317#317: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:08:25 [error] 317#317: *2 open() "/config/www/nextcloud/favicon.ico" failed (2: No such file or directory), client: 192.168.1.53, server: _, request: "GET /favicon.ico HTTP/1.1", host: "192.168.1.238:444", referrer: "https://192.168.1.238:444/"
2018/02/11 22:08:25 [error] 317#317: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.53, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:444", referrer: "https://192.168.1.238:444/"
2018/02/11 22:08:28 [error] 317#317: *2 directory index of "/config/www/nextcloud/" is forbidden, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:08:28 [error] 317#317: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:09:43 [error] 317#317: *7 directory index of "/config/www/nextcloud/" is forbidden, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:09:43 [error] 317#317: *7 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:17:51 [error] 317#317: *19 directory index of "/config/www/nextcloud/" is forbidden, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:17:51 [error] 317#317: *19 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:25:47 [error] 316#316: *3 directory index of "/config/www/nextcloud/" is forbidden, client: 172.17.0.1, server: _, request: "GET /nextcloud/ HTTP/1.1", host: "192.168.1.238:443"
2018/02/11 22:25:47 [error] 316#316: *3 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 172.17.0.1, server: _, request: "GET /nextcloud/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:443"
2018/02/11 22:26:02 [error] 316#316: *5 directory index of "/config/www/nextcloud/" is forbidden, client: 172.17.0.1, server: _, request: "GET /nextcloud/ HTTP/1.1", host: "192.168.1.238:443"
2018/02/11 22:26:02 [error] 316#316: *5 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 172.17.0.1, server: _, request: "GET /nextcloud/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:443"
2018/02/11 22:39:03 [error] 314#314: *2 directory index of "/config/www/" is forbidden, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:39:03 [error] 314#314: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:39:14 [error] 313#313: *4 directory index of "/config/www/nextcloud/" is forbidden, client: 172.17.0.1, server: _, request: "GET /nextcloud/ HTTP/1.1", host: "192.168.1.238:443"
2018/02/11 22:39:14 [error] 313#313: *4 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 172.17.0.1, server: _, request: "GET /nextcloud/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:443"
2018/02/11 22:40:00 [error] 314#314: *2 directory index of "/config/www/" is forbidden, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"
2018/02/11 22:40:00 [error] 314#314: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.53, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.238:444", referrer: "http://unraid01.local/Docker"

I tried uninstalling the docker app and reinstalling it, but the results are the same.

I'm not sure what I'm missing.

On 2/11/2018 at 1:32 PM, Prokie said:

What information do you need me to send you?

So I had the http 500 error page as well when I tried to upgrade to 13 via the WebGui.

 

Tried a couple of things, but what fixed it for me was running the upgrade commands via the terminal.

 

See the first page and the upgrade instructions and follow that post, maybe that will work for you as well.

I tried updating this docker but got an error message. Anyone else getting the same error?

Error: Error: image lsiodev/nextcloud:latest not found

Edited February 12, 20188 yr by kamhighway

54 minutes ago, kamhighway said:

I tried updating this docker but got an error message. Anyone else getting the same error?

Error: Error: image lsiodev/nextcloud:latest not found

 

It's a long time since nextcloud was in dev. You need to move to the linuxserver/nextcloud image. 

But I'm not sure if you can just change it and everything works. Check which version of nextcloud you are on and what is the latest. If it's the same, you should be able to replace it by changing the repository. 

Anyway you should take a backup of both nextcloud appdata and the database before doing anything. 

17 hours ago, Snipe3000 said:

I have been trying to follow the nextcloud setup guide found here:

https://www.linuxserver.io/2016/07/28/installing-nextcloud-on-unraid/

 

I'm not able to get past the nextcloud install portion.

The log shows this:

Config files are not getting generated.

 

nginx error log shows this:

I tried uninstalling the docker app and reinstalling it, but the results are the same.

I'm not sure what I'm missing.

 

Based on the post time, I think Snipe3000 and I had this issue at about exactly the same time - finally gave up and went to bed. My Nextcloud log looks identical. I didn't check the nginx logs, but I did take a look in the Unraid filesystem and the /appdata/nextcloud/config folder never got created. This is also a brand new install, for whatever that's worth.

11 hours ago, theDrell said:

So I had the http 500 error page as well when I tried to upgrade to 13 via the WebGui.

 

Tried a couple of things, but what fixed it for me was running the upgrade commands via the terminal.

 

See the first page and the upgrade instructions and follow that post, maybe that will work for you as well.

I tried it, did not help sadly. Thanks anyway!