4 minutes ago, enricovandijkhuizen said:

I just updated to the latest version but I now have the problem that after loggin in I don't have any style... Everything is just white and I also don't have any icon images? Does someone now a solution for this? 

Check your container logs and post them here.

3 minutes ago, iXNyNe said:

Check your container logs and post them here.

I don't understand wtf just happend but after a couple of minutes and a browser refresh everything is back to normal and all styles are being applied again... 

 

So I don't think I need to post the logs... Now I have just the problem with the Integrity Check...

41 minutes ago, enricovandijkhuizen said:

I don't understand wtf just happend but after a couple of minutes and a browser refresh everything is back to normal and all styles are being applied again... 

 

So I don't think I need to post the logs... Now I have just the problem with the Integrity Check...

That will be resolved after an update to the container. It is currently being tested. 

If anyone wants to test the fix here are instructions https://github.com/linuxserver/docker-nextcloud/issues/324#issuecomment-1608555412

I would just ask that you let me know your results.

 

Right now I'm just waiting for confirmation.

hi, just updated to 27.0.0 

i do get a message in nextcloud 

 

`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…)` pressing rescan does nothing, any fix for this ?

16 minutes ago, Danuel said:

hi, just updated to 27.0.0 

i do get a message in nextcloud 

 

`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…)` pressing rescan does nothing, any fix for this ?

The integrity check message shouldn't cause any functional issue and should be resolved in the next release. If you're interested in testing the fix before it is fully released see my message above.

Edited June 27, 20233 yr by iXNyNe

4 hours ago, iXNyNe said:

The integrity check message shouldn't cause any functional issue and should be resolved in the next release. If you're interested in testing the fix before it is fully released see my message above.

The latest test image is

lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325

 

It has a bunch of small fixes and tweaks, among them the integrity check extra files should be resolved.

Shouldn't be long before this is released as lscr.io/linuxserver/nextcloud:latest for those who would like to wait.

14 minutes ago, iXNyNe said:

The latest test image is

lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325

 

It has a bunch of small fixes and tweaks, among them the integrity check extra files should be resolved.

Shouldn't be long before this is released as lscr.io/linuxserver/nextcloud:latest for those who would like to wait.

So do I need to stay locked onto “lscr.io/linuxserver/nextcloud:version-27.0.0” or what’s recommendation for things like this with fixes and such? Or will the fixes move to “…-27.0.0.”?

1 hour ago, blaine07 said:

So do I need to stay locked onto “lscr.io/linuxserver/nextcloud:version-27.0.0” or what’s recommendation for things like this with fixes and such? Or will the fixes move to “…-27.0.0.”?

Staying locked is smart, but if you prefer the bleeding edge you can go back to the latest tag.

 

If you're locked there won't be any surprise updates. Not every update will work perfectly even if you're locked (always check the changes logs for important changes), but using latest could mean a breaking change is applied at a time when you're less prepared to handle it.

15 hours ago, iXNyNe said:

That's the correct log.

 

At the bottom it mentions two nginx config files you need to update (the samples in the folder with those files are the updated version). If you didn't customize those files yourself you can delete them and restart the container and they will be recreated.

Looks like deleting and restarting did the trick. What, if anything different will I notice from this change?

 

Thanks,

Lev

NextLog2.txt

 

PS. also, deleting the "invalid files" is a pain as I have to do it via terminal or MC. doing it through Windows yields - I do not have permission. 

 

Also, now the there is a  "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds. Message - fixed that by     add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;

 

 

 

 

Edited June 28, 20233 yr by levster

2 hours ago, levster said:

Looks like deleting and restarting did the trick. What, if anything different will I notice from this change?

 

Thanks,

Lev

NextLog2.txt 25.81 kB · 0 downloads

 

PS. also, deleting the "invalid files" is a pain as I have to do it via terminal or MC. doing it through Windows yields - I do not have permission. 

 

Also, now the there is a  "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds. Message - fixed that by     add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;

 

 

 

 

Re: changes from deleting the nginx confs

At the top of each file is a link to the list of changes applied to the file. It's usually minor functional or organizational changes with these.

 

Re: integrity check extra files

You can try the test image I posted above (it should take care of the files for you) or hang in there for the next stable release. The files don't cause any issue other than the warning, and they will be cleaned up automatically with the next release (or using the test image).

 

Re: header warning

If you're using nextcloud behind a reverse proxy you should configure that setting in your proxy rather than nextcloud. I advise looking up what hsts is and how it works and ensuring you can access nextcloud via https before turning hsts on. Otherwise, ignore the warning. It's harmless.

Hi

I have still another issue. The cronjob doesn't work anymore. 

The file is not more available. How i can fix this? 

 

 

 

Thank and greez mAik

 

5 hours ago, maikki said:

Hi

I have still another issue. The cronjob doesn't work anymore. 

The file is not more available. How i can fix this? 

 

 

 

Thank and greez mAik

 

The container comes with its own cron, you shouldn't need a user script. If you look in /config/crontabs/ there should be a file called root, and I'm guessing it has an incorrect path in it. You can delete the file and restart the container and it will recreate the file with the correct path.

1 hour ago, iXNyNe said:

The container comes with its own cron, you shouldn't need a user script. If you look in /config/crontabs/ there should be a file called root, and I'm guessing it has an incorrect path in it. You can delete the file and restart the container and it will recreate the file with the correct path.

 

Thx for help.. 

I deletet the file and restart the cotainer.. The file was new create but the issue is the same. (Uptime Container 10min)

 

 

s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
cp: not replacing '/config/crontabs/root'
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    99
User GID:    100
───────────────────────────────────────

using keys found in /config/keys
# do daily/weekly/monthly maintenance
# min   hour    day     month   weekday command
*/15    *       *       *       *       run-parts /etc/periodic/15min
0       *       *       *       *       run-parts /etc/periodic/hourly
0       2       *       *       *       run-parts /etc/periodic/daily
0       3       *       *       6       run-parts /etc/periodic/weekly
0       5       1       *       *       run-parts /etc/periodic/monthly
# nextcloud cron
*/5     *       *       *       *       s6-setuidgid abc php7.4 -f /app/www/public/cron.php
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2021-10-24 │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│            │ 2023-06-23 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory

Edited June 28, 20233 yr by maikki
Containerlog

1 hour ago, maikki said:

 

Thx for help.. 

I deletet the file and restart the cotainer.. The file was new create but the issue is the same. (Uptime Container 10min)

 

 

s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
cp: not replacing '/config/crontabs/root'
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    99
User GID:    100
───────────────────────────────────────

using keys found in /config/keys
# do daily/weekly/monthly maintenance
# min   hour    day     month   weekday command
*/15    *       *       *       *       run-parts /etc/periodic/15min
0       *       *       *       *       run-parts /etc/periodic/hourly
0       2       *       *       *       run-parts /etc/periodic/daily
0       3       *       *       6       run-parts /etc/periodic/weekly
0       5       1       *       *       run-parts /etc/periodic/monthly
# nextcloud cron
*/5     *       *       *       *       s6-setuidgid abc php7.4 -f /app/www/public/cron.php
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2021-10-24 │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│            │ 2023-06-23 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.
s6-applyuidgid: fatal: unable to exec php7.4: No such file or directory

That's definitely not the most up to date cron file. It should look like this https://github.com/linuxserver/docker-nextcloud/blob/master/root/etc/crontabs/root

2 hours ago, iXNyNe said:

That's definitely not the most up to date cron file. It should look like this https://github.com/linuxserver/docker-nextcloud/blob/master/root/etc/crontabs/root

Okay, thanks this fix the cronjob.. 

 

greez maik

Hi, today I started up nextcloud after a week and it won’t start because the data is from NC 25 and yesterday it was automatic updated to NC 27. I use appdata backup v2.5, it’s possible that rolling back a backup of appdata can fix the problem or I need to reinstall NC? The backup was from 20/06/2023

thanks

15 minutes ago, mv_dev said:

Hi, today I started up nextcloud after a week and it won’t start because the data is from NC 25 and yesterday it was automatic updated to NC 27. I use appdata backup v2.5, it’s possible that rolling back a backup of appdata can fix the problem or I need to reinstall NC? The backup was from 20/06/2023

thanks

https://info.linuxserver.io/issues/2023-06-25-nextcloud/

You should not need to restore from backup. You will need to change your image (as instructed in the post I'm linking) and follow the steps to get updated. Future updates shouldn't require manual action.

I reinstalled Nextcloud

But I can't connect it to an already existing my MaridDB database - message that the user already exists

How do I connect to the my previous Nextcloud database ?

3 minutes ago, Thulsa Doom said:

I reinstalled Nextcloud

But I can't connect it to an already existing my MaridDB database - message that the user already exists

How do I connect to the my previous Nextcloud database ?

does your config.php still have the correct database credentials and connection info?

can you post your container logs here?

14 minutes ago, iXNyNe said:

у вашего config.php все еще есть правильные учетные данные базы данных и информация о подключении?

Вы можете разместить журналы контейнера здесь?

Yes - I copied the appdata/nextcloud folder
When opening the GUI window with a clean install

 

Error
The username is already in use

Create an administrator account

 

 

2 hours ago, Thulsa Doom said:

Yes - I copied the appdata/nextcloud folder
When opening the GUI window with a clean install

 

Error
The username is already in use

Create an administrator account

 

 

And there is no option to login (instead of register)?

My next suggestion would be to check the config.php for a version. Post the version from your config.php here along with your container logs (those really help narrow things down). We may need to change to an older image to try and get things working again, and possibly might need to restore the config, the data mount, and the database (but I won't be sure what's needed without more info).

 

p.s I can only read english unfortunately, so I may have to ask for translations

Is there any way to update nextcloud if I'm unable to change the docker app versions in unraid? I have a weird issue in unraid that crashes unraid entirely when I change versions. 

 

I just can't upgrade it manually because of the new image. Well, I could if I could chjange the version but that's not an option in my case until that's resolved if ever.. Would be nice to have nextcloud again.

 

Hi guys.

In order to use the latest linuxserver.io nextcloud docker image. I was told  I need to update my nextcloud to version 24 first.

I run "updater.phar" command throught cli within the docker container. The update failed with the error:

An unhandled exception has been thrown:
ArgumentCountError: Too few arguments to function OCA\Circles\Migration\Version0022Date20220526111723::__construct(), 0 passed in /config/www/nextcloud/lib/private/DB/MigrationService.php on line 456 and exactly 1 expected in /config/www/nextcloud/apps/circles/lib/Migration/Version0022Date20220526111723.php:55
Stack trace:
#0 /config/www/nextcloud/lib/private/DB/MigrationService.php(456): OCA\Circles\Migration\Version0022Date20220526111723->__construct()
#1 /config/www/nextcloud/lib/private/DB/MigrationService.php(473): OC\DB\MigrationService->createInstance()
#2 /config/www/nextcloud/lib/private/DB/MigrationService.php(419): OC\DB\MigrationService->executeStep()
#3 /config/www/nextcloud/lib/private/Installer.php(590): OC\DB\MigrationService->migrate()
#4 /config/www/nextcloud/lib/private/Installer.php(544): OC\Installer::installShippedApp()
#5 /config/www/nextcloud/lib/private/Updater.php(276): OC\Installer::installShippedApps()
#6 /config/www/nextcloud/lib/private/Updater.php(132): OC\Updater->doUpgrade()
#7 /config/www/nextcloud/core/Command/Upgrade.php(255): OC\Updater->upgrade()
#8 /config/www/nextcloud/3rdparty/symfony/console/Command/Command.php(255): OC\Core\Command\Upgrade->execute()
#9 /config/www/nextcloud/3rdparty/symfony/console/Application.php(1000): Symfony\Component\Console\Command\Command->run()
#10 /config/www/nextcloud/3rdparty/symfony/console/Application.php(271): Symfony\Component\Console\Application->doRunCommand()
#11 /config/www/nextcloud/3rdparty/symfony/console/Application.php(147): Symfony\Component\Console\Application->doRun()
#12 /config/www/nextcloud/lib/private/Console/Application.php(215): Symfony\Component\Console\Application->run()
#13 /config/www/nextcloud/console.php(100): OC\Console\Application->run()
#14 /config/www/nextcloud/occ(11): require_once('/config/www/nex...')
#15 {main}
Keep maintenance mode active? [y/N] 

 

My nextcloud server is stuck in maintenance mode. Did anyone have the same problems with me? Please hlep me! By the way, I update from 20.0.2 to 20.0.14 and I got the aformentioned error.

 

On 6/27/2023 at 4:19 PM, iXNyNe said:

Follow the instructions here to get your nextcloud running https://info.linuxserver.io/issues/2023-06-25-nextcloud/

 

Once that's done, if you prefer automatic updates, the post mentions using the image without a tag. Then anytime you update the docker container it should update nextcloud (no more manual command updates).

 

If you prefer manual updates, pin a tag for the current version and change the tag when you want to update.

I cant even find the app in the docker list.

 

Even version.php or config.php , all are empty. What should i do ?