Open BrendanTCC opened 11 months ago
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.
Is it possible you've run out of disk space? It can cause this problem.
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 UPDATE accounts SET set_react_as_default_ap = 0;
on the db container. The react app causes the blank screen.
Hey @BrendanTCC, it's a longshot, but you can try
UPDATE accounts SET set_react_as_default_ap = 0;
on the db container. The react app causes the blank screen.
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 dockerfiles-app-1
keeps restarting after i (admittedly quite stupidly) restarted the entire stack so i can't even get back in and get the migration dump to try and whip up a reversal script.
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 artisan migrate:refresh
. Unfortunately, that hasn't solved the blank screen issue.
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.
Same here. Have been running fine for almost a year, did a pull to upgrade to the latest and now I get a white screen. Nginx shows 200's for every request and the app shows 200s as well but every request is logged as just '/index.php'.
Tried setting set_react_as_default_ap = 0
, 15gb free space
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
:Server: Engine: Version: 24.0.5 API version: 1.43 (minimum version 1.12) Go version: go1.20.3 Git commit: 24.0.5-0ubuntu1~22.04.1 Built: Mon Aug 21 19:50:14 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.12-0ubuntu1~22.04.3 GitCommit:
runc: Version: 1.1.4-0ubuntu1~22.04.3 GitCommit:
docker-init: Version: 0.19.0 GitCommit:
[2023-12-18 11:54:57] production.INFO: finished running composer install
[2023-12-18 11:54:57] production.INFO: cleared config
[2023-12-18 11:54:57] production.INFO: view cleared
[2023-12-18 11:54:57] production.INFO: queue restarted
[2023-12-18 11:54:58] production.INFO: Sent for version check