Unsupported cipher or incorrect key length.

[0b00001111]

Checklist

• I have read the docs.
• I have searched open and closed issues.

Deployment Environment

Docker Compose

Description

Hello, sorry if I'm being stupid or have overlooked the solution somewhere in the documentation.

To the setup: Proxmox Server, https://community-scripts.github.io/ProxmoxVE/scripts?id=docker installed (including portainer and post-installed composer). Running so far. Then I wanted to use Portainer according to the instructions under https://docs.speedtest-tracker.dev/getting-started/installation/using-docker-compose .

So I generate the APP_KEY via echo -n 'base64:'; openssl rand -base64 32; and get for example base64:f7w7DWWlQ4ez5RMzT9inSVcpzE6zHAamvHjGKCXSFXo=. I write this value under the corresponding entry as environment - APP_KEY=base64:f7w7DWWlQ4ez5RMzT9inSVcpzE6zHAamvHjGKCXSFXo= from the SQLite example.

Then deploy the whole thing in Portainer (with debug flag).

I get Error 500 with Unsupported cipher or incorrect key length. Supported ciphers are: aes-128-cbc, aes-256-cbc, aes-128-gcm, aes-256-gcm.
Source of error: app/Http/Middleware/AllowedIpAddressesMiddleware.php :19

While searching the internet I found this:
[https://stackoverflow.com/questions/44619357/laravel-the-only-supported-ciphers-are-aes-128-cbc-and-aes-256-cbc-with-the-cor] it says that possibly a base64 key with 32 characters would help if I create one with this length: echo -n 'base64:'; openssl rand -base64 24; is still not possible.

echo -n 'base64:'; openssl rand -base64 24; execute in container via console does not work either, it tells me root@f1a29fd96131:/# php artisan key:generate Could not open input file: artisan

At this point I can't figure out what the problem might be. Can someone please help me? I am a noob in such things :(

Anything else?

No response

[alexjustesen]

Running echo -n 'base64:'; openssl rand -base64 32; is the correct command for generating a key, make sure to restart your app container too.

[0b00001111]

Ok thank you for verifiying that. I allway re-pulled und re-deployed the container. Strange thing: now it works, before it has definitely not (i tried ~10 times). Is there a maximum time between generation of the base64 and the deployment? Or is only the last generated base64 valid and I have accidentally overwritten it myself by generating other variants??

[alexjustesen]

It was probably caught up in the cache 🤷‍♂️