Whoops, looks like something went wrong. (No update was made) #1867

Closed
opened 2026-02-05 02:05:38 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @ItsNoted on GitHub (Sep 27, 2020).

When trying to save or edit a page, it fails and gives this error. "Whoops, looks like something went wrong." I have not updated at all since I began using Bookstack. All I did was reboot my server and this began happening.

Tried restarting the container and even rolled back to a backup from yesterday when I know it was working and it still breaks when I edit pages. tried disabling dark mode too as some have suggested and still does it.

This is the first time I've had issues and I saw people were getting this after updating but I haven't updated...

Installed on Ubuntu.

Originally created by @ItsNoted on GitHub (Sep 27, 2020). When trying to save or edit a page, it fails and gives this error. "Whoops, looks like something went wrong." I have not updated at all since I began using Bookstack. All I did was reboot my server and this began happening. Tried restarting the container and even rolled back to a backup from yesterday when I know it was working and it still breaks when I edit pages. tried disabling dark mode too as some have suggested and still does it. This is the first time I've had issues and I saw people were getting this after updating but I haven't updated... Installed on Ubuntu.
Author
Owner

@ssddanbrown commented on GitHub (Sep 27, 2020):

Hi @nashosted, There was an issue in a previous version of the linuxserver.io image where a faulty PHP config file would be written out which would cause this. This config file would then only get picked up after a restart. I believe it has been fixed but, after upgrading the container, you may need to restart the fresh one so that it updates the config file on first run then uses it from second run.

@ssddanbrown commented on GitHub (Sep 27, 2020): Hi @nashosted, There was an issue in a previous version of the linuxserver.io image where a faulty PHP config file would be written out which would cause this. This config file would then only get picked up after a restart. I believe it has been fixed but, after upgrading the container, you may need to restart the fresh one so that it updates the config file on first run then uses it from second run.
Author
Owner

@ssddanbrown commented on GitHub (Jan 16, 2021):

Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.

@ssddanbrown commented on GitHub (Jan 16, 2021): Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#1867