🐛 Bug Report: pocket_id version command does not work without Encryption Key #595

Closed
opened 2026-02-04 20:36:57 +03:00 by OVERLORD · 6 comments
Owner

Originally created by @StrausFuenf on GitHub (Jan 8, 2026).

Reproduction steps

Run the pocketid binary version command without env variables
./pocket-id version

Expected behavior

Version should work without Encryption Key.

Actual Behavior

Command throws error: config error: ENCRYPTION_KEY must be at least 16 bytes long

Pocket ID Version

v.2.0 - 2.1.0

Database

Postgres 16

OS and Environment

Debian 13 LXC

Log Output

Without Env Var:
config error: ENCRYPTION_KEY must be at least 16 bytes long
With Env Var: pocket-id 2.1.0

Originally created by @StrausFuenf on GitHub (Jan 8, 2026). ### Reproduction steps Run the pocketid binary version command without env variables ./pocket-id version ### Expected behavior Version should work without Encryption Key. ### Actual Behavior Command throws error: config error: ENCRYPTION_KEY must be at least 16 bytes long ### Pocket ID Version v.2.0 - 2.1.0 ### Database Postgres 16 ### OS and Environment Debian 13 LXC ### Log Output Without Env Var: config error: ENCRYPTION_KEY must be at least 16 bytes long With Env Var: pocket-id 2.1.0
Author
Owner

@ManuelW77 commented on GitHub (Jan 9, 2026):

I can't get it working even with a encryption key set.
Same error msg: config error: ENCRYPTION_KEY must be at least 16 bytes long

@ManuelW77 commented on GitHub (Jan 9, 2026): I can't get it working even with a encryption key set. Same error msg: config error: ENCRYPTION_KEY must be at least 16 bytes long
Author
Owner

@20pakay commented on GitHub (Jan 11, 2026):

Hi!!!

I've been trying to configure container all weekend and I kept getting the same error (ENCRYPTION_KEY must be at least 16 bytes long) even without ENCRYPTION_KEY variable.
This night I have tried recreate container (pocket-id v2.2.0) with a encryption key set and pocket-id is working properly

pocket-id v2.2.0 was updated 5 hours ago

I hope you get lucky

@20pakay commented on GitHub (Jan 11, 2026): Hi!!! I've been trying to configure container all weekend and I kept getting the same error (ENCRYPTION_KEY must be at least 16 bytes long) even without ENCRYPTION_KEY variable. This night I have tried recreate container (pocket-id v2.2.0) with a encryption key set and pocket-id is working properly pocket-id v2.2.0 was updated 5 hours ago I hope you get lucky
Author
Owner

@StrausFuenf commented on GitHub (Jan 13, 2026):

Hi!!!

I've been trying to configure container all weekend and I kept getting the same error (ENCRYPTION_KEY must be at least 16 bytes long) even without ENCRYPTION_KEY variable. This night I have tried recreate container (pocket-id v2.2.0) with a encryption key set and pocket-id is working properly

pocket-id v2.2.0 was updated 5 hours ago

I hope you get lucky

Hey,

setting up pocket id is not the issue. Its running fine with systemd + env file.

The problem is the version command also needs a encryption key which should work without one.

Same error with 2.2.0

@StrausFuenf commented on GitHub (Jan 13, 2026): > Hi!!! > > I've been trying to configure container all weekend and I kept getting the same error (ENCRYPTION_KEY must be at least 16 bytes long) even without ENCRYPTION_KEY variable. This night I have tried recreate container (pocket-id v2.2.0) with a encryption key set and pocket-id is working properly > > pocket-id v2.2.0 was updated 5 hours ago > > I hope you get lucky Hey, setting up pocket id is not the issue. Its running fine with systemd + env file. The problem is the version command also needs a encryption key which should work without one. Same error with 2.2.0
Author
Owner

@juju4 commented on GitHub (Jan 18, 2026):

Same here. My pocketid ansible role CI has systemd unit works fine but cli command like above or /usr/local/bin/pocket-id --help returns an error while they should not
https://github.com/juju4/ansible-pocketid/actions/runs/21117418231/job/60725001371#step:10:306

It seems to come from f0144584af (diff-26655dfbf33b31bc9c17ec7f3f1577743aac89c6c3fcc6c1e5e0bc23e9c15fb4R17)
ValidateEnvConfig should only happen if running service (not version or help) or if requesting specifically validating config (option which pocket-id has not in cli currently but would be a good addition)

@juju4 commented on GitHub (Jan 18, 2026): Same here. My pocketid ansible role CI has systemd unit works fine but cli command like above or `/usr/local/bin/pocket-id --help` returns an error while they should not https://github.com/juju4/ansible-pocketid/actions/runs/21117418231/job/60725001371#step:10:306 It seems to come from https://github.com/pocket-id/pocket-id/commit/f0144584af90b918a3157a298f1bb95928a117b8#diff-26655dfbf33b31bc9c17ec7f3f1577743aac89c6c3fcc6c1e5e0bc23e9c15fb4R17 ValidateEnvConfig should only happen if running service (not version or help) or if requesting specifically validating config (option which pocket-id has not in cli currently but would be a good addition)
Author
Owner

@kmendell commented on GitHub (Jan 19, 2026):

Fixed here: c62533d388

Will be available in the next version :)

@kmendell commented on GitHub (Jan 19, 2026): Fixed here: https://github.com/pocket-id/pocket-id/commit/c62533d38827adec877fc15d5e6143299a60af92 Will be available in the next version :)
Author
Owner

@juju4 commented on GitHub (Jan 24, 2026):

Thanks!

@juju4 commented on GitHub (Jan 24, 2026): Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#595