mirror of
https://github.com/plankanban/planka.git
synced 2026-02-05 00:39:58 +03:00
Newest build doesn't show anything #20
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 @Trollwut on GitHub (Aug 22, 2020).
Hey mates!
Yesterday I pulled for updates and up-d'd it. Now there is an empty web page showing, although everything runs "fine".
docker-compose logsdoesn't show anything specific, in fact it shows the same messages as always:The build I'm using is from docker-hub with commit source
767d395.Is there any way to up a new/old build, until this is fixed?
Also, this is the source code of the client web page:
@Trollwut commented on GitHub (Aug 22, 2020):
Oh I also see that my volumes now are empty...
good that I used an external database, so at least all cards aare there
@meltyshev commented on GitHub (Aug 22, 2020):
Hi! I trying to reproduce it, but everything works ok for me. Did you update the image by
docker-compose pull? Is there something in the console? Source code looks ok, I have the same... Can you open any static file (for example/static/js/main.f491311b.chunk.js)? It looks like static files won't be loaded or something happened in the code, so the error will be raised to the console.@ghost commented on GitHub (Aug 23, 2020):
Tested with the latest pull, after login with the demo info, the thing just keeps on spinning forever. Blank page, same as Trollwut
@Trollwut commented on GitHub (Aug 23, 2020):
Did you also lose your data inside your volumes?
Because now I fear pulling again so this happens again and I love my attachments and images :/
@ghost commented on GitHub (Aug 24, 2020):
I think the blank error has to do with SSL, without SSL it works fine, with SSL, I just get a blank page.
https://github.com/plankanban/planka/issues/21
Even with this nginx config it doesn't work. I have to enter example.com:[port] to get it to work.
@gamelaster commented on GitHub (Aug 24, 2020):
The blank page is shown when the app can't connect to planka's websocket. Also, I'm running latest planka, and everything works finely.
@nickbe commented on GitHub (Aug 25, 2020):
Also check if there are any pid lockfiles left. I found that sometimes they have to be manually deleted after some failed start.
@meltyshev commented on GitHub (Aug 25, 2020):
And keep in mind that «Please note that Planka is NOT released yet, API and database structure may be changed!». Currently, there are no migrations and new database structure for the next version can be incompatible with an old one. Updates will properly work on Planka release - I will write migrations on each database change. In the current version, the database changes very often, so migrations can take some working time.
@gamelaster commented on GitHub (Aug 26, 2020):
@meltyshev in this case, it would be nice to make database backup when docker container will detect upgrade
@nickbe commented on GitHub (Aug 26, 2020):
That's basically a one lines for every user who wants that. If you're abilities do not go beyond docker containers then I suggest you wait for major updates rather than the smaller ones. As Maks mentioned - the database structure will change considerably in the coming weeks and there's no time for any automatic backup or migration scripts for now.
@spartan117aut commented on GitHub (Oct 15, 2020):
Just had the same problem. Turned out that I didn't edit BASE_URL in docker-compose.yml...
That happens when you don't read the instructions carefully. Just wanted to share in case anyone else has troubles...
@timshannon commented on GitHub (Oct 26, 2021):
Not sure if this is the same issue, but I thought I'd drop this info here:
I was running fine on the docker :latest tag, and I noticed there was a more recent 1.0.0-beta tag out there, so I thought i'd check it out.
After pulling the tag I get a blank screen or a forever spinning wheel. Docker logs show that a new table is missing:
And per the comments above, it looks like there is no DB migration in place yet, which explains the missing tables on existing instances.
@meltyshev or @nickbe will post 1.0 have data migrations? Basically it's not worth actually using this software until you know that data you put in it will be preserved between versions.
@lp419665 commented on GitHub (Jun 14, 2022):
Hello, my Planka juct became blank (black) page. When I query the database everything seems ok, I can see tasks. Do I need to check some tables? Planka is running on OpenShift.
@SiM22 commented on GitHub (Jun 15, 2022):
What you said is the reality. From comments made in other issues there seems to be a goal for a paid cloud version of Planka or something along those lines. The lack of care for the users who have helped them better the product is at the moment non existent.
@gamelaster commented on GitHub (Jun 15, 2022):
@SiM22 in Readme there was mentioned for long time that it's ALPHA software and it can break (mainly in terms of database structure). And it did. There are several issues here which have several ways of fixing this. I had this issue too, and fixed it according the manuals. This is still just community project, so far no efforts being commercial product, and developer seems to be busy.
@jkocianICA commented on GitHub (Dec 30, 2022):
I was running into this problem just now and this is exactly what the problem was. Oops!
@Istria1704 commented on GitHub (Jun 25, 2023):
Is it possible to have multiple base URLs?
Currentry, I have my base url set to the local ip of the server: 192.168.2.20.
I have an NGINX proxy that points both planka.example.com and planka.example2.com to 192.168.2.20:3000. But in Chrome, I get a blank page when using those URLs. When I go to http://192.168.2.20:3000, it does work.
And also in Firefox, all 3 options work fine.
Edit: Correction, in Firefox, the login screen loads. But after logging in it says "server connection failed".
@meltyshev commented on GitHub (Jul 4, 2023):
Unfortunately, this isn't possible for now. But I'll think about how it can be done, somebody already asked about this feature.
@Istria1704 commented on GitHub (Jul 4, 2023):
Thanks.
It would be a nice feature to have. So planka can be reached both locally and remotely.
When set to the local address, it's not reachable from outside the LAN. And if set to the subdomain, it's not reachable when the Internet connection is down.
Maybe it's worth having a look at how for example Nextcloud does it. There you can set multiple "trusted domains" in the config file.
Still, even without this, Planka is still the nicest, cleanest and snappiest service I tried until now. Good work!
@Maxwelldoug commented on GitHub (Oct 19, 2023):
A local dns server could solve this - override your domain to the internal IP in your local DNS server. Not a full solution, but definitely a workaround.