Unable to use digitalocean managed database

[halkeye]

I'm not sure how to set show_sensitive_data_on_connection_error

/app $ export DATABASE_URL='postgresql://username:password@private-dok8s-sfo2-[snip].b.db.ondigitalocean.com:port/plausible?ssl=require'
/app $ ./migrate.sh
Loading plausible..
Starting dependencies..
Starting repos..
02:07:29.689 [error] :gen_statem #PID<0.149.0> terminating
** (RuntimeError) connect raised CaseClauseError exception. The exception details are hidden, as they may contain sensitive data such as database credentials. You may set :show_sensitive_data_on_connection_error to true when starting your connection if you wish to see all of the details
    (postgrex 0.19.3) lib/postgrex/protocol.ex:90: Postgrex.Protocol.connect/1
    (db_connection 2.7.0) lib/db_connection/connection.ex:74: DBConnection.Connection.handle_event/4
    (stdlib 6.2.2) gen_statem.erl:3737: :gen_statem.loop_state_callback/11
    (stdlib 6.2.2) proc_lib.erl:329: :proc_lib.init_p_do_apply/3
Queue: [internal: {:connect, :init}]
Postponed: []
02:07:29.689 [error] :gen_statem #PID<0.148.0> terminating
** (RuntimeError) connect raised CaseClauseError exception. The exception details are hidden, as they may contain sensitive data such as database credentials. You may set :show_sensitive_data_on_connection_error to true when starting your connection if you wish to see all of the details
    (postgrex 0.19.3) lib/postgrex/protocol.ex:90: Postgrex.Protocol.connect/1
    (db_connection 2.7.0) lib/db_connection/connection.ex:74: DBConnection.Connection.handle_event/4
    (stdlib 6.2.2) gen_statem.erl:3737: :gen_statem.loop_state_callback/11
    (stdlib 6.2.2) proc_lib.erl:329: :proc_lib.init_p_do_apply/3
Queue: [internal: {:connect, :init}]
Postponed: []
** (EXIT from #PID<0.94.0>) shutdown

I tried most combos of ssl=true, ssl=require, ssl=true&ssl=verify-full&sslrootcert=/ca-certificate.crt

ssl=true by it self gives me

02:11:39.371 [warning] setting ssl: true on your database connection offers only limited protection, as the server's certificate is not verified. Set "ssl: [cacertfile: path/to/file]" instead
02:11:39.371 [warning] setting ssl: true on your database connection offers only limited protection, as the server's certificate is not verified. Set "ssl: [cacertfile: path/to/file]" instead
02:11:39.570 [error] Postgrex.Protocol (#PID<0.149.0>) failed to connect: ** (DBConnection.ConnectionError) ssl connect: Options (or their values) can not be combined: [{verify,verify_peer},
                                                {cacerts,undefined}] - {:options, :incompatible, [verify: :verify_peer, cacerts: :undefined]}
02:11:39.570 [error] Postgrex.Protocol (#PID<0.148.0>) failed to connect: ** (DBConnection.ConnectionError) ssl connect: Options (or their values) can not be combined: [{verify,verify_peer},
                                                {cacerts,undefined}] - {:options, :incompatible, [verify: :verify_peer, cacerts: :undefined]}

[halkeye]

I did download the code and set the flag, it looks like verify-full or require isn't a switch statement it understands

env DATABASE_CACERTFILE=/ca-certificate.crt

gets me further

Loading plausible..
Starting dependencies..
Starting repos..
03:15:05.321 [warning] ignoring `ssl=true` parameter in URL because `ssl` is already set in the configuration: [cacertfile: "/ca-certificate.crt", verify: :verify_peer]
03:15:05.352 [warning] ignoring `ssl=true` parameter in URL because `ssl` is already set in the configuration: [cacertfile: "/ca-certificate.crt", verify: :verify_peer]
03:15:05.356 [warning] ignoring `ssl=true` parameter in URL because `ssl` is already set in the configuration: [cacertfile: "/ca-certificate.crt", verify: :verify_peer]
03:15:05.356 [warning] ignoring `ssl=true` parameter in URL because `ssl` is already set in the configuration: [cacertfile: "/ca-certificate.crt", verify: :verify_peer]
03:15:05.376 [error] Ch.Connection (#PID<0.156.0>) failed to connect: ** (Mint.TransportError) non-existing domain
03:15:05.376 [error] Ch.Connection (#PID<0.155.0>) failed to connect: ** (Mint.TransportError) non-existing domain
03:15:05.849 [warning] ignoring `ssl=true` parameter in URL because `ssl` is already set in the configuration: [cacertfile: "/ca-certificate.crt", verify: :verify_peer]
03:15:07.079 [error] Ch.Connection (#PID<0.155.0>) failed to connect: ** (Mint.TransportError) non-existing domain
03:15:07.258 [error] Ch.Connection (#PID<0.156.0>) failed to connect: ** (Mint.TransportError) non-existing domain
03:15:11.044 [error] Ch.Connection (#PID<0.155.0>) failed to connect: ** (Mint.TransportError) non-existing domain
03:15:11.351 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :plausible, Plausible.IngestRepo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 5306ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:

  1. Ensuring your database is available and that you can connect to it
  2. Tracking down slow queries and making sure they are running fast enough
  3. Increasing the pool_size (although this increases resource consumption)
  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval

See DBConnection.start_link/2 for more information

    (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:1098: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.13.2) lib/ecto/adapters/sql.ex:1219: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.13.2) lib/ecto/migrator.ex:779: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.13.2) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.13.2) lib/ecto/migrator.ex:485: Ecto.Migrator.migrations/3
    (plausible 0.0.1) lib/plausible_release.ex:100: anonymous fn/1 in Plausible.Release.all_pending_migrations/1
    nofile:1: (file)

[halkeye]

Turns out it was because of my debugging that schema migraitons was created, droprping it seems to work

** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 5306ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:

  1. Ensuring your database is available and that you can connect to it
  2. Tracking down slow queries and making sure they are running fast enough
  3. Increasing the pool_size (although this increases resource consumption)
  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval

pays to read error messages.
looks like for digitalocean, ssl=true and DATABASE_CACERTFILE env variable set