Docker update from 24 to 25 - issue with Signature data not found

Hello

First Nextcloud did update and is working but
I have this message

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

  • related_resources
    • EXCEPTION
      • OC\IntegrityCheck\Exceptions\InvalidSignatureException
      • Signature data not found.

Raw output

Array
(
[related_resources] => Array
(
[EXCEPTION] => Array
(
[class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
[message] => Signature data not found.
)

    )

)

Something is missing in the latest docker image ?

Thanks

I have the same issue with the regular non-docker install after updating with the webupdater to 25 stable

2 Likes

Same issue here, upgraded from 24 to 25 using Docker and I get the below.

The provided text and help do not assist in resolving this issue as no files are actually listed…


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
=======
- related_resources
	- EXCEPTION
		- OC\IntegrityCheck\Exceptions\InvalidSignatureException
		- Signature data not found.

Raw output
==========
Array
(
    [related_resources] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
                    [message] => Signature data not found.
                )

        )

)

Same here. I just updated my regular 24.0.6 to 25.0.0 and have the same error.

Same here. Using Docker.

Having the same issue here. Using docker nextcloud:25.0.0 with digest sha256:c65b3a099746f9168a594adc84f586a6a40719f50889d7814a6b68f6e183b26b.

A related issue has been opened on GitHub already.

Exact same issue here. Using Docker. Went from v24 (latest version) to v25

I am also having the same issue

same here, docker

same here on docker

is there there a fix already?

Update the Related Resources app and rescan the files.