Closed lucasplcorrea closed 6 days ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
In regard to your volumes:
volumes:
- /path/to/bookstack/config:/config
- app_data:/var/www/html/uploads
You'd probably want that first line set to an actual convenient path on your host.
No idea what that second /var/www/html/uploads
entry is doing, where did you get that from?
We've seen it a few times now, I think there's some guide somewhere giving bad advice.
I think your issue is the APP_KEY, it should include the base64:
prefix
I'm sorry, I asked GPT to help me generate a docker-compose since I was already facing many difficulties with this container, and I ended up missing this part. In Windows, how would this path look correctly?
I would like the data to remain persistent because I intend to migrate this container later to an Ubuntu server with Portainer.
I temporarily removed the lines related to the volume, and put bookstack in debu mode, I received the following information:
RuntimeException Unsupported cipher or incorrect key length. Supported ciphers are: aes-128-cbc, aes-256-cbc, aes-128-gcm, aes-256-gcm.
PHP Version: 8.3.12 BookStack Version: v24.10 Theme Configured:
0 /app/www/vendor/laravel/framework/src/Illuminate/Encryption/EncryptionServiceProvider.php(32): Illuminate\Encryption\Encrypter->__construct()
Why use ChatGPT for something that needs to be customized for you? We already provide a sample compose yaml with instructions and details on what everything is
We've seen it a few times now, I think there's some guide somewhere giving bad advice.
I think your issue is the APP_KEY, it should include the
base64:
prefix
Legend!
I was ignoring the prefix, believing that because it is a prefix, it should not be considered.
Why use ChatGPT for something that needs to be customized for you? We already provide a sample compose yaml with instructions and details on what everything is
I used chatgpt because I had never used docker, nor the application, and the week before, it worked the first time, so I decided to try to get help from whoever helped generate the file.
Adding the base64 prefix: and then the generated key, works like a charm!
I'm going to close the topic and try to return to the backup I had created before all this problem happened.
We strongly advise against using Chatgpt or similar tools for this sort of thing because all they really do is guess and they frequently get it wrong, even if it technically works.
Is there an existing issue for this?
Current Behavior
A while ago I uploaded a bookstack docker container and everything worked fine, but I needed to run docker-compose again and I can't get it to work anymore.
Among all the errors I faced and managed to fix, the last one I was unsuccessful in was a 500 error at the end of the installation, only a message is displayed:
" An Error Occurred An unknown error occurred Return to home "
In my browser console I get:
GET http://192.168.222.108:6875/login 500 (Internal Server Error)
The app and db logs don't show me much:
app:
db:
My docker-compose looks like this:
Expected Behavior
No response
Steps To Reproduce
I create the docker-compose file with the description above:
I access the folder via terminal, and type docker-compose up -d
Environment
CPU architecture
x86-64
Docker creation
Container logs