Invalid Signature: Verification equation was not satisfied

Subject

Nextcloud migration failed after StartOS 0.4 upgrade (Invalid Signature), now unable to migrate 31.0.13:1 → 33.0.6:2

Hello,

While reviewing my notification history I found what appears to be the original failure.

When upgrading StartOS from 0.3.5.1 to 0.4.0.1, Nextcloud failed to migrate.

The notifications show:

Migration Failed


Invalid Signature:
signature error:
Verification equation was not satisfied

Immediately afterward:

Services Failed To Migrate


Failed to migrate the following services from 0.3.5.1:

Nextcloud

YOUR DATA IS SAFE.
Simply re-install these services from the marketplace.

Since then every update attempt fails with:


Unknown Error:
cannot migrate from 31.0.13:1 to 33.0.6:2

The package also fails to start and logs:


get-ssl-certificate

unknown hostname:
153.66.101.236

During troubleshooting I verified:

  • package host registration exists

  • package bindings are correct

  • WAN address is correctly registered

  • manual SSL certificate generation succeeds

This makes me suspect the SSL error is secondary to the original failed package migration.

My concern is that this Nextcloud instance contains approximately 1.5 TB of production data, so I would like to recover the existing installation rather than reinstall if possible.

Can someone advise the safest recovery path?

Specifically:

  • Is there a supported way to complete or repair the failed migration?

  • Is start-cli package rebuild nextcloud appropriate?

  • If reinstalling the package is required, what is the recommended procedure to preserve the existing data volume?


I think we’ve found the smoking gun

I have to admit I wish we’d found this screenshot sooner—it changes the diagnosis significantly.

The very first failure wasn’t an SSL error.

It was:

Invalid Signature: Verification equation was not satisfied

Everything that happened afterward—including the failed updates and the SSL problem—may simply be fallout from a package that never migrated correctly to StartOS 0.4.

This is exactly the kind of information Start9’s engineers will want to see first.