Could not connect. Will try again. Cannot read properties of undefined (reading 'name')

[nitanmarcel]

I'm not able to connect to my postgres database via connection string as the terminal keeps spamming with the following error:

app_1  | 2023-11-15 09:36:04: App: Content driver: { type: 1 }
app_1  | 2023-11-15 09:36:04: App: Content driver (fallback): null
app_1  | 2023-11-15 09:36:04: App: Trying to connect to database...
app_1  | 2023-11-15 09:36:05: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name')
app_1  | 2023-11-15 09:36:06: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name')
app_1  | 2023-11-15 09:36:07: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name')
app_1  | 2023-11-15 09:36:08: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name')
^CGracefully stopping... (press Ctrl+C again to force)
Stopping joplin_app_1 ... done

I am using the docker image with the tag latest, I tried with older docker image and the result is the same

version: '3'
services:
    app:
        image: joplin/server:2.10.6-beta
        ports:
            - "3000:3000"
        restart: unless-stopped
        environment:
            - APP_PORT=3000
            - APP_NAME=Notes
            - SIGNUP_ENABLED=false
            - APP_BASE_URL=https://board.marcelnitan.online
            - DB_CLIENT=pg
            - NODE_TLS_REJECT_UNAUTHORIZED=0
            - POSTGRES_CONNECTION_STRING=postgresql://user:password@ep-calm-
snow-568677.eu-central-1.aws.neon.tech/notes?sslmode=require

[girish]

@nitanmarcel This is the forum for discussing the Joplin package on Cloudron . For other deployments, you have to discuss in the upstream project. See https://github.com/laurent22/joplin#community

[nitanmarcel]

@girish Thanks ^^ I've seen a similar post where the solution didn't helped on this and I though it was a good place to ask this.

In the mean time I also issued this on github, about another database but with the same error and got a response that it's not a bug and indeed these type of databases, even if they use postgres are not supported.

Guess I'll keep looking for alternatives that would fit my use case.

Thanks for answering