Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Plausible #3455

Closed
1 of 2 tasks
jln13x opened this issue Sep 16, 2024 · 4 comments · Fixed by #3705
Closed
1 of 2 tasks

[Bug]: Plausible #3455

jln13x opened this issue Sep 16, 2024 · 4 comments · Fixed by #3705

Comments

@jln13x
Copy link

jln13x commented Sep 16, 2024

Description

Couldnt get Plausible to work and rooted the problem down to SERVICE_BASE64_64_PLAUSIBLE environment variable.

We are referencing this variable from SECRET_KEY_BASE - which is expected to be atleast 64 bytes long but generated variable in SERVICE_BASE64_64_PLAUSIBLE was only 32 bytes long for me. Couldn't find where this variable gets generated.

I fixed it for now by generating a 64 byte string openssl rand -base64 64 by myself and pasting it as the value for SERVICE_BASE64_64_PLAUSIBLE

Minimal Reproduction (if possible, example repository)

Follow the docs https://coolify.io/docs/services/plausible

Exception or Error

Logs from Plausible Container

** (ArgumentError) cookie store expects conn.secret_key_base to be at least 64 bytes

Version

335

Cloud?

  • Yes
  • No
@diogox
Copy link

diogox commented Sep 17, 2024

Same here. Fixed it the same way.

@dreadedhamish
Copy link

Old issue that was marked as fixed but wasn't/
#1449

@AndreiHudovich
Copy link

I just faced the same issue, fixed it with OP's openssl rand -base64 64. Thanks, man!

@andrasbacsai
Copy link
Member

This will be fixed in the upcoming version.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants