[Support] Linuxserver.io - Nextcloud

[alturismo]

2 hours ago, tallbill said:

Yeah I've tried that and several variants with no luck.  

 

 

1st google hit

 

https://discourse.linuxserver.io/t/nextcloud-reset-admin-password/595

 

and lsio NC uses abc as user

[tallbill]

15 hours ago, alturismo said:

 

1st google hit

 

https://discourse.linuxserver.io/t/nextcloud-reset-admin-password/595

 

and lsio NC uses abc as user

 

I'm not sure why you must be smug about it.  Its a big assumption that I didn't google the problem or try the first several solutions that I found.  Clearly I don't understand the context of all linux commands so its difficult to parse multiple threads on the subject, especially considering that I tried many things already posted.

 

I tried many variants and yes I just discovered the switch to abc and everything worked.

 

So thanks and sorry for the rant.  Just trying to learn.

[Profezor]

Copying files directly into Nextcloud

 

Using Sopaceinvader's video.

I want to move files from a previous install of Nextcloud.

I use the following command, the new install still does not recognise the files or add them even though the command seems to run.

 

sudo -u abc php /config/www/nextcloud/console.php files:scan --all

 

Any ideas or tricks?

Thanks in advance. There are gigs of files to move over.

[CyberMew]

How to solve these kind of "504 Gateway Time-out" issue when using the updater? I have to click Retry many times before it will go through (I am assuming it is getting interrupted and then resuming each time I do Retry). I am now stuck at Create Backup. 

[blaine07]

How to solve these kind of "504 Gateway Time-out" issue when using the updater? I have to click Retry many times before it will go through (I am assuming it is getting interrupted and then resuming each time I do Retry). I am now stuck at Create Backup. 

I would recommend, in future, following the manual update instructions in OP. I’ve never had any success using Nextcloud’s updates. I don’t have recommendations on moving forward from your current state. If you have a functional backup I’d restore and manually upgrade.

[Jessie]

On 4/7/2022 at 4:54 PM, Profezor said:

Copying files directly into Nextcloud

 

Using Sopaceinvader's video.

I want to move files from a previous install of Nextcloud.

I use the following command, the new install still does not recognise the files or add them even though the command seems to run.

 

sudo -u abc php /config/www/nextcloud/console.php files:scan --all

 

Any ideas or tricks?

Thanks in advance. There are gigs of files to move over.

I'm still on a learning curve for this as as well but i've found you need to recreate the users before scan:all will work.. And you can't create the user if the file for that user exists in the store. so I used krusader to rename the file in the store. eg user = test to testa.

Then I created user = test. Then I went back to the store and there is now a new user = test. I then deleted user = test with krusader and renamed testa to test.

Repeat for all other users. (Good luck if you have a hundred of them) Restart then run scan --all

 

I'm sure there must be an elegant way to copy the users over from the old database, but I don't know how to do it.  Seems noone else does either.  I've asked the question numerous times here and the best answer was "I did that not too hard." which of course is no help to anyone.

 

I notice there is a new line in the linuxserver mariadb template which suggests it might merge a database but the documentation is almost non existent, so no idea whether it would do it or what it actually does anyway.

 

 

Edit.  I missed a step. After you recreate the users, you need to log into each one so nextcloud creates the profile. Then you go to krusader and delete the new user and unrename the file you changed earlier.

The usernames are case sensitive so make sure the unrename matches the case of the newly created username

 

Edited April 9, 2022 by Jessie

[Gragorg]

Just updated my nextcloud and had the error pop up.  "Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation ↗. (List of invalid files… / Rescan…)" 

How can I get rid of this?  Rescan doesn't work.    The list of files is below.

 

Technical information ===================== The following list covers which files have failed the integrity check. Please read the previous linked documentation to learn more about the errors and how to fix them. Results ======= - core - INVALID_HASH - core/js/mimetypelist.js Raw output ========== Array ( [core] => Array ( [INVALID_HASH] => Array ( [core/js/mimetypelist.js] => Array ( [expected] => 94195a260a005dac543c3f6aa504f1b28e0078297fe94a4f52f012c16c109f0323eecc9f767d6949f860dfe454625fcaf1dc56f87bb8350975d8f006bbbdf14a [current] => 1b07fb272efa65a10011ed52a6e51260343c5de2a256e1ae49f180173e2b6684ccf90d1af3c19fa97c31d42914866db46e3216883ec0d6a82cec0ad5529e78b1 ) ) ) )

[dius]

I upgraded Nextcloud the other day. I soon discovered that I could no longer reach my Nextcloud service.  I was wondering how I could go about troubleshooting the cause of this issue, because it was working just fine before the upgrade.  I applied another upgrade this morning hoping it would solve the problem, but it still persists.  The log doesn't show any problems, so I'm not sure it has anything to do with the upgrade.

 

Thanks for any pointers or suggestions.

 

I have just noticed that my Collabora server is not working.  I don't know if that could be why I'm not able to reach Nextcloud (I rather doubt it, but thought I'd mention it just in case).

 

Another update: I can reach Nextcloud by directly typing in the IP address of my Unraid server, but not using duckdns, like I used to be able to do.  I'm guessing that it's a problem with the reverse proxy somehow.

Edited April 11, 2022 by dius

[ijuarez]

2 hours ago, dius said:

I upgraded Nextcloud the other day. I soon discovered that I could no longer reach my Nextcloud service.  I was wondering how I could go about troubleshooting the cause of this issue, because it was working just fine before the upgrade.  I applied another upgrade this morning hoping it would solve the problem, but it still persists.  The log doesn't show any problems, so I'm not sure it has anything to do with the upgrade.

 

Thanks for any pointers or suggestions.

 

I have just noticed that my Collabora server is not working.  I don't know if that could be why I'm not able to reach Nextcloud (I rather doubt it, but thought I'd mention it just in case).

 

Another update: I can reach Nextcloud by directly typing in the IP address of my Unraid server, but not using duckdns, like I used to be able to do.  I'm guessing that it's a problem with the reverse proxy somehow.

 

By ip you mean inside your network, not from the internet?

If its on the outside what page do you get when it does not come up?

Have you checked your duck DNS setup?

[CyberMew]

On 4/9/2022 at 6:00 AM, blaine07 said:

I would recommend, in future, following the manual update instructions in OP. I’ve never had any success using Nextcloud’s updates. I don’t have recommendations on moving forward from your current state. If you have a functional backup I’d restore and manually upgrade.

Thanks. Do you mean do method 3 (fully manually)? Method 1 and 2 seems to give me issues. Either file missing or unable to remove folders in the later stages progress of the updater, very poor QC.

[dius]

5 minutes ago, ijuarez said:

 

By ip you mean inside your network, not from the internet?

If its on the outside what page do you get when it does not come up?

Have you checked your duck DNS setup?

Yes - using the local IP address of my server - I'm currently on the same network.

 

However - just about 15 minutes ago, it started to work - I can now reach it remotely.  I have no idea why, or what was wrong. I still can't get my Collarbora server to start though.  I get a strange error logged when I try start it:

 

--------------------------- Log snippet below ----------------------------

Generating RSA private key, 2048 bit long modulus (2 primes)
.............................................................................................+++++
...................+++++
e is 65537 (0x010001)
Signature ok
subject=C = DE, ST = BW, L = Stuttgart, O = Dummy Authority, CN = localhost
Getting CA Private Key
-e ERR: Use of domain variable is not supported. First host/domain who tries to connect to COOL is always allowed.
To allow multiple host and its aliases use something like this and pass it as env variable:
aliasgroup1=https://domain1:443,https://its-alias|its-second-alias:443
aliasgroup2=https://domain2:443,https://its-alias:443
For more info: https://sdk.collaboraonline.com/docs/installation/CODE_Docker_image.html

----------------------- End log snippet -----------------------------------

 

This is all I get each time I try to start it.  I realize this is not the correct forum to try solve this problem, so feel free to point me where I need to go.  

 

Thanks.

[nug]

9 hours ago, dius said:

--------------------------- Log snippet below ----------------------------

Generating RSA private key, 2048 bit long modulus (2 primes)
.............................................................................................+++++
...................+++++
e is 65537 (0x010001)
Signature ok
subject=C = DE, ST = BW, L = Stuttgart, O = Dummy Authority, CN = localhost
Getting CA Private Key
-e ERR: Use of domain variable is not supported. First host/domain who tries to connect to COOL is always allowed.
To allow multiple host and its aliases use something like this and pass it as env variable:
aliasgroup1=https://domain1:443,https://its-alias|its-second-alias:443
aliasgroup2=https://domain2:443,https://its-alias:443
For more info: https://sdk.collaboraonline.com/docs/installation/CODE_Docker_image.html

----------------------- End log snippet -----------------------------------

 

This is all I get each time I try to start it.  I realize this is not the correct forum to try solve this problem, so feel free to point me where I need to go.  

 

Thanks.

 

I came here looking to solve this exact same issue as well. This started a few days ago when I updated the Nextcloud docker container.

Edited April 12, 2022 by nug

[Tolete]

16 hours ago, dius said:

Yes - using the local IP address of my server - I'm currently on the same network.

 

However - just about 15 minutes ago, it started to work - I can now reach it remotely.  I have no idea why, or what was wrong. I still can't get my Collarbora server to start though.  I get a strange error logged when I try start it:

 

--------------------------- Log snippet below ----------------------------

Generating RSA private key, 2048 bit long modulus (2 primes)
.............................................................................................+++++
...................+++++
e is 65537 (0x010001)
Signature ok
subject=C = DE, ST = BW, L = Stuttgart, O = Dummy Authority, CN = localhost
Getting CA Private Key
-e ERR: Use of domain variable is not supported. First host/domain who tries to connect to COOL is always allowed.
To allow multiple host and its aliases use something like this and pass it as env variable:
aliasgroup1=https://domain1:443,https://its-alias|its-second-alias:443
aliasgroup2=https://domain2:443,https://its-alias:443
For more info: https://sdk.collaboraonline.com/docs/installation/CODE_Docker_image.html

----------------------- End log snippet -----------------------------------

 

This is all I get each time I try to start it.  I realize this is not the correct forum to try solve this problem, so feel free to point me where I need to go.  

 

Thanks.

 

 

collabora/nextcloud office docs was working, after updating (Collabora) log shows.

 

 

ERR: Use of domain variable is not supported. First host/domain who tries to connect to COOL is always allowed.
To allow multiple host and its aliases use something like this and pass it as env variable:
aliasgroup1=https://domain1:443,https://its-alias|its-second-alias:443
aliasgroup2=https://domain2:443,https://its-alias:443
https://sdk.collaboraonline.com/docs/installation/CODE_Docker_image.html

 

looks like  some changes on last update that affect the allowed domains/alliasnames

 

 

-going back to previous version (Collabora) gets you back online (w/nextcloud no longer connecting to collabora server).

-staying in latest (Collabora) and leaving "Container Variable: domain" empty starts the container (w/nextcloud 'Could not establish connection to the Collabora Online server.')

 

My nextcloud instance is running. just not playing nice with Collabora right now.

 

 

anyone figured out the new required variable syntax, to get Collabora back up and running w/nextcloud?

 

[Autchirion]

On 1/30/2021 at 10:02 PM, skois said:

I haven't done any benchmarks, i just selected model 4 because from the comparison chart on developers github seems the best.

haven't tried to do any GPU passthrough, but i would like to, i'm gonna try maybe next week!
Right now i'm planning some down time, moving server to rack and whole network!

I was planning also to create a docker with pdlib, but once pdlib goes to stable alpine, LSIO said will include it.
Right now only if i update the docker or change something needs to reinstall ( i have done some updates to the install script, to check if it is instailled before install it)

Here is the updated script

#!/bin/bash
#FLAG="/config/firstbook.log"
FLAG="/usr/lib/php7/modules/pdlib.so"
if [ ! -f $FLAG ]; then
  apk add --no-cache --upgrade make cmake gcc g++ php7-dev libx11-dev openblas-dev re2c

  rm -rf dlib pdlib
  git clone https://github.com/davisking/dlib.git
  cd dlib/dlib
  mkdir build
  cd build
  cmake -DBUILD_SHARED_LIBS=ON ..
  make
  sudo make install

  cd /

  git clone https://github.com/goodspb/pdlib.git
  cd pdlib
  phpize
  PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig ./configure
  make
  sudo make install
  rm -rf /dlib /pdlib
#  touch $FLAG
else
  echo "Already run of 1st boot. Delete /config/firstboot.log to run again on next boot"
fi

 

Thank you for this, unfortunately this came relevant again after this script doesn't work any more. I took the liberty of posting your script on github.

apk update
apk add --upgrade -X http://dl-cdn.alpinelinux.org/alpine/edge/testing php7-pdlib
apk add bzip2-dev

 

[blaine07]

What version of Nextcloud and Collabora are you all seeing this on? My Collabora is quite a few versions behind because every update had issues…

Instructions you guys post say add ENV variable(to Collabora container) with host of where Nextcloud would live. Has anyone tried doing what it says?

[blaine07]

I don’t think I have this fully correct but if I’m reading right…it would look something like this.

Take pictures of your current setup so you can roll back— I am NOT confident I have the “key” right in ENV VARIABLE.

Domain variable isn’t used/goes away. You’d delete this variable:




Then you would ADD this with the domain of your Nextcloud server:


Then you’d be able to upgrade to new version of Collabora. I’m still on 21.11.2.4.1 here; if I get time later I’ll play with above.

Edited April 13, 2022 by blaine07

[Tolete]

took a second look at this got it up and running.

 

steps i took--

reinstall/enable 'Nextcloud Office' (5.0.3) app.

 

 

Collabora (default/latest)- 

 

edit container and remove the 'Domain' Variable.

add  new Variable

 

save.

 

in NginxProxyManager-

specify https protocol and the server host/ip and port 9980. Also enable Websockets Support.

On the SSL tab select a new certificate, enable HTTP/2.

 

On the Advanced tab, enter:

# static files
location ^~ /loleaflet {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# WOPI discovery URL
location ^~ /hosting/discovery {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# main websocket
location ~ ^/lool/(.*)/ws$ {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

# download, presentation and image upload
location ~ ^/lool {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# Admin Console websocket
location ^~ /lool/adminws {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

save and test.

Edited April 14, 2022 by Tolete
updated proxy

[blaine07]

15 minutes ago, Tolete said:

took a second look at this got it up and running.

 

steps i took--

 

reinstall/enable 'Nextcloud Office' (5.0.3) app.

 

 

Collabora (latest)- 

edit container and remove the 'Domain' Variable.

add  new Variable

save.

 

in NginxProxyManager-

specify https protocol and the server host/ip and port 9980. Also enable Websockets Support.

On the SSL tab select a new certificate, enable HTTP/2.

 

On the Advanced tab, enter:

# static files
location ^~ /loleaflet {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# WOPI discovery URL
location ^~ /hosting/discovery {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# main websocket
location ~ ^/lool/(.*)/ws$ {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

# download, presentation and image upload
location ~ ^/lool {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# Admin Console websocket
location ^~ /lool/adminws {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

 

save and test.

Is that with “latest” version of Collabora? Thank you!

[Tolete]

43 minutes ago, blaine07 said:

Is that with “latest” version of Collabora? Thank you!

 

58 minutes ago, Tolete said:

Collabora (latest)- 

[dius]

2 hours ago, Tolete said:

in NginxProxyManager-

specify https protocol and the server host/ip and port 9980. Also enable Websockets Support.

On the SSL tab select a new certificate, enable HTTP/2.

I'm not the sharpest knife in the drawer, so forgive my ignorance, but how do you get to this NginxProxyManager?  I'm running swag on my unraid server, which incorporates Nginx, but I have never seen the interface you show in your post.

[ijuarez]

1 minute ago, dius said:

I'm not the sharpest knife in the drawer, so forgive my ignorance, but how do you get to this NginxProxyManager?  I'm running swag on my unraid server, which incorporates Nginx, but I have never seen the interface you show in your post.

NPM is a different reverse proxy manger

 

so is traefik.

[blaine07]

3 hours ago, Tolete said:

took a second look at this got it up and running.

 
steps i took--
 
reinstall/enable 'Nextcloud Office' (5.0.3) app.
 

 
Collabora (latest)- 
edit container and remove the 'Domain' Variable.
add  new Variable

save.
 
in NginxProxyManager-
specify https protocol and the server host/ip and port 9980. Also enable Websockets Support.
On the SSL tab select a new certificate, enable HTTP/2.

 
On the Advanced tab, enter:

# static fileslocation ^~ /loleaflet { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# WOPI discovery URLlocation ^~ /hosting/discovery { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# main websocketlocation ~ ^/lool/(.*)/ws$ { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host; proxy_read_timeout 36000s;}# download, presentation and image uploadlocation ~ ^/lool { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# Admin Console websocketlocation ^~ /lool/adminws { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host; proxy_read_timeout 36000s;}

 

 
save and test.

Your pic shows “alliasgroup1”

Should it be as shown or “aliasgroup1” with ONE “l”?

 

edit: weird it only does work with TWO “l”. I don’t understand; I don’t see it expressed as anywhere with “alliasgroup” so don’t understand why that works. 🤦🏼‍♂️

Edited April 13, 2022 by blaine07
I dumb

[Tolete]

46 minutes ago, blaine07 said:

Your pic shows “alliasgroup1”

Should it be as shown or “aliasgroup1” with ONE “l”?

 

edit: weird it only does work with TWO “l”. I don’t understand; I don’t see it expressed as anywhere with “alliasgroup” so don’t understand why that works. 🤦🏼‍♂️

 

i have updated pic/post

 

documentation says/pic show 'aliasgroup1' the '|' in pic is just the cursor.

[blaine07]

Also, does anyone know where admin resides now? Can't seem to find it?

 

It used to be at "https://[IP]:[PORT:9980]/loleaflet/dist/admin/admin.html"

 

Now that 404s?

[blaine07]

Just now, Tolete said:

 

i have updated pic/post

 

documentation says/pic show 'aliasgroup1' the '|' in pic is just the cursor.

It didn't work for me with just one "l" but does with two? I dont understand lol