500 Server Error after migration

Lucas ReisOriginal post

Rank 2: Process

Sep 30, 2025, 16:59

I am trying to migrate my current appwrite instance to a new VPS. I have followed the official guide to backup and restore it and it seemed to work (I am able to login), but when I try to navigate to the database, auth, functions etc of a project, I get a 500 error. I have looked at the logs and found the following error:

Plain text

    [Error] Method: GET
    [Error] URL: /v1/project/usage
    [Error] Type: PDOException
    [Error] Message: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'pingCount' in 'SET'
    [Error] File: @swoole/library/core/Database/PDOStatementProxy.php
    [Error] Line: 49
    [Error] Timestamp: 2025-09-30T16:48:07+00:00
    [Error] Method: GET
    [Error] URL: /v1/users
    [Error] Type: PDOException
    [Error] Message: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'pingCount' in 'SET'
    [Error] File: @swoole/library/core/Database/PDOStatementProxy.php
    [Error] Line: 49```

Although it seems to not be necessary, I tried running the migration command but no luck.
The appwrite version I am using in the live server is the same I am using in the new VPS (1.7.4) and I have copied the same docker-compose and .env files from the production server, just changing the domain.

Does any one have any idea of what could be wrong? This **pingCount ** was [added](https://github.com/appwrite/appwrite/pull/8761/files) in version 1.6.x so I dunno why it says it is missing.

Summary

Developers' migration to new VPS causes a 500 Server Error with 'Unknown column pingCount' in PDOException. Error log shows missing column error for pingCount in the SET on the new server. Even though the migration guide was followed correctly and version consistency maintained, the error persists. The 'pingCount' column was added in a previous version, so check the database schema for discrepancies. Double-check the backup and restore process, and ensure that all necessary steps have been followed correctly during the migration to prevent column inconsistencies.

Need support?_