[Support] Linuxserver.io - Nextcloud

[Greygoose]

On 1/25/2018 at 5:46 PM, CHBMB said:

 

By using the occ terminal command.

You'll need to research what exactly to do, should be in the online Nextcloud server admin manual.

docker exec -it nextcloud bash
cd /config/www/nextcloud/
sudo -u abc php7 occ WHATEVER COMMAND IT IS YOU NEED TO RUN

 

This was spot on, scanning as we speak and it has solved it

 

https://www.c-rieger.de/using-nextclouds-command-line/#vier

 

Thank you

[daniel329]

10 hours ago, DZMM said:

ok, I tried doing this via Let's Encrypt.  I did a bit of googling and I found a config file that 'works' - I can edit docs in Nextcloud, but I can't access the collabora docker at office.mydomain.com although I can via the docker url.  Happy as I can meet the primary objective, but if anyone can explain why config file for office is wrong please I'll be even happier:

server {
	listen 443 ssl;
	server_name office.mydomain.com;

# SSL settings
	ssl_certificate /config/keys/letsencrypt/fullchain.pem;
	ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
	ssl_dhparam /config/nginx/dhparams.pem;
	ssl_protocols TLSv1.2;
	
	ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
	ssl_prefer_server_ciphers on;

	client_max_body_size 0;
	
# static files
	location ^~ /loleaflet {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Host $http_host;
	}

# WOPI discovery URL
	location ^~ /hosting/discovery {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Host $http_host;
	}

# main websocket
	location ~ ^/lool/(.*)/ws$ {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "Upgrade";
		proxy_set_header Host $http_host;
		proxy_read_timeout 36000s;
	}

# download, presentation and image upload
	location ~ ^/lool {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Host $http_host;
	}

# Admin Console websocket
	location ^~ /lool/adminws {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "Upgrade";
		proxy_set_header Host $http_host;
		proxy_read_timeout 36000s;
	}
}

Having the exact same issue. There is also no "office" section in the upper left corner of Nextcloud like usual.

[killeriq]

On 1/28/2018 at 11:51 PM, CHBMB said:

You need to upgrade this manually. personally I always use the terminal.  Link on the first post,

thanks...installed btw there is newer version out ... so instead on 12.0.0 in the link use 12.0.5

[CHBMB]

thanks...installed btw there is newer version out ... so instead on 12.0.0 in the link use 12.0.5

I know, but I can't be bothered to go back and edit that post everytime a new version comes out.

I figure people should be able to work that bit out for themselves...

Sent from my LG-H815 using Tapatalk

[killeriq]

Yeah , sure completely understand

---

Btw any clue about the Android App - have the latest DEV version updating every day, but the autoupload feature is somehow not working....

month or 2 ago was fine...drives me nuts when the pics from mobile are not going to cloud.

I uninstalled the app wiped data...install it again seems its uploading something but ignores pics which were there before app installation.

Cant understand what they are fixing there everyday and not able to get autoupload properly working...

 

 

Thanks

[saarg]

8 minutes ago, killeriq said:

Yeah , sure completely understand

---

Btw any clue about the Android App - have the latest DEV version updating every day, but the autoupload feature is somehow not working....

month or 2 ago was fine...drives me nuts when the pics from mobile are not going to cloud.

I uninstalled the app wiped data...install it again seems its uploading something but ignores pics which were there before app installation.

Cant understand what they are fixing there everyday and not able to get autoupload properly working...

 

 

Thanks

 

Maybe not use the dev version if it doesn't work correctly?

I have no problems with uploads on the normal version.

[killeriq]

6 minutes ago, saarg said:

 

Maybe not use the dev version if it doesn't work correctly?

I have no problems with uploads on the normal version.

normal didnt had autoupload workin at all...but it might change since ive tried last time...will try again, thx

[CHBMB]

I use the playstore version too

Sent from my LG-H815 using Tapatalk

[vanes]

Hello! I ask for help with a strange problem ...
After updating to 12.0.5 nextcloud does not allow the disks to spindown....
this is exactly nextcloud container! I did tests 2 days, with stopped nextcloud container discs spindown as they should!
tried a full reinstallation, but problem still exists

[ebnerjoh]

6 hours ago, vanes said:

Hello! I ask for help with a strange problem ...
After updating to 12.0.5 nextcloud does not allow the disks to spindown....
this is exactly nextcloud container! I did tests 2 days, with stopped nextcloud container discs spindown as they should!
tried a full reinstallation, but problem still exists

 

Hi, 

 

As I read your message I noticed that I have the same issue...

I have 2 disks in my array, nextcloud data is only on one of the two disks and exactly this disk is not spinning down.

 

Br,

Johannes

[vanes]

I will clarify a bit, there was a container with 12.0.4, I updated the nextcloud (not the container) to 12.0.5, the update was successful. Spindown work as it should! Next day  container was updated,   from this moment spindown does not work

Then i completly uninstall nextcloud+mariadb+letsencrypt recreated shares, reinstalled containers - no spindown!  Tried without mariadb (sqlLite) still no spindown.... =(

no spindown on disk with nextcloud share (/mnt/user/nextcloud) and parity...

i think it is container issue, not unraid or nextcloud

Edited February 2, 2018 by vanes

[CHBMB]

I don't, most recent container, Nextcloud 12.0.5, longstanding install.....

All my drives spun down.

Sent from my LG-H815 using Tapatalk

[vanes]

Error

PHP

Narrowing occurred during type inference. Please file a bug report on bugs.php.net at /config/www/nextcloud/lib/composer/composer/ClassLoader.php#444

my nextcloud log full of such messages

this error appears every 15min right after cron jobs

Edited February 3, 2018 by vanes

[levster]

Ever since upgrading to the latest release I have had problems connecting remotely to my Nextcloud. I can log in using a local ip address, but not remotely. I constantly see errors with code integrity check.  I've attached the logs. 

 

nextcloud.log

[CHBMB]

7 hours ago, levster said:

Ever since upgrading to the latest release I have had problems connecting remotely to my Nextcloud. I can log in using a local ip address, but not remotely. I constantly see errors with code integrity check.  I've attached the logs. 

 

nextcloud.log

 

Based on that, all I can say is there must be an error in your config somewhere.  Unless I see your config files, who knows what.  I'd hazard a guess at config.php though.

[CHBMB]

16 hours ago, vanes said:

Error

PHP

Narrowing occurred during type inference. Please file a bug report on bugs.php.net at /config/www/nextcloud/lib/composer/composer/ClassLoader.php#444

my nextcloud log full of such messages

this error appears every 15min right after cron jobs

 

A quick google reveals this is a bug with php

https://github.com/nextcloud/server/issues/7380

[CHBMB]

20 hours ago, vanes said:

I will clarify a bit, there was a container with 12.0.4, I updated the nextcloud (not the container) to 12.0.5, the update was successful. Spindown work as it should! Next day  container was updated,   from this moment spindown does not work

Then i completly uninstall nextcloud+mariadb+letsencrypt recreated shares, reinstalled containers - no spindown!  Tried without mariadb (sqlLite) still no spindown.... =(

no spindown on disk with nextcloud share (/mnt/user/nextcloud) and parity...

i think it is container issue, not unraid or nextcloud

 

I had a thought on this, are you 100% sure it's not a Nextcloud client accessing the server?

[vanes]

18 hours ago, CHBMB said:

I had a thought on this, are you 100% sure it's not a Nextcloud client accessing the server?

100% no clients

 

I decided to start again a second time, deleted everything (share, container, template, appdata folder). Then installed nextcloud container (sqllite)! did not touch any settings, spun down all my disks and began to watch... and now seems that everything fine, disks are not spinning 1 hour... What was the reason I do not understand! the second reinstallation differs from the first one in that I deleted the template. Now i am going to add letsencrypt, will write my result later....

 

I set up letsencrypt, and everything is seems to be fine. Disk with nextcloud spin down as it should. What exactly was the key i don't know =) maybe template.....

 

omg... after nightly mover spindown stopped working again....

Edited February 4, 2018 by vanes

[levster69]

 
Based on that, all I can say is there must be an error in your config somewhere.  Unless I see your config files, who knows what.  I'd hazard a guess at config.php though.

Sorry for a stupid question, but how do I upload the config files? In other words, which ones should I post?

Sent from my SM-G935V using Tapatalk

[CHBMB]

All the ones that are edited in my guide.  Basically config.php and the nextcloud file you create in LetsEncrypt

[levster]

33 minutes ago, CHBMB said:

All the ones that are edited in my guide.  Basically config.php and the nextcloud file you create in LetsEncrypt

I never set up letsEncrypt. I'll dig up the rest. Thank you. 

[levster]

4 hours ago, CHBMB said:

All the ones that are edited in my guide.  Basically config.php and the nextcloud file you create in LetsEncrypt

Here is the config.php from "\\TOWER2\cache\appdata\nextcloud\www\nextcloud\config" with some fileds edited to remove IDs. 

 

Any other file that I need to upload that would be helpful?

 

Thanks,

 

Lev

 

config.php

Edited February 3, 2018 by levster

[CHBMB]

7 minutes ago, levster said:

Here is the config.php from "\\TOWER2\cache\appdata\nextcloud\www\nextcloud\config" with some fileds edited to remove IDs. 

 

Any other file that I need to upload that would be helpful?

 

Thanks,

 

Lev

 

config.php

Check out my guide here and how I've set up config.php

[levster]

8 hours ago, CHBMB said:

Check out my guide here and how I've set up config.php

 

I've added / changed the lines as in your setup guide. Now, when trying to get into WebUI, the following link is used: "https://nextcloud.ddns.net/index.php/login". There is no port specification. The page does not load at all, with the following message:

This site can’t be reached

nextcloud.ddns.net refused to connect.

 

Typing in the local url: https://192.168.1.131:444 redirects to the nextcloud.ddns.net and same message appears.

 

Thanks,

 

Lev

 

PS. Well, after rebooting the server, I can upload to it, but reaching the WebUI is either taking a VERY long time or timing out completely.

 

After adding a port:

 

  'overwrite.cli.url' => 'https://nextcloud.ddns.net',
  'overwritehost' => 'nextcloud.ddns.net:444',

 

I can get into webUI. However, all of the errors / invalid files are still there.

 

Do you think that at this time it would make sense to wipe out the Nextcloud / MariaDB installs and start from fresh? It seems that the upload are going ok, so I'm not sure.

 

config_uploaded2.php

Edited February 4, 2018 by levster

[CHBMB]

4 hours ago, levster said:

 

I've added / changed the lines as in your setup guide. Now, when trying to get into WebUI, the following link is used: "https://nextcloud.ddns.net/index.php/login". There is no port specification. The page does not load at all, with the following message:

This site can’t be reached

nextcloud.ddns.net refused to connect.

 

Typing in the local url: https://192.168.1.131:444 redirects to the nextcloud.ddns.net and same message appears.

 

Thanks,

 

Lev

 

PS. Well, after rebooting the server, I can upload to it, but reaching the WebUI is either taking a VERY long time or timing out completely.

 

After adding a port:

 

  'overwrite.cli.url' => 'https://nextcloud.ddns.net',
  'overwritehost' => 'nextcloud.ddns.net:444',

 

I can get into webUI. However, all of the errors / invalid files are still there.

 

Do you think that at this time it would make sense to wipe out the Nextcloud / MariaDB installs and start from fresh? It seems that the upload are going ok, so I'm not sure.

 

config_uploaded2.php

 

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.