Issue Keila Docker

[omokobsen]

Server operating system version

Ubuntu 24.04

Plesk version and microupdate number

18.0.56

Hi there,
is anyone able to help setting up a Keila (Mailchimp alternative) as Docker Container?

Steps to reproduce
- install docker in plesk
- set up new subdomain e.g. keila.domain.com
- set up mail adress for keila e.g. [email protected]
- run pentacent/keila
- config as described here
Error log

19:52:49.671 [info] Loading 147 CA(s) from :otp store
19:52:49.672 [warning] Captcha not configured.
Keila will fall back to using hCaptcha’s staging configuration.

To configure a captcha, use the following environment variables:

- CAPTCHA_SITE_KEY
- CAPTCHA_SECRET_KEY
- CAPTCHA_URL (defaults to https://hcaptcha.com/siteverify or https://api.friendlycaptcha.com/api/v1/siteverify)
- CAPTCHA_PROVIDER (defaults to hCaptcha, unless set to 'friendly_captcha')

19:52:49.672 [warning] You have not configured a Hashid salt. Defaulting to
:crypto.hash(:sha256, SECRET_KEY_BASE <> "hashid_salt") |> Base.url_encode64()

19:52:49.672 [warning] You have not configured a directory for user uploads.
Default directory "./uploads" will be used.

If want to store uploads in a different directory you can set
USER_CONTENT_DIR

19:52:49.672 [warning] You have not configured a separate URL for untrusted content uploaded by
users.

If you serve user uploads on a different domain, you can set
USER_CONTENT_BASE_URL

19:52:49.718 [error] Postgrex.Protocol (#PID<0.2613.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
19:52:49.718 [error] Postgrex.Protocol (#PID<0.2614.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused
19:52:51.717 [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 :keila, Keila.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

19:52:51.717 [notice] Application keila exited: exited in: Keila.Application.start(:normal, [])
    ** (EXIT) an exception was raised:
        ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2000ms. 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.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
            (elixir 1.15.8) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
            (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
            (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
            (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
            (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
            (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
            (keila 0.15.0) lib/keila/release_tasks.ex:28: Keila.ReleaseTasks.migrate/0
Runtime terminating during boot (terminating)

Crash dump is being written to: erl_crash.dump...done

I think this is the issue:
19:52:49.718 [error] Postgrex.Protocol (#PID<0.2613.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (localhost:5432): connection refused - :econnrefused

But I need help to solve it.

 

[omokobsen]

Please support