mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 16:49:47 +03:00
Error while Picture upload after Backup and restore on new Maschine #4918
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stothew on GitHub (Aug 19, 2024).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
Hello together,
I think my migration process is missing a step but can´t point it out.
I switched to a new Ubuntu server 24.04 and wanted to migrate Bookstack to it.
What I did:
Now all seems to be nice. All data / old pictures are here and Bookstack is up to date. But if I try to paste a picture or upload it via Interface I get "Internal Server error"
What did I miss?
May something with the App key? But could find any info about "how to switch to the old APP key"
Any hint is welcome :)
Thank you!
Exact BookStack Version
BookStack v24.05.3
Log Content
No response
Hosting Environment
Self-hosted, VMware, Ubuntu 24.04, used official installation script, all up to date
@ssddanbrown commented on GitHub (Aug 19, 2024):
Hi @stothew,
Doubt that's relevant here, since the APP_KEY is not used for images. That said, it is used for other things like MFA details so you might want to sure this is the same as before (Ensure it's the same as your old
.envAPP_KEYvalue).This will likely get logged to the webserver log.
Watch the apache error log and reproduce the error scenario, then share back any lines that are logged:
The lines from that (if any) should hold some clues to understand why the error is thrown.
@stothew commented on GitHub (Aug 19, 2024):
Hi ssddanbrown,
Thank you for the fast replay!
Unfortunately reproducing the error (upload a picture) doesn´t add any lines to my apache error log.
here is the log:
As you can see I tried to restart the whole server but without luck.
@ssddanbrown commented on GitHub (Aug 19, 2024):
Ah, okay, for that error try watching the app log instead:
Log messages will start with a timestamp, and the first few lines of each message are most relevant.
@stothew commented on GitHub (Aug 19, 2024):
Unfortunately, there are also no lines added while uploading a picture.
output of : tail -f /var/www/bookstack/storage/logs/laravel.log
but this was the stack trace of an older error. it was created while the Database user pw was not changed.
So... No, error from today. No lines were added while uploading pictures....
Any other Ideas? Thank you!
@stothew commented on GitHub (Aug 20, 2024):
I noticed the owner changed completely over the different versions.
But when I change the permissions the picture upload says I need to check the write permissions... so I guess it was okay in first place..
Any other/saver way to update from a really old Bookstack version...? do I need to go back?
@ssddanbrown commented on GitHub (Aug 20, 2024):
Updating from old versions is fine.
php artisan migratewhat does that output?@stothew commented on GitHub (Aug 20, 2024):
Thank you so much for the help.
here are the requested outputs:
Its Firefox 129.0.1 (64Bit)
@ssddanbrown commented on GitHub (Aug 20, 2024):
Thanks, no extra clues there though.
While in the browser developer tools, can you open the "Network" tab.
Then reproduce the error. You should see an extra (likely red) line appear in this tab after attempting image upload.
Click on that line, then view the "response" tab in the sidebar which appears, then screenshot what you see there.
@stothew commented on GitHub (Aug 20, 2024):
Let me know if I can do anything else.
@ssddanbrown commented on GitHub (Aug 20, 2024):
Okay, so that confirms an app-level error.
What's the output of running
ls -alh /var/www/bookstack/storage/logs/?@stothew commented on GitHub (Aug 20, 2024):
@ssddanbrown commented on GitHub (Aug 20, 2024):
Okay, the log is lacking permissions.
Update with
chown user:www-data /var/www/bookstack/storage/logs/laravel.log.Then, retry watching the app logs while reproducing the error (
tail -f /var/www/bookstack/storage/logs/laravel.log)@stothew commented on GitHub (Aug 20, 2024):
Now it is adding lines:
It says no write permission, but as I said this morning changing the storage permission did not help...
Why did the installation Script not set this? Whats the correct permissions to run smoothly?
Thanks again!
@ssddanbrown commented on GitHub (Aug 20, 2024):
@stothew Those commands are setting permissions on a
/storagefolder, which (if exists) would not be part of your BookStack install (since you're specifying a folder at the root of your filesystem).It does set some default permissions, but when you copied in old files, or had errors via commands, that may have interfered.
You can follow our example permissions approach here:
https://www.bookstackapp.com/docs/admin/filesystem-permissions/#example-permissions-approach
Be sure to replace
barryin those commands withuser(I'm assuming going by your screenshots above).@stothew commented on GitHub (Aug 20, 2024):
Ah, okay! I only set it to the storage folder because the old server had the permissions like that. With the permissions set as described in the link, all works fine! May the Link is worth a mention on the Backup and Restore page? after unpacking tarball, reapply the file permissions :)
Thank you so much for digging into my problem!
I have used Bookstack for years now and would be very sad to get problems with all that documentation.
Thank you for this wonderful piece of Software, and thanks again for the great help with troubleshooting.
Keep up the good work.
if I can help someday, let me know.
@ssddanbrown commented on GitHub (Oct 14, 2024):
Good to hear you got things working, I'll therefore close this off.