Drop-OSS/drop
1
0
Fork 0
mirror of https://github.com/Drop-OSS/drop.git synced 2026-07-21 16:15:24 -04:00
Code Issues 77 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #421] Database error when moving docker from ghcr.io/drop-oss/drop:latest to ghcr.io/drop-oss/drop:0.4.0-rc-3 #349

New Issue
Open
opened 2026-06-05 14:21:55 -04:00 by yindo · 5 comments
yindo commented 2026-06-05 14:21:55 -04:00
Owner
Copy Link
Copy Source

Originally created by @shadownetdev1 on GitHub (May 31, 2026).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/421

Title. I assume database migration missed something?

Docker log:

[03:04:02.574] INFO (19): enabled metadata provider: Steam

[03:04:02.575] INFO (19): enabled metadata provider: PCGamingWiki

[03:04:02.575] WARN (19): skipping metadata provider setup: Error: Missing config item IGDB_CLIENT_ID for IGDB

[03:04:02.610] INFO (service-torrential/19): service launched

[03:04:02.622] INFO (service-nginx/19): service launched

[03:04:02.945] INFO (service-torrential/19): INFO  [torrential] using 12 threads

[03:04:02.945] INFO (service-torrential/19): INFO  [torrential::server] created client subroutine

[03:04:02.945] INFO (service-torrential/19): INFO  [torrential] started depot server

[03:04:02.945] ERROR (service-nginx/19): nginx: [alert] could not open error log file: open() "/data/nginx/logs/error.log" failed (2: No such file or directory)

[03:04:02.945] INFO (service-torrential/19): connected to torrential socket

[03:04:02.945] INFO (service-torrential/19): service healthy

[03:04:03.074] INFO (19): initialised the ca

[03:04:03.120] INFO (19): enabled auth: OpenID

[03:04:03.120] INFO (19): enabled auth: Simple

[03:04:03.120] INFO (19): AuthManager initialized

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] https://drop.alcazar.top/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] https://drop.alcazar.top/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] http://localhost/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] https://drop.alcazar.top/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}

[request error] [unhandled] [GET] https://drop.alcazar.top/api/v1

 PrismaClientKnownRequestError: 

Invalid `prisma.applicationSettings.findFirst()` invocation:

The column `(not available)` does not exist in the current database.

    at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

    ... 8 lines matching cause stack trace ...

    at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

  cause: PrismaClientKnownRequestError: 

  Invalid `prisma.applicationSettings.findFirst()` invocation:

  

  

  The column `(not available)` does not exist in the current database.

      at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172)

      at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467)

      at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174)

      at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

      at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816)

      at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219)

      at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979)

      at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636)

      at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177)

      at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) {

    code: 'P2022',

    meta: {

      modelName: 'ApplicationSettings',

      driverAdapterError: [DriverAdapterError]

    },

    clientVersion: '7.3.0'

  },

  statusCode: 500,

  fatal: false,

  unhandled: true,

  statusMessage: undefined,

  data: undefined

}
Originally created by @shadownetdev1 on GitHub (May 31, 2026). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/421 Title. I assume database migration missed something? Docker log: ``` [03:04:02.574] INFO (19): enabled metadata provider: Steam [03:04:02.575] INFO (19): enabled metadata provider: PCGamingWiki [03:04:02.575] WARN (19): skipping metadata provider setup: Error: Missing config item IGDB_CLIENT_ID for IGDB [03:04:02.610] INFO (service-torrential/19): service launched [03:04:02.622] INFO (service-nginx/19): service launched [03:04:02.945] INFO (service-torrential/19): INFO [torrential] using 12 threads [03:04:02.945] INFO (service-torrential/19): INFO [torrential::server] created client subroutine [03:04:02.945] INFO (service-torrential/19): INFO [torrential] started depot server [03:04:02.945] ERROR (service-nginx/19): nginx: [alert] could not open error log file: open() "/data/nginx/logs/error.log" failed (2: No such file or directory) [03:04:02.945] INFO (service-torrential/19): connected to torrential socket [03:04:02.945] INFO (service-torrential/19): service healthy [03:04:03.074] INFO (19): initialised the ca [03:04:03.120] INFO (19): enabled auth: OpenID [03:04:03.120] INFO (19): enabled auth: Simple [03:04:03.120] INFO (19): AuthManager initialized [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] https://drop.alcazar.top/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] https://drop.alcazar.top/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] http://localhost/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] https://drop.alcazar.top/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } [request error] [unhandled] [GET] https://drop.alcazar.top/api/v1 PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) ... 8 lines matching cause stack trace ... at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { cause: PrismaClientKnownRequestError: Invalid `prisma.applicationSettings.findFirst()` invocation: The column `(not available)` does not exist in the current database. at Vr.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:8172) at Vr.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7467) at Vr.request (/app/app/server/node_modules/@prisma/client/runtime/client.js:65:7174) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async a (/app/app/server/node_modules/@prisma/client/runtime/client.js:75:5816) at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:992219) at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:991979) at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:992636) at async Object.handler (file:///app/app/server/chunks/routes/api/index.get.mjs:1:1177) at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921) { code: 'P2022', meta: { modelName: 'ApplicationSettings', driverAdapterError: [DriverAdapterError] }, clientVersion: '7.3.0' }, statusCode: 500, fatal: false, unhandled: true, statusMessage: undefined, data: undefined } ```
yindo commented 2026-06-05 14:21:55 -04:00
Author
Owner
Copy Link
Copy Source

@DecDuck commented on GitHub (Jun 1, 2026):

Yep, looks like it. There should be a line printed to the console when it runs - is it not there, or did you manually truncate the logs?

<!-- gh-comment-id:4589435357 --> @DecDuck commented on GitHub (Jun 1, 2026): Yep, looks like it. There should be a line printed to the console when it runs - is it not there, or did you manually truncate the logs?
yindo commented 2026-06-05 14:21:55 -04:00
Author
Owner
Copy Link
Copy Source

@shadownetdev1 commented on GitHub (Jun 1, 2026):

I do not believe that my logs were truncated, but I will check again when I can (likely tomorrow or Tuesday)

<!-- gh-comment-id:4590252455 --> @shadownetdev1 commented on GitHub (Jun 1, 2026): I do not believe that my logs were truncated, but I will check again when I can (likely tomorrow or Tuesday)
yindo commented 2026-06-05 14:21:55 -04:00
Author
Owner
Copy Link
Copy Source

@shadownetdev1 commented on GitHub (Jun 2, 2026):

I ended up doing everything fresh from beginning to end. Getting the same end result.

Attached is the full log file.

_drop-test_logs.txt

<!-- gh-comment-id:4605973360 --> @shadownetdev1 commented on GitHub (Jun 2, 2026): I ended up doing everything fresh from beginning to end. Getting the same end result. Attached is the full log file. [_drop-test_logs.txt](https://github.com/user-attachments/files/28522081/_drop-test_logs.txt)
yindo commented 2026-06-05 14:21:55 -04:00
Author
Owner
Copy Link
Copy Source

@shadownetdev1 commented on GitHub (Jun 2, 2026):

This issue can likely be closed. It seems to have been caused by some weird permissions bug. I force all my docker containers to a set user account to allow for non root backups (See the example below). When that line is in place Drop fails migration, but as I start over with the default ownership it works fine. There is no errors thrown in either container and no files added with the wrong ownership, so I have no idea where it is going wrong. Guess I will just have to add a exception in my backup script for Drop.

services:
  postgres:
    container_name: drop-postgres
    image: postgres:14-alpine
    healthcheck:
      test: pg_isready -d drop -U drop
      interval: 30s
      timeout: 60s
      retries: 5
      start_period: 10s
    volumes:
      - /appdata/drop/db:/var/lib/postgresql/data
    user: 1001:1001
    environment:
      - POSTGRES_PASSWORD=drop665
      - POSTGRES_USER=drop665
      - POSTGRES_DB=drop665
      - PUID=1001
      - PGID=1001
      - UMASK=000

  drop:
    container_name: drop
    image: ghcr.io/drop-oss/drop:0.4.0-rc-3
    depends_on:
      postgres:
        condition: service_healthy
    ports:
      - 2766:3000
    volumes:
      - /appdata/drop/library:/library
      - /appdata/drop/data:/data
    user: 1001:1001
    environment:
      - PUID=1001
      - PGID=1001
      - UMASK=000
      - DATABASE_URL=postgres://drop665:drop665@drop-postgres:5432/drop665
      - EXTERNAL_URL=<redacted> # default, customise if accessing from another computer or behind a reverse proxy
      - OIDC_CLIENT_ID=Drop
      - OIDC_CLIENT_SECRET=<redacted>
      - OIDC_ADMIN_GROUP=admin
      - OIDC_WELLKNOWN=https://<redacted>/realms/<redacted>/.well-known/openid-configuration # Keycloak
<!-- gh-comment-id:4606084815 --> @shadownetdev1 commented on GitHub (Jun 2, 2026): This issue can likely be closed. It seems to have been caused by some weird permissions bug. I force all my docker containers to a set user account to allow for non root backups (See the example below). When that line is in place Drop fails migration, but as I start over with the default ownership it works fine. There is no errors thrown in either container and no files added with the wrong ownership, so I have no idea where it is going wrong. Guess I will just have to add a exception in my backup script for Drop. ``` services: postgres: container_name: drop-postgres image: postgres:14-alpine healthcheck: test: pg_isready -d drop -U drop interval: 30s timeout: 60s retries: 5 start_period: 10s volumes: - /appdata/drop/db:/var/lib/postgresql/data user: 1001:1001 environment: - POSTGRES_PASSWORD=drop665 - POSTGRES_USER=drop665 - POSTGRES_DB=drop665 - PUID=1001 - PGID=1001 - UMASK=000 drop: container_name: drop image: ghcr.io/drop-oss/drop:0.4.0-rc-3 depends_on: postgres: condition: service_healthy ports: - 2766:3000 volumes: - /appdata/drop/library:/library - /appdata/drop/data:/data user: 1001:1001 environment: - PUID=1001 - PGID=1001 - UMASK=000 - DATABASE_URL=postgres://drop665:drop665@drop-postgres:5432/drop665 - EXTERNAL_URL=<redacted> # default, customise if accessing from another computer or behind a reverse proxy - OIDC_CLIENT_ID=Drop - OIDC_CLIENT_SECRET=<redacted> - OIDC_ADMIN_GROUP=admin - OIDC_WELLKNOWN=https://<redacted>/realms/<redacted>/.well-known/openid-configuration # Keycloak ```
yindo commented 2026-06-05 14:21:55 -04:00
Author
Owner
Copy Link
Copy Source

@shadownetdev1 commented on GitHub (Jun 2, 2026):

Sorry if I wasted any of your time and thanks for working on this great project!

<!-- gh-comment-id:4606090610 --> @shadownetdev1 commented on GitHub (Jun 2, 2026): Sorry if I wasted any of your time and thanks for working on this great project!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
duplicate
feature
feature
good first issue
needs-triage
pull-request
Mirrored from GitHub Pull Request
 qol
support
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop#349
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?