After downloading and installing an app, my freedombox is no longer accessible from web page, only ssh

If you are asking for support for an issue, please include the following information at the top of your post:

  • Freedombox is plugged directly into home router and each port is forwarded seperately.
  • Purchased Pioneer Freedombox probably somtime in 2019. Can’t remember.
  • The version of FreedomBox your are running: I can’t access the menu to show me the version, but I flashed my SD Card with the latest “freedombox-stable_pioneer_a20-olinuxino-lime2-armhf.img

This is the 5th time I’ve encountered this error, and had to reflash the SD card with a new freedombox, but I am tired of reflashing and it takes days to download all apps, and I would like to find a solution instead of reflashing.

I flashed my Pioneer Freedombox with the latest stable image of freedombox. I installed many apps from the web interface. Then I installed an app that I can’t remember. During or after that app installation from the web interface, the web interface stopped working and I can no longer connect to “freedombox.local”. Note: Before it stopped working, I disabled logging from the web interface, so I’m not sure debug logs will be on the server, let alone where I can access them.

I CAN ssh into my freedombox successfully, and when I do, I run sudo service apache2 status, which shows that apache2 is not running. I then run sudo service apache2 start, and apache2 shows it is now running. Then I try accessing freedombox from freedombox.local in the web interface. Again, no connection. Instead I get

This site can’t be reached
**freedombox** refused to connect.
Try:
* Checking the connection
* [Checking the proxy and the firewall](chrome-error://chromewebdata/#buttons)
ERR_CONNECTION_REFUSED

When I access freedombox via ssh, and run sudo journalctl the only errors in the log that show up are the following:

Jul 18 05:51:38 freedombox systemd[1]: Reloaded apache2.service - The Apache HTTP Server.
Jul 18 05:51:38 freedombox apache-error[2080]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
Jul 18 05:51:39 freedombox apache-error[2219]: [ssl:warn] [pid 1635:tid 1635] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
Jul 18 05:51:39 freedombox apache-error[2219]: [ssl:error] [pid 1635:tid 1635] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=freedombox / issuer: CN=freedombox / serial: 63BB4862BB61C5>
Jul 18 05:51:39 freedombox apache-error[2219]: [ssl:error] [pid 1635:tid 1635] AH02604: Unable to configure certificate 127.0.1.1:443:0 for stapling
Jul 18 05:51:39 freedombox apache-error[2219]: [mpm_event:notice] [pid 1635:tid 1635] AH00489: Apache/2.4.57 (Debian) mod_auth_pubtkt/0.13 OpenSSL/3.0.11 configured -- resuming normal operations
Jul 18 05:51:39 freedombox apache-error[2219]: [core:notice] [pid 1635:tid 1635] AH00094: Command line: '/usr/sbin/apache2'
Jul 18 05:51:39 freedombox apache-error[2219]: [mpm_event:warn] [pid 1635:tid 1635] AH00488: long lost child came home! (pid 2081)

There are no logs in /var/log/apache2/*.

I’m not sure what is going wrong here, where to look for relavent logs, and how to fix this issue. I would like to get my Freedombox Local Web interface working again, but have no Idea how, and I’ve done this like 6 times now. Could someone please guide me to a fix or tell me how to debug and fix this from ssh? I’m not even sure the logs I SHOULD be looking at.

Any help is much appreciated as I really don’t want to flash and reinstall freedombox all over again.
Thanks

I’m not sure what’s going on and don’t have a surefire solution for you, but two things I would try would be:

  1. Check that service uwsgi is running (in addition to apache2).

  2. Try rebooting from the command line (sudo shutdown -r now) and then log in via ssh and check services.

Do you know the local IP to your fbx?
server certificate does NOT include an ID which matches the server name seems like a certificate issue with your box.

Maybe it’s a red herring, but yours is the first case I have seen of someone using anything other than 127.0.0.1 for local address - is the 127.0.1.1 somehow a typo somewhere?

You should be able to access the web interface using the machines IP address:
example: https://10.0.0.15

While logged in through ssh you can use the “ip a” command to show the current configuration.

In system settings, use configure and make sure the information is correct and complete; update setup if necessary.

Check let’s encrypt in the system settings and see if it has obtained a certificate. if it has, try accessing your box by the address listed in let’s encypt, otherwise, obtain a certificate.

Regarding 127.0.1.1, freedombox uses that address to identify the host vs the loopback.