Docker compose fails

[thenitai]

The latest docker compose on here fails. Replacing the plausible pull with plausible/analytics:v2.0 makes it work again.

[ruslandoga]

👋 @thenitai

Could you explain a bit more please? The current docker-compose.yml uses plausible/analytics:v2.0

[thenitai]

Look at the v2.1 branch. The plausible link in the docker-compose file doesn't work

[ruslandoga]

Ah, thank you! I've updated it to a release candidate.

[xiaohanyu]

Hello, I use v2.1.0 branch's docker-compose.yml and it reports with following error:

docker-compose -f compose.production.yml logs -f plausible
plausible-plausible-1  | ERROR! Config provider Config.Reader failed with:
plausible-plausible-1  | ** (ArgumentError) incorrect padding
plausible-plausible-1  |     (elixir 1.16.0) lib/base.ex:735: Base.decode64base!/2
plausible-plausible-1  |     /app/releases/0.0.1/runtime.exs:163: (file)
plausible-plausible-1  |     (elixir 1.16.0) src/elixir.erl:405: :elixir.eval_external_handler/3
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:750: :erl_eval.do_apply/7
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:1026: :erl_eval.expr_list/7
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:456: :erl_eval.expr/6
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:539: :erl_eval.expr/6
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:325: :erl_eval.expr/6
plausible-plausible-1  |
plausible-plausible-1  |
plausible-plausible-1  | Runtime terminating during boot ({#{message=><<"incorrect padding">>,'__struct__'=>'Elixir.ArgumentError','__exception__'=>true},[{'Elixir.Base','decode64base!',2,[{file,"lib/base.ex"},{l
ine,735}]},{elixir_eval,'__FILE__',1,[{file,"/app/releases/0.0.1/runtime.exs"},{line,163}]},{elixir,eval_external_handler,3,[{file,"src/elixir.erl"},{line,405}]},{erl_eval,do_apply,7,[{file,"erl_eval.erl"},{line,
750}]},{erl_eval,expr_list,7,[{file,"erl_eval.erl"},{line,1026}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,456}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,539}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},
{line,325}]}]})
plausible-plausible-1  |
plausible-plausible-1  | Crash dump is being written to: erl_crash.dump...done
plausible-plausible-1  | ERROR! Config provider Config.Reader failed with:
plausible-plausible-1  | ** (ArgumentError) incorrect padding
plausible-plausible-1  |     (elixir 1.16.0) lib/base.ex:735: Base.decode64base!/2
plausible-plausible-1  |     /app/releases/0.0.1/runtime.exs:163: (file)
plausible-plausible-1  |     (elixir 1.16.0) src/elixir.erl:405: :elixir.eval_external_handler/3
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:750: :erl_eval.do_apply/7
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:1026: :erl_eval.expr_list/7
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:456: :erl_eval.expr/6
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:539: :erl_eval.expr/6
plausible-plausible-1  |     (stdlib 5.2) erl_eval.erl:325: :erl_eval.expr/6
plausible-plausible-1  |

v2.0 works well.

Just FYI.

@ruslandoga

[ruslandoga]

👋 @xiaohanyu

Your TOTP_VAULT_KEY (added in v2.1.0) seems to be invalid, more info on it is in the "Quick start" https://github.com/plausible/community-edition/tree/v2.1.0#quick-start section of the guide.

The error comes from https://github.com/plausible/analytics/blob/cc867396b237c10ea996783844dc19e3e110aa73/config/runtime.exs#L163

[xiaohanyu]

@ruslandoga works like a charm after change TOTP_VAULT_KEY to be 32 chars long.

May I know why it mandates 32 chars for TOTP_VAULT_KEY?

Meanwhile, I suggest to declare this requirements in the doc to avoid future confusions.

[ruslandoga]

Meanwhile, I suggest to declare this requirements in the doc to avoid future confusions.

Right, will do! Thank you for the suggestions.

May I know why it mandates 32 chars for TOTP_VAULT_KEY?

@zoldar could help with this one out please?

[zoldar]

May I know why it mandates 32 chars for TOTP_VAULT_KEY?

This requirement comes from the library we use for vaulting the TOTP secrets in the database (so that they remain encrypted "at rest") - Cloak. This in turn is caused by specific requirements for AES key used for encryption and decryption in the underlying core OTP :crypto API.