[Bug]: White screen when updating planka #528

Closed
opened 2026-02-04 20:12:29 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @Asynchronite on GitHub (Jun 16, 2024).

Where is the problem occurring?

I'm not sure

What browsers are you seeing the problem on?

Chrome, Firefox

Current behaviour

Currently, I tried updating planka by running docker-compose pull, and then docker-compose up -d. The reason why I didn't do docker-compose down first is because I do not want to loose all of my data on the planka.
After which, I only got a blank screen, with a warning that images on the website might be dangerous and uncached or something like that (but that's outside of the scope of this issue)

Desired behaviour

After running docker-compose up -d, I expected my planka instance to boot up again with whatever the new update contained, not with a blank white screen

Steps to reproduce

  1. docker-compose pull
  2. docker-compose up -d
  3. White screen

Other information

Yes, I tried restarting my VPS, still nothing.

Originally created by @Asynchronite on GitHub (Jun 16, 2024). ### Where is the problem occurring? I'm not sure ### What browsers are you seeing the problem on? Chrome, Firefox ### Current behaviour Currently, I tried updating planka by running docker-compose pull, and then docker-compose up -d. The reason why I didn't do docker-compose down first is because I do not want to loose all of my data on the planka. After which, I only got a blank screen, with a warning that images on the website might be dangerous and uncached or something like that (but that's outside of the scope of this issue) ### Desired behaviour After running docker-compose up -d, I expected my planka instance to boot up again with whatever the new update contained, not with a blank white screen ### Steps to reproduce 1. docker-compose pull 2. docker-compose up -d 3. White screen ### Other information Yes, I tried restarting my VPS, still nothing.
Author
Owner

@Asynchronite commented on GitHub (Jun 16, 2024):

I have backups so I can switch to the before and after, but even before I pull, there are a lot of errors when I run docker-compose logs.
Actually, I think it's the same error over and over again.
image

@Asynchronite commented on GitHub (Jun 16, 2024): I have backups so I can switch to the before and after, but even before I pull, there are a lot of errors when I run docker-compose logs. Actually, I think it's the same error over and over again. ![image](https://github.com/plankanban/planka/assets/60348001/ae068b92-ba8e-4c47-9590-4823a51608a0)
Author
Owner

@Asynchronite commented on GitHub (Jun 16, 2024):

Ends up it was my docker-compose.yml and proxy manager. Make sure you have it set to HTTP/HTTPS depending on your NGINX config.

@Asynchronite commented on GitHub (Jun 16, 2024): Ends up it was my docker-compose.yml and proxy manager. Make sure you have it set to HTTP/HTTPS depending on your NGINX config.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#528