I'm trying to connect to a Postgres instance running on GCP using Metabase Cloud.
Unfortunately I cannot specify neither SSL client key, SSL client cert, nor SSL server cert.
All other sensible solutions have such an option:
Google Data Studio:
My goal was to use your service, as I think it is the best on market, but I cannot even connect our database.
Previous discussions that I've checked (unfortunately all related to self-hosted Metabase versions):
I’m trying to evaluate Metabase and to do so I need to connect to a PostgreSQL 9.6 database over SSL using a self-signed certificate. I first tried with the macOS client, but the error message was too vague, so I then downloaded the .jar file so that I could watch the terminal while attempting to connect.
The cert and key that I use function with other clients and I’ve chmod 0600'd them.
Into the “Additional JDBC connection string options” field, I have tried the following:
I’ve installed the docker version of metabase and I am using docker-compsoe, I am setting up postgres for production however, I need to connect to the remote database using SSL required parameter.
what environment variable should I set?
Hi, my database connection of type postgresql requires client certificate and key ssl connection. I tried many solutions I found, including adding the certificate to the java keystore, adding the certificate to specific folder, adding the certificate to connection string (using environment variables or JDBC connection options through metabase UI) but no luck.
According to this post:
SSL connection to Postgres with self-signed certificate
And I still get a “PSQException: FATAL: connection requi…
I’m trying to set up the metabase application database using our postgres instance.
Unfortunately this postgres instance runs in ssl mode which in turn means I have to
set the query parameter sslmode=require to get a valid connection string.
Is there any mechanism, hack or env var to be set to set additional jdbc options?
Setting up a database via the web frontend is no problem it only effects the initialization of
the applications meta database in the setup process…
BTW: I’m running …
... and others