# \[SOLVED\] Problems with Cockpit & Javascript Restrictor

**URL:** <https://discuss.freedombox.org/t/solved-problems-with-cockpit-javascript-restrictor/1787>\
**Category:** Hardware Owners Support\
**Created:** [October 26, 2021, 8:06am UTC](https://discuss.freedombox.org/t/solved-problems-with-cockpit-javascript-restrictor/1787 "2021-10-26T08:06:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Avron](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/a/a9adbd/32.png) [@Avron](https://discuss.freedombox.org/u/Avron)\
**Post date:** [October 26, 2021, 8:06am UTC](https://discuss.freedombox.org/t/solved-problems-with-cockpit-javascript-restrictor/1787/1 "2021-10-26T08:06:51Z")

</div>

This is the second time I am having these problems, the last time it happened it was solved on the next day without doing anything.

What happens: I can log in to cockpit, the overview page is displayed with the four sections “Health”, “Usage”, “System information”, “Configuration” (might not be the exact names in English as I am translating from French), but Health is empty, CPU is 0, memory is zero, no ID, no on time, only system time is shown.

“Journal”, “Storage”, “Network”, “Services” show “loading” with a wheel forever. “Accounts” shows a blank page, “Applications” a smaller wheel forever, “Software updates” shows “Checking software status” and “Loading available updates, please wait” with a wheel forever.

“sudo systemctl restart cockpit” does not change anything .

---

<div class="post-metadata">

**Author:** ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil)\
**Post date:** [October 26, 2021, 1:12pm UTC](https://discuss.freedombox.org/t/solved-problems-with-cockpit-javascript-restrictor/1787/2 "2021-10-26T13:12:02Z")

</div>

Some pointers:

- Ensure that you are accessing Cockpit with a valid URL (as listed in the app) and not an IP address.
- Check browser developer tools to see if any network requests are failing.
- Check system logs using `journalctl -f` while accessing Cockpit.
- Cockpit seems to have services other than cockpit.service. Try restarting them all or reboot the machine.

---

<div class="post-metadata">

**Author:** ![lifeform](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/l/7ab992/32.png) [@lifeform](https://discuss.freedombox.org/u/lifeform)\
**Post date:** [October 26, 2021, 2:57pm UTC](https://discuss.freedombox.org/t/solved-problems-with-cockpit-javascript-restrictor/1787/3 "2021-10-26T14:57:04Z")

</div>

Probably unrelated since your first incident cleared up spontaneously, but I had the same cockpit symptoms recently after installing the Javascript Restrictor browser extension. Setting the level to 0 (turn wrappers off) in the extension for the domain of my FreedomBox allowed cockpit to function again.

---

<div class="post-metadata">

**Author:** ![Avron](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/a/a9adbd/32.png) [@Avron](https://discuss.freedombox.org/u/Avron)\
**Post date:** [October 26, 2021, 3:11pm UTC](https://discuss.freedombox.org/t/solved-problems-with-cockpit-javascript-restrictor/1787/4 "2021-10-26T15:11:22Z")

</div>

This is probably it, you saved me a lot of time, thanks !

I was using my laptop when I saw the problem today, now using my desktop that has the level to 0 and cockpit is fine on it. I can’t check what was on my laptop because I made something wrong on it and it is no more booting, will fix that later.
