# Are any devs paying attention to the cockpit white screen issue that has existed since jun 2019?

**URL:** https://discuss.freedombox.org/t/are-any-devs-paying-attention-to-the-cockpit-white-screen-issue-that-has-existed-since-jun-2019/1310
**Category:** Development
**Created:** [January 12, 2021, 2:01am UTC](https://discuss.freedombox.org/t/are-any-devs-paying-attention-to-the-cockpit-white-screen-issue-that-has-existed-since-jun-2019/1310 "2021-01-12T02:01:46Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Danrancan](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/danrancan/32/482_2.png) [@Danrancan](https://discuss.freedombox.org/u/Danrancan)
#### Post date: [January 12, 2021, 2:01am UTC](https://discuss.freedombox.org/t/are-any-devs-paying-attention-to-the-cockpit-white-screen-issue-that-has-existed-since-jun-2019/1310/1 "2021-01-12T02:01:46Z")

</div>

I just wanted to attempt to turn some heads to a well confirmed [unresolved issue](https://discuss.freedombox.org/t/cockpit-server-administration/204/51) regarding the pioneer freedombox. I myself can confirm this issue exists in freedombox current as well as stable. My question is what attempts have been made to resolve this issue, and if not many, what attempts are going to be made (and when) to resolve this issue? it would be nice to get some dev input and feedback as to how  
[this MAJOR issue](https://discuss.freedombox.org/t/cockpit-server-administration/204/51) has existed for so long and what can be done as a current workaround or hot fix. Thanks for any attention this way or to [the thread sited in my post](https://discuss.freedombox.org/t/cockpit-server-administration/204/51).

---

<div class="post-metadata">

### Author: ![fred1m](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/fred1m/32/347_2.png) [@fred1m](https://discuss.freedombox.org/u/fred1m)
#### Post date: [January 12, 2021, 5:55am UTC](https://discuss.freedombox.org/t/are-any-devs-paying-attention-to-the-cockpit-white-screen-issue-that-has-existed-since-jun-2019/1310/2 "2021-01-12T05:55:33Z")

</div>

> [@Cockpit server administration](https://discuss.freedombox.org/t/cockpit-server-administration/204/52):
>
> I tested cockpit app on both stable and testing containers today. I was able to login in using Firefox and Chromium. I have a FreedomBox installed on Debian testing and a FreedomBox Pioneer. Cockpit works on both of them. Cockpit only allows you to login using the domain names it’s configured with. Are you using one of the URLs listed under the Access section in the Cockpit app? This is how it looks on my FreedomBox.

---

<div class="post-metadata">

### Author: ![Danrancan](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/danrancan/32/482_2.png) [@Danrancan](https://discuss.freedombox.org/u/Danrancan)
#### Post date: [March 24, 2021, 3:40am UTC](https://discuss.freedombox.org/t/are-any-devs-paying-attention-to-the-cockpit-white-screen-issue-that-has-existed-since-jun-2019/1310/3 "2021-03-24T03:40:14Z")

</div>

Very weird. I have tested over a dozen different freedombox images at this point including stable and weekly’s, and this issue persists for me, even using the correct cockpit url as you pointed out in the above image. I also noticed that after first boot, my freedombox shows “ghost” WAN interfaces in its plinth interface settings. When clicking on the interfaces, freedombox exposes an error page, so I just delete the (ghost) interfaces and things seem to halfway work. Does any of this or content in the ORIGINAL POST sound indicitave of a hardware problem of a defective lime2 board? Because at this point, thats the only thing I can conclude considering I am the only one facing these issues.
