shift@doogle:/$ cat /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search hsd1.fl.comcast.net
@fefekrzr, Comcast is my ISP and it’s their DNS my FB is unable to reach.
shift@doogle:/$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 37 Jan 30 17:34 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf
shift@doogle:/$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Active: active (running) since Wed 2025-01-29 12:37:23 EST; 1 day 8h ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-ma>
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 368 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 2093)
Memory: 5.2M
CPU: 9min 16.232s
CGroup: /system.slice/systemd-resolved.service
└─368 /lib/systemd/systemd-resolved
Questions
For my own edification (and crash course on network administration), here's what I believe you were looking into by having me run those commands.
Examined the contents of the /etc/resolv.conf file.
Examined information details about the /etc/resolv.conf file, with some formatting preferences added. I suspect you were looking for what, if any, changes might’ve been made.
Examined package manager details regarding the systemd-resolved package. Again, I suspect you were looking for changes, or needed changes.
Does the lower 1st number in the Version table (254.22) compared to the installed version number preceded by asterisks (252.33-1) indicate this package needs immediate updating per the line starting with “100?”
Examined the runtime status of the systemd-resolved package. I think you might’ve been checking to see if it was loaded, active, which documents it was referencing, etc.
Is that an accurate summary of what you were trying to do with the above commands?
Should I use a different DNS instead of Comcast’s? I don’t really trust ISP’s to keep information private.
Have you had a chance to check the status of the apache2 service? Identifying any issues there could help us quickly restore access to the web interface.
Regarding the DNS issue, to rule out any connectivity problems specific to Comcast, you might want to test using an alternative DNS server. For example, you can try querying Google’s public DNS server with the following command:
dig @8.8.8.8 debian.org A
If this works and you can successfully contact Google’s DNS server, you could temporarily configure the FreedomBox WAN connection to use that server. This might help restore functionality in the short term.
No, v254.22 is the package in backports. We only use specific packages from backports when they are needed.
Note that “search” field is not the same as “nameserver”. Your nameserver is set to the locally running service, which is systemd-resolved. And it appears that fallback DNS servers are already set for systemd-resolved. I’m not sure what the issue is then.
From the symptoms you described, it seemed likely to me that apache2 was failing. Try checking the logs to identify any errors:
sudo journalctl -u apache2.service -p err
If this doesn’t show anything useful, try running the command without the priority filter to see all related logs:
sudo journalctl -u apache2.service
One possible issue I’m considering is that DNS queries might have been blocked by your ISP during the upgrade process. What I’m hoping for is to get apache running again so that you regain access to the web interface. Then temporarily switch your primary DNS server to Google’s public DNS (8.8.8.8), which we’ve already confirmed FreedomBox can reach. After making this change, try completing the upgrade again. If it works, you can switch back to your original DNS server afterward.
I imagine you could change the DNS server through the command line. Personally, since FreedomBox is heavily scripted, I try not to make changes to it from places it doesn’t expect.
This might not be the perfect solution, and there could be a better approach that someone else can suggest. However, gathering more information at this stage certainly won’t hurt.
shift@doogle:~$ sudo journalctl -u apache2.service -p err
[sudo] password for shift:
Feb 14 12:19:07 doogle systemd[1]: Failed to start apache2.service - The Apa>
lines 1-1/1 (END)
shift@doogle:~$ sudo journalctl -u apache2.service
Jan 21 12:32:59 freedombox systemd[1]: Starting apache2.service - The Apache HTTP Server...
Jan 21 12:33:00 freedombox apachectl[737]: AH00558: apache2: Could not reliably determine the>
Jan 21 12:33:00 freedombox systemd[1]: Started apache2.service - The Apache HTTP Server.
Jan 21 15:21:58 freedombox systemd[1]: Stopping apache2.service - The Apache HTTP Server...
Jan 21 15:21:58 freedombox apachectl[1555]: AH00558: apache2: Could not reliably determine th>
Jan 21 15:21:58 freedombox systemd[1]: apache2.service: Deactivated successfully.
Jan 21 15:21:58 freedombox systemd[1]: Stopped apache2.service - The Apache HTTP Server.
Jan 21 15:21:58 freedombox systemd[1]: Starting apache2.service - The Apache HTTP Server...
Jan 21 15:21:58 freedombox apachectl[1561]: AH00558: apache2: Could not reliably determine th>
Jan 21 15:21:59 freedombox apache-error[1562]: [ssl:warn] [pid 1561:tid 1561] AH01909: 127.0.>
Jan 21 15:21:59 freedombox apache-error[1562]: [ssl:error] [pid 1561:tid 1561] AH02217: ssl_s>
Jan 21 15:21:59 freedombox apache-error[1562]: [ssl:error] [pid 1561:tid 1561] AH02604: Unabl>
Jan 21 15:21:59 freedombox systemd[1]: Started apache2.service - The Apache HTTP Server.
Jan 21 15:21:59 freedombox apache-error[1565]: [ssl:warn] [pid 1564:tid 1564] AH01909: 127.0.>
Jan 21 15:21:59 freedombox apache-error[1565]: [ssl:error] [pid 1564:tid 1564] AH02217: ssl_s>
Jan 21 15:21:59 freedombox apache-error[1565]: [ssl:error] [pid 1564:tid 1564] AH02604: Unabl>
Jan 21 15:21:59 freedombox apache-error[1565]: [mpm_event:notice] [pid 1564:tid 1564] AH00489>
Jan 21 15:21:59 freedombox apache-error[1565]: [core:notice] [pid 1564:tid 1564] AH00094: Com>
Jan 21 15:25:39 freedombox systemd[1]: Reloading apache2.service - The Apache HTTP Server...
Jan 21 15:25:39 freedombox apachectl[1901]: AH00558: apache2: Could not reliably determine th>
lines 1-20...skipping...
Jan 21 12:32:59 freedombox systemd[1]: Starting apache2.service - The Apache HTTP Server...
Jan 21 12:33:00 freedombox apachectl[737]: 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
Jan 21 12:33:00 freedombox systemd[1]: Started apache2.service - The Apache HTTP Server.
Jan 21 15:21:58 freedombox systemd[1]: Stopping apache2.service - The Apache HTTP Server...
Jan 21 15:21:58 freedombox apachectl[1555]: 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
Jan 21 15:21:58 freedombox systemd[1]: apache2.service: Deactivated successfully.
Jan 21 15:21:58 freedombox systemd[1]: Stopped apache2.service - The Apache HTTP Server.
Jan 21 15:21:58 freedombox systemd[1]: Starting apache2.service - The Apache HTTP Server...
Jan 21 15:21:58 freedombox apachectl[1561]: 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
Jan 21 15:21:59 freedombox apache-error[1562]: [ssl:warn] [pid 1561:tid 1561] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
Jan 21 15:21:59 freedombox apache-error[1562]: [ssl:error] [pid 1561:tid 1561] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=freedombox / issuer: CN=freedombox / serial: 6555838BC21>
Jan 21 15:21:59 freedombox apache-error[1562]: [ssl:error] [pid 1561:tid 1561] AH02604: Unable to configure certificate 127.0.1.1:443:0 for stapling
Jan 21 15:21:59 freedombox systemd[1]: Started apache2.service - The Apache HTTP Server.
Jan 21 15:21:59 freedombox apache-error[1565]: [ssl:warn] [pid 1564:tid 1564] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
Jan 21 15:21:59 freedombox apache-error[1565]: [ssl:error] [pid 1564:tid 1564] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=freedombox / issuer: CN=freedombox / serial: 6555838BC21>
Jan 21 15:21:59 freedombox apache-error[1565]: [ssl:error] [pid 1564:tid 1564] AH02604: Unable to configure certificate 127.0.1.1:443:0 for stapling
Jan 21 15:21:59 freedombox apache-error[1565]: [mpm_event:notice] [pid 1564:tid 1564] AH00489: Apache/2.4.57 (Debian) mod_auth_pubtkt/0.13 OpenSSL/3.0.11 configured -- resuming normal operations
Jan 21 15:21:59 freedombox apache-error[1565]: [core:notice] [pid 1564:tid 1564] AH00094: Command line: '/usr/sbin/apache2'
Jan 21 15:25:39 freedombox systemd[1]: Reloading apache2.service - The Apache HTTP Server...
Jan 21 15:25:39 freedombox apachectl[1901]: 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
Jan 21 15:25:39 freedombox apache-error[1565]: [mpm_event:notice] [pid 1564:tid 1564] AH00493: SIGUSR1 received. Doing graceful restart
Jan 21 15:25:39 freedombox systemd[1]: Reloaded apache2.service - The Apache HTTP Server.
Jan 21 15:25:40 freedombox apache-error[1565]: 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
Jan 21 15:25:40 freedombox apache-error[1902]: [ssl:warn] [pid 1564:tid 1564] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
Jan 21 15:25:40 freedombox apache-error[1902]: [ssl:error] [pid 1564:tid 1564] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=freedombox / issuer: CN=freedombox / serial: 6555838BC21>
Jan 21 15:25:40 freedombox apache-error[1902]: [ssl:error] [pid 1564:tid 1564] AH02604: Unable to configure certificate 127.0.1.1:443:0 for stapling
Jan 21 15:25:40 freedombox apache-error[1902]: [mpm_event:notice] [pid 1564:tid 1564] AH00489: Apache/2.4.57 (Debian) mod_auth_pubtkt/0.13 OpenSSL/3.0.11 configured -- resuming normal operations
Jan 21 15:25:40 freedombox apache-error[1902]: [core:notice] [pid 1564:tid 1564] AH00094: Command line: '/usr/sbin/apache2'
Jan 21 15:25:40 freedombox apache-error[1902]: [mpm_event:warn] [pid 1564:tid 1564] AH00488: long lost child came home! (pid 1566)
Jan 21 15:25:52 freedombox systemd[1]: Reloading apache2.service - The Apache HTTP Server...
Jan 21 15:25:52 freedombox apachectl[2040]: 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
Jan 21 15:25:52 freedombox apache-error[1902]: [mpm_event:notice] [pid 1564:tid 1564] AH00493: SIGUSR1 received. Doing graceful restart
Jan 21 15:25:52 freedombox systemd[1]: Reloaded apache2.service - The Apache HTTP Server.
Jan 21 15:25:53 freedombox apache-error[1902]: 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
Jan 21 15:25:53 freedombox apache-error[2042]: [ssl:warn] [pid 1564:tid 1564] AH01909: 127.0.1.1:443:0 server certificate does NOT include an ID which matches the server name
Jan 21 15:25:53 freedombox apache-error[2042]: [ssl:error] [pid 1564:tid 1564] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=freedombox / issuer: CN=freedombox / serial: 6555838BC21>
Jan 21 15:25:53 freedombox apache-error[2042]: [ssl:error] [pid 1564:tid 1564] AH02604: Unable to configure certificate 127.0.1.1:443:0 for stapling
Jan 21 15:25:53 freedombox apache-error[2042]: [mpm_event:notice] [pid 1564:tid 1564] AH00489: Apache/2.4.57 (Debian) mod_auth_pubtkt/0.13 OpenSSL/3.0.11 configured -- resuming normal operations
Jan 21 15:25:53 freedombox apache-error[2042]: [core:notice] [pid 1564:tid 1564] AH00094: Command line: '/usr/sbin/apache2'
Jan 21 15:25:53 freedombox apache-error[2042]: [mpm_event:warn] [pid 1564:tid 1564] AH00488: long lost child came home! (pid 1903)
-- Boot 9d4e80386f034fffb64f613c1d6b56ec --
Feb 14 12:17:37 doogle systemd[1]: Starting apache2.service - The Apache HTTP Server...
Feb 14 12:19:07 doogle systemd[1]: apache2.service: start operation timed out. Terminating.
Feb 14 12:19:07 doogle systemd[1]: apache2.service: Killing process 792 (apache2) with signal SIGKILL.
Feb 14 12:19:07 doogle systemd[1]: apache2.service: Failed with result 'timeout'.
Feb 14 12:19:07 doogle systemd[1]: Failed to start apache2.service - The Apache HTTP Server.
~
~
~
lines 1-46/46 (END)
