[Support] Linuxserver.io - Nextcloud


Recommended Posts

17 hours ago, skois said:

Your photos seems to either be deleted on not shared publicly!
Probably on your config you have an 'overwritehost' => nc.example.com 
This rewrites every request even from a local ip to the public domain.
Remove this line and add your local ip subnet or pc specific to your trusted domains. (see the previous post)

Thanks for your help skols. I fixed the images above. Seems like i embedded them wrong.

 

I tried what you said and now it works on my lan but not via wan. Is this just how this configuration works where unless your router supports hairpinning the right way you either get internal or external use? It seems like i should be able to create an exception where if i approach swag using an internal ip address i get directed to the 192.168.XXX.XXX:444 address and via the external route (or router IP?) get the nextcloud.example.com. Though maybe i am just defining hairpinning in a different way. :D

 

Again thanks for helping some random guy on the internet out.

Link to comment
7 hours ago, MadOne627 said:

Thanks for your help skols. I fixed the images above. Seems like i embedded them wrong.

 

I tried what you said and now it works on my lan but not via wan. Is this just how this configuration works where unless your router supports hairpinning the right way you either get internal or external use? It seems like i should be able to create an exception where if i approach swag using an internal ip address i get directed to the 192.168.XXX.XXX:444 address and via the external route (or router IP?) get the nextcloud.example.com. Though maybe i am just defining hairpinning in a different way. :D

 

Again thanks for helping some random guy on the internet out.

Try changing 

'overwrite.cli.url' => 'https://internal_ip:webui_port

and also on your config i see you have two 'overwritehost',

delete one and comment the other.

  • Thanks 1
Link to comment
On 1/12/2021 at 3:21 AM, skois said:

If we assume your lan pc is on the same subnet and your subnet is 10.0.0.0/24, then on your config.php on nc add this on the trusted domains.
It should work now



  'trusted_domains' => 
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),

 

Thanks for your help! Gave this a shot but no go. I stopped the nc docker, updated the config.php file using krusader and confirmed that I had the changes saved. Then started up the nc container which brought me back to the initial set up page. I entered all the details as before and ended up back at the Internal server error page. Looking at the config.php file I see that my entry has been removed and it's back the way it was now.

 

Should I be using nano or a command line based editor instead? I've attached a new log file and the config.php as it was edited, before being reset.

 

Thank your for your time skois! I'm sure you're very busy and I appreciate your help.

 

Edit: I've got wireguard installed, is that causing a problem?

nextcloud.log config.php

Edited by blakeslade
Wireguard
Link to comment

Hi @linuxserver.io

 

I have recently been using Nextcloud with MariaDB on one of my servers and just wanted to move it to the other for my reverse proxy

 

i used cp -arv command to move the appdata folders of nextcloud and mariadb

 

both unraid server use same root password and profiles

 

i copied using same command all the next cloud /data from old server to new and mirrored the /mnt/user/nextcloud set up as it was on the original server

 

 

****Edit

found that i missed the updated server IP for both Nextcloud and MariaDB in the config.php file its working now

Edited by Can0n
Link to comment
25 minutes ago, blakeslade said:

Thanks for your help! Gave this a shot but no go. I stopped the nc docker, updated the config.php file using krusader and confirmed that I had the changes saved. Then started up the nc container which brought me back to the initial set up page. I entered all the details as before and ended up back at the Internal server error page. Looking at the config.php file I see that my entry has been removed and it's back the way it was now.

 

Should I be using nano or a command line based editor instead? I've attached a new log file and the config.php as it was edited, before being reset.

 

Thank your for your time skois! I'm sure you're very busy and I appreciate your help.

nextcloud.log 160.03 kB · 0 downloads config.php 653 B · 0 downloads

The Answer is yes use nano or

this worked on my system

open up the shell for nexcloud

cd /config/www/nextcloud

pwd

should show ":/config/www/nextcloud#"

copy and paste

occ config:system:set trusted_domains 1 --value=192.168.1.*

change your ip to the one you need ... Did this from memory hope it works and helps you out

 

Link to comment
22 minutes ago, John Graham said:

The Answer is yes use nano or

this worked on my system

open up the shell for nexcloud

cd /config/www/nextcloud

pwd

should show ":/config/www/nextcloud#"

copy and paste

occ config:system:set trusted_domains 1 --value=192.168.1.*

change your ip to the one you need ... Did this from memory hope it works and helps you out

 

So nextcloud is still stuck in the inital setup phase. It's stuck there. Every time I open the WebGUI it's asking me for an admin user and pw along with db options.

 

When I open a shell to "/config/www/nextcloud" this is what I get:

 

occ config:system:set trusted_domains 1 --value=10.0.0.*


Nextcloud is not installed - only a limited number of commands are available

There are no commands defined in the "config:system" namespace.
 

At this point I've tried a few times and am running out of user names since it seems to save the ones I've tried in the past (lots of admin variations)?

 

Thanks again!

Link to comment
2 hours ago, blakeslade said:

So nextcloud is still stuck in the inital setup phase. It's stuck there. Every time I open the WebGUI it's asking me for an admin user and pw along with db options.

 

When I open a shell to "/config/www/nextcloud" this is what I get:

 

occ config:system:set trusted_domains 1 --value=10.0.0.*


Nextcloud is not installed - only a limited number of commands are available

There are no commands defined in the "config:system" namespace.
 

At this point I've tried a few times and am running out of user names since it seems to save the ones I've tried in the past (lots of admin variations)?

 

Thanks again!

If this is a new installation and you don't have any data, i would suggest delete appdata from both database and nextcloud and force update both dockers (open advanced view on docker tab). and start fresh.
That means you have to recreate the databases (check spaceinvaders video for the commands).
Something wasn't completed correctly on the 1st install and now it seems to fail every time.
Also before starting the initial setup (after wiping appdata and forcing update the dockers) 
Add the trusted domain.
  'trusted_domains' => 
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),

Link to comment
16 minutes ago, skois said:

If this is a new installation and you don't have any data, i would suggest delete appdata from both database and nextcloud and force update both dockers (open advanced view on docker tab). and start fresh.
That means you have to recreate the databases (check spaceinvaders video for the commands).
Something wasn't completed correctly on the 1st install and now it seems to fail every time.
Also before starting the initial setup (after wiping appdata and forcing update the dockers) 
Add the trusted domain.
  'trusted_domains' => 
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),

Thanks ton skois, I'll give that a go this afternoon.

 

I'm not currently using a cache drive, so my appdata is located at: /mnt/user/appdata

 

That's the only place I need to delete the data?

Link to comment
Thanks ton skois, I'll give that a go this afternoon.
 
I'm not currently using a cache drive, so my appdata is located at: /mnt/user/appdata
 
That's the only place I need to delete the data?
Correct!
Actually /mnt/user contains both data cache and array, depending on the share configuration

Sent from my Mi 10 Pro using Tapatalk

Link to comment
22 minutes ago, skois said:

Correct!
Actually /mnt/user contains both data cache and array, depending on the share configuration

Sent from my Mi 10 Pro using Tapatalk
 

Getting a 504 Gateway time out error now. I feel like this is a comedy of errors on my end.

 

Here are the commands I entered for mariadb:

 

mysql -uroot -p
password

create user 'nextcloud' identified by 'mypassword';

create database if not exists nextcloud;

grant all privileges on nextcloud.* to 'nextcloud' identified by 'mypassword';

 

I used nano for the config.php file, which looked like this before opening the nc webui:

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'trusted_domains' =>
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),
  );

 

Now the config.php looks like this (after the 504 timeout):

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'trusted_domains' =>
  array (
    0 => '10.0.0.72:444',
  ),
  'instanceid' => 'ocj51yowyofq',
  'passwordsalt' => 'MrmUOLhtq7TnzskZxDQePo8gChclH+',
  'secret' => 'Ee5QoOEXhdGDvIzD61ogzdx4g53tXVsCe6RB2eddED4DnWzI',
  'dbtype' => 'mysql',
  'version' => '20.0.4.0',
  'overwrite.cli.url' => 'https://10.0.0.72:444',
  'dbname' => 'nextcloud',
  'dbhost' => '10.0.0.72:444',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
);

 

I've attached an updated nextcloud.log from the /data folder (on my array /mnt/user/Nextcloud) and docker page logs.

 

Ideas?

 

nextcloud.log Nextcloud_Log_2021.01.13.txt Mariadb_log_2021.01.13.txt

Link to comment
18 hours ago, skois said:

Try changing 

'overwrite.cli.url' => 'https://internal_ip:webui_port

and also on your config i see you have two 'overwritehost',

delete one and comment the other.

Thats it. I can now get to it internally with the LAN IP:Port and can get to it via web address via WAN. Thanks for your guidance skols!

  • Like 1
Link to comment
15 hours ago, blakeslade said:

Getting a 504 Gateway time out error now. I feel like this is a comedy of errors on my end.

 

Here are the commands I entered for mariadb:

 

mysql -uroot -p
password

create user 'nextcloud' identified by 'mypassword';

create database if not exists nextcloud;

grant all privileges on nextcloud.* to 'nextcloud' identified by 'mypassword';

 

I used nano for the config.php file, which looked like this before opening the nc webui:

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'trusted_domains' =>
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),
  );

 

Now the config.php looks like this (after the 504 timeout):

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'trusted_domains' =>
  array (
    0 => '10.0.0.72:444',
  ),
  'instanceid' => 'ocj51yowyofq',
  'passwordsalt' => 'MrmUOLhtq7TnzskZxDQePo8gChclH+',
  'secret' => 'Ee5QoOEXhdGDvIzD61ogzdx4g53tXVsCe6RB2eddED4DnWzI',
  'dbtype' => 'mysql',
  'version' => '20.0.4.0',
  'overwrite.cli.url' => 'https://10.0.0.72:444',
  'dbname' => 'nextcloud',
  'dbhost' => '10.0.0.72:444',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
);

 

I've attached an updated nextcloud.log from the /data folder (on my array /mnt/user/Nextcloud) and docker page logs.

 

Ideas?

 

nextcloud.log 209.29 kB · 0 downloads Nextcloud_Log_2021.01.13.txt 1.77 kB · 0 downloads Mariadb_log_2021.01.13.txt 5.54 kB · 0 downloads

I was able to reproduce, something after the install is messing up the trusted domains.
So lets do it all over again.
go to 

- /mnt/user/appdata/nextcloud  - delete everything there.

- /mnt/user/appdata/mariadb - delete everything there.

- /mnt/user/nextcloud - delete everything there *if you have DATA there, back them up first*(this is the /data folder, i suggest cleaning because i saw before you created a bunch of admins and there will be a lot of files assosiated with them there that you wont need.)

 

Ok, now delete both dockers 

- mariadb

- nextcloud

 

* Go to Apps.
* Install mariadb (check that is on bridge network for now)

* Open console

 

mysql -uroot -p
password

create user 'dbusernextcloud' identified by 'mypassword';

create database if not exists nextclouddb;

grant all privileges on nextclouddb.* to 'dbusernextcloud' identified by 'mypassword';

* Close console.

* Go to Apps

* Install nextcloud (check that is on bridge network for now)
* Open WebUI (if it opens, do the initial setup)

- database user: dbusernextcloud

- database password: mypassword

- database name: nextclouddb

- localhost: unraidip:portofmariadb

fill also username and password for admin.
*Click Finish Setup. (DONT CLOSE PAGE on 504 error)

*With the page still displaying 504 error, go to /mnt/user/appdata/nextcloud/www/nextcloud/config/ and edit the config.php

truested_domain section should look like this (dont forget the comma after each entry). ofc change the ips according to yours.
You should only need to add the line 1, 0 should be there.


  'trusted_domains' => 
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),


*After saving the config.php. Go back to your browser and refresh the page. It should now ask you to log in. 

In case still shows 504 error. Try restarting docker WITHOUT CLOSING the page. and when docker restarts, refresh the page once more.


Hopefully this will get you started!

 

  • Like 1
Link to comment
4 hours ago, skois said:

I was able to reproduce, something after the install is messing up the trusted domains.
So lets do it all over again.
go to 

- /mnt/user/appdata/nextcloud  - delete everything there.

- /mnt/user/appdata/mariadb - delete everything there.

- /mnt/user/nextcloud - delete everything there *if you have DATA there, back them up first*(this is the /data folder, i suggest cleaning because i saw before you created a bunch of admins and there will be a lot of files assosiated with them there that you wont need.)

 

Ok, now delete both dockers 

- mariadb

- nextcloud

 

* Go to Apps.
* Install mariadb (check that is on bridge network for now)

* Open console

 


mysql -uroot -p
password

create user 'dbusernextcloud' identified by 'mypassword';

create database if not exists nextclouddb;

grant all privileges on nextclouddb.* to 'dbusernextcloud' identified by 'mypassword';

* Close console.

* Go to Apps

* Install nextcloud (check that is on bridge network for now)
* Open WebUI (if it opens, do the initial setup)

- database user: dbusernextcloud

- database password: mypassword

- database name: nextclouddb

- localhost: unraidip:portofmariadb

fill also username and password for admin.
*Click Finish Setup. (DONT CLOSE PAGE on 504 error)

*With the page still displaying 504 error, go to /mnt/user/appdata/nextcloud/www/nextcloud/config/ and edit the config.php

truested_domain section should look like this (dont forget the comma after each entry). ofc change the ips according to yours.
You should only need to add the line 1, 0 should be there.


  'trusted_domains' => 
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),


*After saving the config.php. Go back to your browser and refresh the page. It should now ask you to log in. 

In case still shows 504 error. Try restarting docker WITHOUT CLOSING the page. and when docker restarts, refresh the page once more.


Hopefully this will get you started!

 

I say hot damn! I am floored by your steps. Thank you so much skois! I will get on this later today, and report my results.

Link to comment
On 1/14/2021 at 7:23 AM, skois said:

I was able to reproduce, something after the install is messing up the trusted domains.
So lets do it all over again.
go to 

- /mnt/user/appdata/nextcloud  - delete everything there.

- /mnt/user/appdata/mariadb - delete everything there.

- /mnt/user/nextcloud - delete everything there *if you have DATA there, back them up first*(this is the /data folder, i suggest cleaning because i saw before you created a bunch of admins and there will be a lot of files assosiated with them there that you wont need.)

 

Ok, now delete both dockers 

- mariadb

- nextcloud

 

* Go to Apps.
* Install mariadb (check that is on bridge network for now)

* Open console

 


mysql -uroot -p
password

create user 'dbusernextcloud' identified by 'mypassword';

create database if not exists nextclouddb;

grant all privileges on nextclouddb.* to 'dbusernextcloud' identified by 'mypassword';

* Close console.

* Go to Apps

* Install nextcloud (check that is on bridge network for now)
* Open WebUI (if it opens, do the initial setup)

- database user: dbusernextcloud

- database password: mypassword

- database name: nextclouddb

- localhost: unraidip:portofmariadb

fill also username and password for admin.
*Click Finish Setup. (DONT CLOSE PAGE on 504 error)

*With the page still displaying 504 error, go to /mnt/user/appdata/nextcloud/www/nextcloud/config/ and edit the config.php

truested_domain section should look like this (dont forget the comma after each entry). ofc change the ips according to yours.
You should only need to add the line 1, 0 should be there.


  'trusted_domains' => 
  array (
    0 => '10.0.0.72:444',
    1 => '10.0.0.*',
  ),


*After saving the config.php. Go back to your browser and refresh the page. It should now ask you to log in. 

In case still shows 504 error. Try restarting docker WITHOUT CLOSING the page. and when docker restarts, refresh the page once more.


Hopefully this will get you started!

 

Thank you skois! I now have nc up and running!

 

I'm amazed that you were able to recreate my issue and state the work around so easily. Thank you for taking the time to help me out. I really appreciate it.

 

I'm going to continue the setup process here, with letsencrypt (after I get letsencrypt installed using spaceinvaderone's instructions).

 

Is there another resource that will be helpful to me?

Link to comment

Currently updating from version 18 via the dockerterminal to version 20.

 

Whilst hopping from 19.0.7 to 20.0.5 the updater gets stuck at the following point:

2021-01-16T14:33:34+00:00 Checked for update of app "calendar" in appstore 
2021-01-16T14:33:34+00:00 Repair step: Update name of the stored view
2021-01-16T14:33:34+00:00 Checking for update of app files_accesscontrol in appstore
2021-01-16T14:33:34+00:00 Update app files_accesscontrol from appstore
2021-01-16T14:33:36+00:00 Checked for update of app "files_accesscontrol" in appstore 
2021-01-16T14:33:40+00:00 Repair step: Repair MySQL collation
2021-01-16T14:33:40+00:00 Repair info: All tables already have the correct collation -> nothing to do
2021-01-16T14:33:40+00:00 Repair step: Repair mime types
2021-01-16T14:46:21+00:00 Doctrine\DBAL\Exception\DriverException: An exception occurred while executing 'UPDATE `oc_filecache` SET `mimetype` = ? WHERE (`mimetype` <> ?) AND (`mimetype` <> ?) AND (`name`  COLLATE utf8mb4_general_ci LIKE ?)' with params [19, 19, 2, "%.ott"]:

SQLSTATE[HY000]: General error: 1206 The total number of locks exceeds the lock table size
2021-01-16T14:46:21+00:00 Update failed
2021-01-16T14:46:21+00:00 Maintenance mode is kept active
2021-01-16T14:46:21+00:00 Resetting log level

 

This appears to be a database issue relating to MariaDB.

 

Any ideas of how to fix this would be much appreciated.

Link to comment
2 hours ago, blakeslade said:

Thank you skois! I now have nc up and running!

 

I'm amazed that you were able to recreate my issue and state the work around so easily. Thank you for taking the time to help me out. I really appreciate it.

 

I'm going to continue the setup process here, with letsencrypt (after I get letsencrypt installed using spaceinvaderone's instructions).

 

Is there another resource that will be helpful to me?

I would suggest also looking on this also. Letsncrypt docker was moved to SWAG. It have some small changes to note.
But can't tell you more, because i don't use it.

You might wanna take a look on NginxProxyManager, is a GUI for letsncrypt and nginx. I'm happy with it!

 

  • Like 1
Link to comment
3 minutes ago, Ntouchable said:

Currently updating from version 18 via the dockerterminal to version 20.

 

Whilst hopping from 19.0.7 to 20.0.5 the updater gets stuck at the following point:


2021-01-16T14:33:34+00:00 Checked for update of app "calendar" in appstore 
2021-01-16T14:33:34+00:00 Repair step: Update name of the stored view
2021-01-16T14:33:34+00:00 Checking for update of app files_accesscontrol in appstore
2021-01-16T14:33:34+00:00 Update app files_accesscontrol from appstore
2021-01-16T14:33:36+00:00 Checked for update of app "files_accesscontrol" in appstore 
2021-01-16T14:33:40+00:00 Repair step: Repair MySQL collation
2021-01-16T14:33:40+00:00 Repair info: All tables already have the correct collation -> nothing to do
2021-01-16T14:33:40+00:00 Repair step: Repair mime types
2021-01-16T14:46:21+00:00 Doctrine\DBAL\Exception\DriverException: An exception occurred while executing 'UPDATE `oc_filecache` SET `mimetype` = ? WHERE (`mimetype` <> ?) AND (`mimetype` <> ?) AND (`name`  COLLATE utf8mb4_general_ci LIKE ?)' with params [19, 19, 2, "%.ott"]:

SQLSTATE[HY000]: General error: 1206 The total number of locks exceeds the lock table size
2021-01-16T14:46:21+00:00 Update failed
2021-01-16T14:46:21+00:00 Maintenance mode is kept active
2021-01-16T14:46:21+00:00 Resetting log level

 

This appears to be a database issue relating to MariaDB.

 

Any ideas of how to fix this would be much appreciated.

Access the console of the nextcloud docker. 
Try running. "updater.phar"
If this errors out, do "occ maintenance:mode --off" and try accessing nextcloud webui, go to Settings->Overview and see if there is any errors, (probably should be) errors will probably be about missing things on DB. there you will also see the commands you need to run to fix them. (run them on the nextcloud docker console.
Then try again to update either from WebUI or from console with "updater.phar"

 

Link to comment
On 1/8/2021 at 8:56 AM, BrunoVic said:

I tell you what when I have time I will investigate this and find out what is going on. I might have to source some Nextcloud forums to figure this out. Clearly they don't want to help us out here because we are entitled according to skois. Once I figure this out I will do a technical write up on what I did to resolve this problem.

@BrunoVic@jmial  I've been running NC since like vers 12 or so and about every other time I upgrade it bonks totally. When I upgraded NC this time I ran into the same "internal Service Error". According to the NC forums that pretty much the generic error message. Instead of going through the logs I decided to just nuke the Docker image and delete the appdata directory. I was on vers 18 and was only really using it for file serving/backup which I have all going to a directory outside the appdata directory and Docker so I figured those files were all safe anyway. I tried deleting and starting from my back-up NC appdata folder but it gave me the same error.

 

After you delete the NC image and dir (I actually moved it instead for backup - although it doesn't work), you can just load your NC template and start from scratch. It will automatically install the newest version (v20) and recreate the appdata directory.

 

You will need to connect it to the old database so NOTE: If you want to keep your users/pw you will need to know your user/database/pw for your Nextcloud database on Maraidb (assuming you did the SpaceInvader video you can go there and maybe you used the same?? Fortunately I wrote mine down). O/w you will need to start fresh with a new db and users, etc :(

 

The issue I ran into here was it would not let me use the same admin account I used before so I had to create a new admin username/pw  and then use the old database. But with that, it set up and everything was still there including my upload history and such for other users. 

 

This is what worked for me. Good luck. But you may want to make back-ups of everything just in case.  I like Nextcloud and it has gotten much better over time, but it is still very temperamental! If it's not something easily googled, I just wipe it and start over.

 

  • Like 1
Link to comment

I was greeted with this error this morning.  Is this a container issue that needs solved or an issue I should fix myself?

 

This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.14.

This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.14.

 

Link to comment

I am also now getting the same error message as you, discojon, when starting the WebGUI of my Nextcloud Docker:

This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.14


would you be able to let me know how exactly can I get it to work again?

Where exactly is this config folder where you edited versioncheck.php?

Link to comment

So I was able to bypass the error message but the subsequent update failed so I'm not recommending that at this point.  I'm currently restoring from a backup and hopefully that will get me running.  I think the core issue here is the version of NC this container is running is 17 which is EoL apparently.  

Edited by discojon
Link to comment
2 minutes ago, discojon said:

So I was able to bypass the error message but the subsequent update failed so I'm not recommending that at this point.  I'm currently restoring from a backup and hopefully that will get me running.  I think the core issue here is the version of NC this container is running is 17 which is EoL apparently.  

This is just wrong - it's because you haven't been updating nextcloud within the container. It's our only one that you have to independently update inside the container aswell images.

Link to comment
18 minutes ago, tillkrueger said:

I am also now getting the same error message as you, discojon, when starting the WebGUI of my Nextcloud Docker:

This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.14


would you be able to let me know how exactly can I get it to work again?

Where exactly is this config folder where you edited versioncheck.php?

The config folder is located in your Nextcloud data location.  

 

Just now, j0nnymoe said:

This is just wrong - it's because you haven't been updating nextcloud within the container. It's our only one that you have to independently update inside the container aswell images.

 

The only options I'm presented with when updating in the container are stable and beta.  I don't have an option to upgrade to next version

Link to comment
1 minute ago, discojon said:

The config folder is located in your Nextcloud data location.  

 

 

The only options I'm presented with when updating in the container are stable and beta.  I don't have an option to upgrade to next version

 

What do you mean by next? You only have stable and beta channel in the webui.

 

There is info on updating using the command line in the first post.

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.