Is there a way to re-trigger the DB migration from v0.9.4 to v0.10.0?

[FusionStreak]

Hello,

This morning I followed UPGRADING.md to upgrade from v0.9.4 to v0.10.0. But I accidentally skipped the step to update the WebAdmin before updating the stalwart-mail binary. And it seems that the DB was not migrated (I can not view my users, domains, etc).

I get the following error when trying to view anything under Directory:

Failed to deserialize response
data did not match any variant of untagged enum Response

Is there anyway to manually re-trigger the migration process? I did create a backup before the update.

[mdecimus]

Yes, you can upgrade the webadmin using curl:

# curl -k -u admin:yourpass https://yourserver/api/update/webadmin

[FusionStreak]

I am able to login with my admin account, but not with any other accounts. And I have upgraded the WebAdmin from the web interface. But the database hasn't migrated. I am unable to view anything under Directory.

My setup:

OS: Ubuntu jammy 22.04 x86_64
Kernel: Linux 5.15.0-119-generic
Stalwart: v0.10.0 (directly installed)

[mdecimus]

Any errors on the logs? You're seeing that message because the webadmin version does not match the mail server version. When you hover over the Stalwart logo on the webadmin make sure it shows the latest version number.

[FusionStreak]

When I hover over the logo, it shows:

Stalwart Management UI v0.1.15

Here are the logs when trying to update the WebAdmin:

2024-09-24T18:56:45Z DEBUG HTTP request URL (http.request-url) listenerId = "https", localPort = 443, remoteIp = X.X.X.X, remotePort = 54109, url = "/api/update/webadmin"
2024-09-24T18:56:45Z TRACE Expression evaluation result (eval.result) listenerId = "https", localPort = 443, remoteIp = X.X.X.X, remotePort = 54109, id = "server.http.allowed-endpoint", result = "Integer(200)"
2024-09-24T18:56:45Z TRACE Write batch operation (store.data-write) elapsed = 0ms, total = 2
2024-09-24T18:56:45Z TRACE HTTP request body (http.request-body) listenerId = "https", localPort = 443, remoteIp = X.X.X.X, remotePort = 54109, contents = "", size = 0
2024-09-24T18:56:46Z TRACE Blob write operation (store.blob-write) key = base64:U1RBTFdBUlRfV0VCQURNSU4=, elapsed = 19ms, size = 2303841
2024-09-24T18:56:46Z TRACE Blob read operation (store.blob-read) key = base64:U1RBTFdBUlRfV0VCQURNSU4=, elapsed = 2ms, size = 2303841
2024-09-24T18:56:46Z INFO Webadmin resource unpacked (resource.webadmin-unpacked) path = "/tmp/STALWART_WEBADMIN"
2024-09-24T18:56:46Z TRACE HTTP response body (http.response-body) listenerId = "https", localPort = 443, remoteIp = X.X.X.X, remotePort = 54109, contents = "{"data":null}", code = 200, size = 13

[mdecimus]

Are you certain that you're running v0.10.0? Try executing stalwart-mail -V