mirror of
https://github.com/Drop-OSS/drop-app.git
synced 2026-07-18 18:44:30 -04:00
[GH-ISSUE #186] [BUG] CA not initialized on nightly version behind nginx #177
Reference in New Issue
Block a user
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?
Originally created by @Visirt on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/186
Describe the bug
While trying to run the nightly version of drop and running a Windows source-code compiled version of drop-app.
When trying to log into the drop server with the app, after clicking on Authorize and getting redirected to the drop app, the app displays the following error:
Authentication failed
Drop encountered an error while connecting to your instance. Error: server returned invalid response: 500, Server Error
And the following error appears on the drop server logs
[request error] [unhandled] [POST] https://localhost:4000/api/v1/client/auth/handshake
H3Error: CA not initialised
at useCertificateAuthority (file:///app/app/server/chunks/nitro/nitro.mjs:1:1089860)
... 3 lines matching cause stack trace ...
at async Server. (file:///app/app/server/chunks/nitro/nitro.mjs:1:98901) {
cause: Error: CA not initialised
at useCertificateAuthority (file:///app/app/server/chunks/nitro/nitro.mjs:1:1089860)
at Object.handler (file:///app/app/server/chunks/routes/api/v1/client/auth/handshake.post.mjs:1:1614)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921)
at async Server. (file:///app/app/server/chunks/nitro/nitro.mjs:1:98901),
statusCode: 500,
fatal: false,
unhandled: true,
statusMessage: undefined,
data: undefined
}
The drop is running behind a Docker LXC on Proxmox, running in the same server as the latest drop server, and using Nginx Proxy Manager as a reverse proxy with SSL enabled.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The expected behavior is to successfully authorize the client to the drop server.
Screenshots
Desktop (please complete the following information):
Additional context
Here's the full output of the docker server
[Drop] performing migrations...
[dotenv@17.2.3] injecting env (0) from .env -- tip: 🔄 add secrets lifecycle management: https://dotenvx.com/ops
Loaded Prisma config from prisma.config.ts.
Prisma schema loaded from prisma.
Datasource "db": PostgreSQL database "drop", schema "public" at "postgres:5432"
117 migrations found in prisma/migrations
┌─────────────────────────────────────────────────────────┐
│ Update available 7.3.0 -> 7.4.1 │
│ Run the following to update │
│ npm i --save-dev prisma@latest │
│ npm i @prisma/client@latest │
└─────────────────────────────────────────────────────────┘
No pending migrations to apply.
Listening on http://[::]:4000
[16:25:04.373] INFO (66): enabled metadata provider: Steam
[16:25:04.374] INFO (66): enabled metadata provider: PCGamingWiki
[16:25:04.374] WARN (66): skipping metadata provider setup: Error: Missing config item IGDB_CLIENT_ID for IGDB
[16:25:04.387] INFO (service-torrential/66): service launched
[16:25:04.396] INFO (service-nginx/66): service launched
[16:25:04.466] WARN (66): Error: Missing all necessary OIDC configuration:
OIDC_AUTHORIZATION: undefined
OIDC_TOKEN: undefined
OIDC_USERINFO: undefined
OIDC_SCOPES: undefined
OIDC_ISSUER: undefined
OIDC_JWKS: undefined
[16:25:04.472] INFO (66): enabled auth: Simple
[16:25:04.472] INFO (66): AuthManager initialized
[16:25:04.970] INFO (service-torrential/66): INFO [torrential] using 2 threads
INFO [torrential::server] created client subroutine
INFO [torrential] started depot server
[16:25:04.971] ERROR (service-nginx/66): nginx: [alert] could not open error log file: open() "/data/nginx/logs/error.log" failed (2: No such file or directory)
[16:25:04.972] INFO (service-torrential/66): connected to torrential socket
[16:25:04.973] INFO (service-torrential/66): service healthy
[unhandledRejection] Could not create backend for path.
[16:25:05.153] INFO (service-torrential/66): INFO [torrential::droplet::manifest] using 1 import threads
WARN [torrential::droplet] manifest generation failed with err: Could not create backend for path.
[request error] [unhandled] [POST] https://localhost:4000/api/v1/client/auth/handshake
H3Error: CA not initialised
at useCertificateAuthority (file:///app/app/server/chunks/nitro/nitro.mjs:1:1089860)
... 3 lines matching cause stack trace ...
at async Server. (file:///app/app/server/chunks/nitro/nitro.mjs:1:98901) {
cause: Error: CA not initialised
at useCertificateAuthority (file:///app/app/server/chunks/nitro/nitro.mjs:1:1089860)
at Object.handler (file:///app/app/server/chunks/routes/api/v1/client/auth/handshake.post.mjs:1:1614)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921)
at async Server. (file:///app/app/server/chunks/nitro/nitro.mjs:1:98901),
statusCode: 500,
fatal: false,
unhandled: true,
statusMessage: undefined,
data: undefined
}
@DecDuck commented on GitHub (Feb 22, 2026):
When was the last time you pulled nightly? We fixed an issue along these lines around a week ago.
@Visirt commented on GitHub (Feb 22, 2026):
I did the last pull 3 hours ago
@DecDuck commented on GitHub (Feb 22, 2026):
If you restart the server, does the issue go away? We think we've found a related issue.
@Visirt commented on GitHub (Feb 23, 2026):
I restarted the entire docker service and the error is still happenning
I also just restarted the entire LXC containing multiple dockers and the error is still happening
Here's once again the output to the drop server.
[Drop] performing migrations...
[dotenv@17.2.3] injecting env (0) from .env -- tip: ⚙️ specify custom .env file path with { path: '/custom/path/.env' }
Loaded Prisma config from prisma.config.ts.
Prisma schema loaded from prisma.
Datasource "db": PostgreSQL database "drop", schema "public" at "postgres:5432"
117 migrations found in prisma/migrations
No pending migrations to apply.
Listening on http://[::]:4000
[11:17:26.680] INFO (72): enabled metadata provider: Steam
[11:17:26.680] INFO (72): enabled metadata provider: PCGamingWiki
[11:17:26.681] WARN (72): skipping metadata provider setup: Error: Missing config item IGDB_CLIENT_ID for IGDB
[11:17:26.694] INFO (service-torrential/72): service launched
[11:17:26.706] INFO (service-nginx/72): service launched
[11:17:26.772] WARN (72): Error: Missing all necessary OIDC configuration:
OIDC_AUTHORIZATION: undefined
OIDC_TOKEN: undefined
OIDC_USERINFO: undefined
OIDC_SCOPES: undefined
OIDC_ISSUER: undefined
OIDC_JWKS: undefined
[11:17:26.777] INFO (72): enabled auth: Simple
[11:17:26.777] INFO (72): AuthManager initialized
[11:17:27.269] INFO (service-torrential/72): INFO [torrential] using 2 threads
INFO [torrential::server] created client subroutine
INFO [torrential] started depot server
[11:17:27.269] ERROR (service-nginx/72): nginx: [alert] could not open error log file: open() "/data/nginx/logs/error.log" failed (2: No such file or directory)
[11:17:27.274] INFO (service-torrential/72): connected to torrential socket
[11:17:27.277] INFO (service-torrential/72): service healthy
[unhandledRejection] Could not create backend for path.
[11:17:27.510] INFO (service-torrential/72): INFO [torrential::droplet::manifest] using 1 import threads
WARN [torrential::droplet] manifest generation failed with err: Could not create backend for path.
[request error] [unhandled] [POST] https://localhost:4000/api/v1/client/auth/handshake
H3Error: CA not initialised
at useCertificateAuthority (file:///app/app/server/chunks/nitro/nitro.mjs:1:1089860)
... 3 lines matching cause stack trace ...
at async Server. (file:///app/app/server/chunks/nitro/nitro.mjs:1:98901) {
cause: Error: CA not initialised
at useCertificateAuthority (file:///app/app/server/chunks/nitro/nitro.mjs:1:1089860)
at Object.handler (file:///app/app/server/chunks/routes/api/v1/client/auth/handshake.post.mjs:1:1614)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async Object.handler (file:///app/app/server/chunks/nitro/nitro.mjs:1:95921)
at async Server. (file:///app/app/server/chunks/nitro/nitro.mjs:1:98901),
statusCode: 500,
fatal: false,
unhandled: true,
statusMessage: undefined,
data: undefined
}
@DecDuck commented on GitHub (Feb 23, 2026):
What image tag are you using? And can you provide the version you're using (it's in the footer)?
@Visirt commented on GitHub (Feb 23, 2026):
I'm using:
drop server version: v0.4.0-nightly.2026.02.22
If it'll be helpful I can try finding out which commit broke this and even try fixing it
@DecDuck commented on GitHub (Feb 23, 2026):
Yeah that'd be super helpful, I can't seem to replicate this bug on my own.
@DecDuck commented on GitHub (Feb 24, 2026):
Found the issue! It was a typo lol.
@DecDuck commented on GitHub (Feb 24, 2026):
It'll be fixed and released soon with the first v0.4.0 release candidate