-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank screen after upgrade #550
Comments
Is it possible you've run out of disk space? It can cause this problem. |
Based on what I can see, it appears I've got a whole ~7GB of space free. |
I actually ran into this problem, is there any solution to get it working again? update: I've tried a lot of things, nothing helped. I restored from backup. |
Hey @BrendanTCC, it's a longshot, but you can try |
But it's not the sense of this, to deactivate react - it should work, as it worked before. After my upgrade to the latest version, I have the same issue. Since then everything worked fine. |
hey, apologies for radio silence for so long. ended up deleting the original container and such and gave up on it for god knows how long... until about a couple of months ago. did an upgrade again, but this time the vm on which i was running the container ran out of space mid-upgrade. to make matters worse, like an idiot i never took backups so i've come full circle. sadly trying to turn off react didn't work this time. that said, i hoped trying to rollback DB migrations then getting the app to try again would help but alas... no dice. i think i accidentally made things worse. what doesn't help as well is that any workarounds (and i suppose belittling for my goofs) appreciated. |
update: i figured out the migrations rollback issue for myself - managed to get into the container and run at the moment, i'm not comfortable completely shutting down the container given i've accidentally pruned my Linkwarden instance after not realizing it hadn't brought itself back up. with this in mind, any suggestions for going in and otherwise suspending billing for recurring invoices are much appreciated. |
Setup information
docker-compose
Describe the bug
To put things simply, seeing a blank screen after upgrading to latest, just like as observed in #549.
To reproduce
Steps to reproduce the behavior:
docker-compose down
docker-compose pull
docker-compose up
(as normal)Expected behavior
See, at the very least, a login screen
Logs
Docker/Kubernetes/Helm:
docker version
:Additional context
PLEASE NOTE: Browser console comes back with quite literally nothing, and
~/dockerfiles/docker/app/storage/logs/laravel.log
only has the following:The text was updated successfully, but these errors were encountered: