When is the docker going to be updated with 27.0.2? It's been a few days now...

2 hours ago, darcon said:

When is the docker going to be updated with 27.0.2? It's been a few days now...

you may ask in the lsio discord channel or at their github etc ...

On 8/13/2023 at 5:31 AM, darcon said:

When is the docker going to be updated with 27.0.2? It's been a few days now...

https://github.com/nextcloud/server/releases

meanwhile 27.0.2 got releases. It's working now.

 

Just updated mine

If you have an instance of RSSHub available - or are hosting it yourself - you can subscribe to the tags for this image using something like this:

 

https://rsshub.yourinstance.whatever/dockerhub/tag/linuxserver/nextcloud

 

Then you should be notified when new releases come up.  It will have an entry for every build, but 8 or so notices every once in a while is no big deal for me.

Hi all

 

after some fun with an old docker install and finally getting it updated and running it seems the cron job isn't working for me and i get this is the log

 

s6-applyuidgid: fatal: unable to exec php7: No such file or directory

 

anyone able to assist or point me to more info if required 

5 hours ago, Maff said:

Hi all

 

after some fun with an old docker install and finally getting it updated and running it seems the cron job isn't working for me and i get this is the log

 

s6-applyuidgid: fatal: unable to exec php7: No such file or directory

 

anyone able to assist or point me to more info if required 

just incase anyone else runs into this i had to edit my crontab file as it was set to php7, changing it to php82 works and also php, now to research the correct way

6 hours ago, Maff said:

Hi all

 

after some fun with an old docker install and finally getting it updated and running it seems the cron job isn't working for me and i get this is the log

 

s6-applyuidgid: fatal: unable to exec php7: No such file or directory

 

anyone able to assist or point me to more info if required 

if you haven't intentionally customized the root cron file in your config i would suggest deleting it and restarting the container. This will recreate the default file with the latest changes.

On 8/12/2023 at 12:22 PM, tmor2 said:

(A)

I wanted to manually update from 26.0.5.1 to 27.0.2 using UNRAID terminal.

-my docker image was set to lscr.io/linuxserver/nextcloud:version-25.0.2, (this was done several months ago, to resolve issues when migrating v24 to 25 - I didn't realize this after I started erors below).

 

- On UNRAID terminal I executed "docker exec -it nextcloud updater.phar"

The updater process started, but it gets stuck at "Delete old files"..Error message says:

 

*********************

[✘] Delete old files failed
core/shipped.json is not available

Update failed. To resume or retry just execute the updater again.

*********************

 

No matter how often I re-execute "docker exec -it nextcloud updater.phar", I end up with the same error.

On the other side, WebGUI: states "Update in process."

 

(B)

Following is the version currently installed:

www/nextcloud/version.php --> (v 26.0.5.1)

www/nextcloud/config/config.php -->(v 26.0.5.1)

 

(C)

When I execute following command in UNRAID terminal docker logs nextcloud

I get following error listed.

 

************************

PHP Warning:  require_once(/config/www/nextcloud/lib/versioncheck.php): Failed to open stream: No such file or directory in /config/www/nextcloud/cron.php on line 40
PHP Fatal error:  Uncaught Error: Failed opening required '/config/www/nextcloud/lib/versioncheck.php' (include_path='.:/usr/share/php8') in /config/www/nextcloud/cron.php:40
Stack trace:
#0 {main}
  thrown in /config/www/nextcloud/cron.php on line 40

************************

 

(D)

What do I do?

 

 

Delete /config/www/nextcloud/index.php and set your image to lscr.io/linuxserver/nextcloud:version-26.0.2 and let the container restart. That should recreate the files it says are missing. Then you can rerun the updater.

On 8/3/2023 at 3:18 PM, iXNyNe said:

Set your image to

lscr.io/linuxserver/nextcloud:version-26.0.2

run in the unraid terminal (not the container terminal)

docker exec -it nextcloud updater.phar # if successful, run it again until it says there are no more updates

let us know the results

 Thanks for the reply, no that didn't work...

 

Are there any differences from this lsio docker opposed to the other labeled as “official” inside community apps?

23 minutes ago, sdballer said:

Are there any differences from this lsio docker opposed to the other labeled as “official” inside community apps?

yes ...

 

lets make it short, lsio based on alpine linux, lsio style with custom options and so on ...

 

official one is like when you pull nextcloud/nextcloud but with a template here in CA, different base distro, different setup ...

update to 27.0.2 got this

Quote

The database is missing some indexes. Due to the fact that adding indexes on big tables could take some time they were not added automatically. By running "occ db:add-missing-indices" those missing indexes could be added manually while the instance keeps running. Once the indexes are added queries to those tables are usually much faster.

 

Since you can no longer use docker exec -it how do you run the occ comand to correct this?

 

Drop into the console and run the command.

Edited August 15, 20232 yr by ijuarez

First of all, a huge thank you to the linuxserver team for getting Nextcloud to be upgraded via the container updates. This will be a huge step in making things easier to maintain. Unfortunately it looks like something wasn't quite right with my instance before I updated to the latest. I tried following the steps outlined in the how-to but ran into some issues. I'm beyond my depth and need some help. Here are the requested items:

• Container logs - 
• Nextcloud log file -  (in the/data volume) - Can't locate
• Nginx log (in the /config/logs volume) - Will provide if needed
• /config/www/nextcloud/config/config.php file - config.php
• Screenshot: 

 

Edited August 16, 20232 yr by mikester15

Any idea why this command in the nextcloud console window doesn't work anymore?

 

 

I'm trying to run 

sudo -u abc php /config/www/nextcloud/occ db:add-missing-indices

 

but it's like the file is not there anymore

Edited August 16, 20232 yr by bigbangus

Spoke too soon. It's now apparently:

 

sudo -u abc php /app/www/public/occ db:add-missing-indices

 

 

Edited August 19, 20232 yr by bigbangus
typo in command

7 hours ago, bigbangus said:

Spoke too soon. It's now apparently:

 

sudo u- abc php /app/www/public/occ db:add-missing-indices

 

 

This helped me out, but spoke to soon again. Mixed up the u- where it should be -u

Thank you!
 

sudo -u abc php /app/www/public/occ db:add-missing-indices

 

12 hours ago, bigbangus said:

Spoke too soon. It's now apparently:

 

sudo u- abc php /app/www/public/occ db:add-missing-indices

 

 

Bruh!, OMG! Thank you so much. I have been trying to get this cleared up without bothering anyone for a while now. I knew it had worked before the other way. That's how I had in my notes. Works like a charm with the correct path.

 

@Wolfhunter1043 Caught the "u-" typo too but thanks for the post. 

Hello
Before I read the whole thread and investigate, I have a simple question to determine if Nextcloud is what i need.
My goal is to be able to select specific files, or folders within my main folder and share them in read only over the internet.
Obviously I wish this to be totally secure on my end and very easy for the receiver, maybe under the form of a link to click, that's it.

Is Nextcloud what i need? If so is there a very simple walkthrough to install it and get this result? (I tried and failed already)

3 hours ago, xtrips said:

Before I read the whole thread and investigate,

no need for your question ... this thread is related to the NC Docker and if you have issues running it, not about features ...

 

3 hours ago, xtrips said:

Is Nextcloud what i need?

may just google it and figure it ... dont be too lazy

 

sample

https://nextcloud.com/de/features/

 

then decide ...

I am using the linuxserver.io nextcloud container behind a reverse proxy using NginxProxyManager.

 

to reduce overhead i wanted to use the http connection behind the reverse proxy instead of the https connection (is on the same machine, does not really matter.) but whenever i use the http connection i get this warning in the settings overview:

Quote

There are some warnings regarding your setup.

Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation ↗.

Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation ↗.

 

I investigated the ./nginx/site-confs/default.conf configuration of this container, but i dont see there being made a difference between http and https, so ... what gives?

5 hours ago, Greyberry said:

I investigated the ./nginx/site-confs/default.conf configuration of this container, but i dont see there being made a difference between http and https, so ... what gives?

this has nothing todo with http or https, this is a known message and you will find plenty of infos if you just google it and add some extras in the proper file, im pretty sure its even mentioned several times in this thread actually.

5 hours ago, alturismo said:

this has nothing todo with http or https, this is a known message and you will find plenty of infos if you just google it and add some extras in the proper file, im pretty sure its even mentioned several times in this thread actually.

it has everything to do with http and https, because (A) i have the proper rules in place:

location ^~ /.well-known {
        # The rules in this block are an adaptation of the rules
        # in `.htaccess` that concern `/.well-known`.

        location = /.well-known/carddav { return 301 /remote.php/dav/; }
        location = /.well-known/caldav  { return 301 /remote.php/dav/; }

        location /.well-known/acme-challenge    { try_files $uri $uri/ =404; }
        location /.well-known/pki-validation    { try_files $uri $uri/ =404; }

        # Let Nextcloud's API for `/.well-known` URIs handle all other
        # requests by passing them to the front-end controller.
        return 301 /index.php$request_uri;
    }

and (B) the warnings do not occur, when i use https behind the reverse proxy.

On 8/16/2023 at 2:19 PM, Wolfhunter1043 said:

This helped me out, but spoke to soon again. Mixed up the u- where it should be -u

Thank you!
 

sudo -u abc php /app/www/public/occ db:add-missing-indices

 

 

On 8/16/2023 at 7:23 PM, Conson Droppa said:

@Wolfhunter1043 Caught the "u-" typo too but thanks for the post. 

 

Fixed in the post. Sorry for the typo fellas if it wasn't hard enough already to chase the occ debacle. Glad I could help.

16 hours ago, Greyberry said:

it has everything to do with http and https, because (A) i have the proper rules in place:

then it should look like this as sample when you directly connecting to your nextcloud server in LAN (with its direct IP)

 

 

most common is that the "well" part was added on the RP Part and while you connecting diretly (bypassinng the RP) then of course you are back in that error ... but as you checked your NC nginx conf ... you should be fine as this is always "ruled" then.

 

 

if you dont get this error (like me posted above) while connectd directly ... my step would be (as im using swag i cant really tell) if NPM is calling this issue, may ask there if anyone may could help ... or if it needs to be added there too ...

 

and btw. your expected benefit (reduce overhead) wont be noticeable if there is any at all ... just as note.

8 hours ago, alturismo said:

then it should look like this as sample when you directly connecting to your nextcloud server in LAN (with its direct IP)

 

Yes when I'm connecting directly it looks like this, but i never use http in the first place on the client side. I wanted to use it on the "backend" so to speak.

 

[Client] -------- https --------> [Reverse Proxy] -------- https -------> [NextCloud] // No Error Occurs

[Client] -------- https --------> [Reverse Proxy] -------- http -------> [NextCloud]  // cardav Error Occurs

 

8 hours ago, alturismo said:

if you dont get this error (like me posted above) while connectd directly ... my step would be (as im using swag i cant really tell) if NPM is calling this issue, may ask there if anyone may could help ... or if it needs to be added there too ...

Okay, i might look further into this in two weeks (I'm not at home the next days). Thank you for taking me seariously in the end, and thank you for your time.

 

8 hours ago, alturismo said:

and btw. your expected benefit (reduce overhead) wont be noticeable if there is any at all ... just as note.

I remember reading an article with benchmarks some time ago, where there was showing quite a difference on low-end machines. I can't find it at the moment unfortunatelly.

But maybe you're right and it is not worth the hassle on newer machines.