files_mindmap icon indicating copy to clipboard operation
files_mindmap copied to clipboard

InvalidSignatureException - Certificate is not valid

Open hermann-san opened this issue 10 months ago • 5 comments

Hi, after a NC update to NC 30.0.5, I've got the below error message. I did deactivate Mindmap, reactivated it, and did a rescan, but the issue is still there. Is there a way to fix this or is an update required? I did not yet re-installed the extension.

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
=======
- files_mindmap
	- EXCEPTION
		- OC\IntegrityCheck\Exceptions\InvalidSignatureException
		- Certificate is not valid.

Raw output
==========
Array
(
    [files_mindmap] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
                    [message] => Certificate is not valid.

hermann-san avatar Feb 12 '25 11:02 hermann-san

Same after upgrading to 30.0.6. I did uninstall and reinstall. Issue stays. The cause seems to be issue #214

thanks for this wonderful app.

simon1964 avatar Feb 13 '25 19:02 simon1964

I'm seeing this also, after updating to 30.0.6

crazybadger avatar Feb 14 '25 09:02 crazybadger

Hello all,

Seeing this too, after updating to 30.0.6.

mickey86 avatar Feb 16 '25 18:02 mickey86

hi, same problem here - after upgrade to 30.0.6 uninstall/reinstall did not help.

there is no cerfitificate in the signature.json file. according to code_signing you have to request your certificate from nextcloud and have to include it into the signature.json file. would be great if you could apply and include it, thanks!

grufocom avatar Feb 17 '25 05:02 grufocom

Same here. After removing the app, another error found

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
=======
- files_mindmap
	- EXCEPTION
		- OC\IntegrityCheck\Exceptions\InvalidSignatureException
		- Certificate is not valid.
- mindmap
	- EXCEPTION
		- Exception
		- App not found

Raw output
==========
Array
(
    [files_mindmap] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
                    [message] => Certificate is not valid.
                )

        )

    [mindmap] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => Exception
                    [message] => App not found
                )

        )

)

Please let me know about any solution, thanks!

WeskerC avatar Feb 17 '25 09:02 WeskerC

Same problem here. Don't know when this started, just noticed it after upgrading to NC v31

Miyamoto72 avatar Feb 26 '25 12:02 Miyamoto72

Same here on NC31.

Bad-and-Mad avatar Mar 03 '25 07:03 Bad-and-Mad

Any news here? It keeps me updating to 30.0.6

Uatschitchun avatar Mar 06 '25 10:03 Uatschitchun

Nothing, the author disappear

WeskerC avatar Mar 07 '25 10:03 WeskerC

Same problem here. Version is also Nexcloud 30.0.6.

Franz-Heinz avatar Mar 10 '25 13:03 Franz-Heinz

Same here. But the author disappeared?

larsik78 avatar Mar 19 '25 07:03 larsik78

Same issue on 0.33.0 and Nextcloud 31.0.2

maurerle avatar Apr 03 '25 02:04 maurerle

See also here and here

schnillerman avatar May 29 '25 07:05 schnillerman

What's the solution to fix this?

js-d-coder avatar Jun 21 '25 07:06 js-d-coder

What's the solution to fix this? The solution lies with the developer, who needs to request a certificate from Nextcloud. Could be any of the devs, I believe

EDIT: KityMinder (which is he base for this integration) has had it's latest update in 2014. Developing a new mindmapping solution to be used as an app in NextCloud would make more sense, imho.

Martinfst avatar Jun 24 '25 06:06 Martinfst

v. 31.0.7 same problem

hrs-s-w avatar Jul 27 '25 01:07 hrs-s-w

v. 31.0.7 same problem

The issue is with the mindmap app developer. Nextcloud wil never be able to solve this. Any future Nextcloud release will show the same issue. I have investigated if another mindmapping tool can be integrated/developed as a new app for Nextcloud. Found a possibility, but my programming skills are probably not sufficient to do this successfully and in an acceptable timeframe.

Martinfst avatar Jul 27 '25 11:07 Martinfst

I'm placing this here in case it helps someone as frustrated with this error as I was. I uninstalled the Mindmaps app but the error would not go away. Nextcloud 31.0.7 on Ubuntu 24.04

The following was suggested by Google's Gemini 2.5Pro AI. And it got rid of the error for me after uninstalling-reinstalling-uninstalling the app, deleting its directory, removing all references to it in the oc_appconfig and oc_migrations database tables as well as multiple Nextcloud cache clears had all failed. Of course I don't have the app installed now so there's that. Change paths and names to suit your setup. Your mileage may vary, try at your own risk etc.


Gemini 2.5Pro Chat Output:

You are correct: that GitHub issue shows this is a known bug in how the files_mindmap app (and others like it) handle their digital signatures.

Why Deleting the App Doesn't Fix It

This is the most frustrating part, and your question gets to the core of the problem. Here’s what's happening:

  1. Nextcloud runs an integrity scan and finds the invalid signature from the Mind Map app.
  2. It saves this "failed" result into its core configuration cache within the database. This result is now stored as a permanent record, separate from the app itself.
  3. When you delete the app's files and its main database tables, you are removing the app, but you are not clearing the cached result of the previous failure.
  4. Every time you load the admin page, Nextcloud isn't re-scanning the now-deleted app. Instead, it's just reading the old, "stuck" failure report from its cache and displaying it to you.

This explains why no amount of file deletion or server reboots has worked. We need to manually perform surgery on that specific cache entry in the database.


The Final Solution: Manually Clear the Cached Result

The nc-integrity-fix script and our DELETE commands were supposed to clear this, but since the error remains, we will try one last, more direct approach: we will UPDATE the stuck record with a blank value instead of trying to delete it.

1. Log in to Your Database

sudo mysql -u 'nextcloud_user' -p

2. Select Your Database

USE nextcloud_db;

3. Manually Overwrite the Cached Integrity Report

This command finds the exact database entry where the "failed" report is stored and overwrites it with an empty array [], effectively telling Nextcloud there are no issues.

UPDATE oc_appconfig SET configvalue = '[]' WHERE appid = 'core' AND configkey = 'oc.integritycheck.checker';

(Remember to replace oc_ if you use a different table prefix).

You should get a confirmation like Query OK, 1 row affected.

4. Exit and Clear the In-Memory Cache

exit;

Now, run the standard repair command to make sure all of Nextcloud's other caches are cleared and it's forced to re-read the now-empty database value.

sudo -u www-data php /var/www/nextcloud/occ maintenance:repair

This is the most targeted fix possible for this specific, persistent error. After running these commands, refresh your admin page. It should finally be clear.

emkamau avatar Aug 14 '25 09:08 emkamau