Feedback for FreedomBox

Overall Impressions

List of things you liked

  • It’s very easy to use
  • Just 2 clicks to add one “App”

List of things you disliked

Feedback on a Problem or for Improvement

  • Update tt-rss (news feed reader)

Thanks for all the great feedback! Overall, I agree with your ideas, and our team has discussed many of these things already. It’s good to know that users are thinking the same things as us.

Good observation. We agree that this is a problem, and one of our developers has already added it to our to-do list: https://salsa.debian.org/freedombox-team/plinth/issues/1722

Please let us know if you have any more ideas, or need any help!

1 Like

As others wrote, for me too a simple “Killer”-App is neccessary. Maybe a file browser.

1 Like

Freedombox is great

After “re-learning” old habits like syncing via Dropbox, using google-calendar, saving kontacts in the cloud, … I start tu see the benefits more and more.
Today, dough, a strange thing occurred to me.
My Freedombox was not available via gnuDIP (username.freedombox.rocks), and it said the connection is insecure.
Not sure if I was hacked or what the reason of this strange behaviour is.
But what I found out is, that my /boot partition was full, and the upgrade to 19.3 was not properly finished. After deleting some of the older kernels and the things that come with it, I did an apt upgrade, and “username.freedom box.rocks” did not give me a server not found anymore.
Still can not connect, since my letsencrypt cert is gone, and asking for a new one gave me a
No certificate followed by a
“There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: …”
I didn’t ask for a single one, since I had one.
Next week I am allowed to get a new one.
I am looking forward to use my bax again.
My conclusion

  1. The Box has a great potential. Especially with new apps like minidlna and samba.
  2. For nontechnical users there is quite some steps to take. To the convenience of a mobile phone is still quite a walk. We will have a lot of fun to go and get there. Thanks to all the people involved.
1 Like

Your FreedomBox would automatically keep trying to get a LE certificate. After the renewal window of one week is over, it should succeed in getting a LE cert.

Unattended upgrades is configured to clean up old kernels in the /boot partition. Maybe it was stuck on a failed apt upgrade and couldn’t proceed.

2 Likes

Thank you for the explanation and your work.

1 Like

First few days on the freedombox (olimex pioneer edition, running 19.23). So far, quite intuitive. Three problems encountered:

  1. the samba issue, for which the permissions 755 fix is already ready to be in the next release I think
  2. the cockpit blank page issue, which I was able to fix using the forum by adding freedombox.local to the cockpit.conf, and which apparently was not in the issues list yet (added)
  3. port forwarding apparently not working on my router :frowning: Not a freedombox issue though. I’ll have to call my provider.

Thanks everyone for delivering freedombox

1 Like

Thanks for your interest in FreedomBox.

You seem like a power user. We hope that in the coming months, you will be able to provide more insights into how to effectively use FreedomBox apps for various purposes and help other users on their journey.

Welcome to the community. :tada:

After the two last updates, my freedombox disconnected, and Bad to be manually rebooted.
Is this a known issue, vor some (unintended) fuckup by me?

There is no known issue the requires rebooting after an update.

Llevo un par de semanas usando freedombox. En general, me parece maravilloso. Syncthing ha sido todo un descubrimiento y desde mi móvil puedo conectarme a mi red domestica gracias a openVPN. Curiosamente, desde el móvil obtengo una dirección IP en mi red, pero si me conecto desde el ordenador del trabajo, salgo a Internet desde mi red doméstica, peor sigo manteniendo la IP de la oficina y no puedo ver los ordenadores de mi red doméstica.

minimdla y samba funcionaron correctamente el primer día, pero tras actualizarse el sistema, ya no puedo acceder. He comprobado los log y parece que no hay errores, simplemente no se puede acceder. MI servidor tiene dos tarjetas de red, pero una está sin uso. Creo que la cosa va por ahí, pero aún no he desentrañado el misterio.

Otra cosa que he descubierto es que en el servidor XMPP no se pueden crear salas. Yo uso un subdominio de noip()com y creo que por ahí vienen el problema. El una instalación anterior que hice de ejabered, descubrí que me pasaba lo mismo, y lo solucioné cambiando conference.miservidor()com por miservidor()com/conference.

Estoy recomendando freedombox a mis amigos. Es una forma ideal para instalar Matrix y disfrutar de servicios descentralizados.

1 Like

@luisgarcia, there are three problems outlined here:

  • OpenVPN works as expected on mobile phone. But OpenVPN from work computer does not.

  • Both miniDLNA and samba stopped working after an update.

  • Creating XMPP conference rooms is not working with ejabberd. Changing from conference.domain.com to domain.com/conference works.

1 Like

Así es. Esos son los tres puntos principales de mi mensaje.