"
# Problem Report: OPNsense services fail to start after reboot
**Subject:** Unbound and WebGUI (lighttpd) fail to start automatically after reboot. Reload all services (console option 11) restores functionality.
## 1. Environment
- OPNsense version: 26.7.7
- FreeBSD: 15.1
- Virtualization: QEMU/KVM with libvirt
- Host operating system: Lubuntu
- Network adapters: VirtIO
- WAN: libvirt NAT network
- LAN: isolated libvirt network
## 2. Network configuration
OPNsense WAN:
- IP address: 192.168.122.23
- Gateway: 192.168.122.1
OPNsense LAN:
- IP address: 192.168.100.1
Debian 13 client:
- IP address: 192.168.100.184
- Default gateway: 192.168.100.1
Both OPNsense interfaces receive their expected IP addresses.
## 3. Problem description
After a normal OPNsense reboot:
- The WAN and LAN interfaces appear to be configured.
- The routing table contains the expected routes.
- configd is running.
- Unbound is not running.
- lighttpd is not running.
- The WebGUI is unavailable.
- The Debian client cannot access the Internet.
The OPNsense console boot log displays:
"Starting web GUI......done."
However, lighttpd is subsequently found not running.
## 4. Reproduction and recovery
The problem occurs after rebooting the OPNsense virtual machine.
Using console option 11, "Reload all services", restores functionality.
After this operation:
- The WebGUI becomes accessible.
- Unbound starts working.
- Debian regains Internet connectivity.
This behaviour is reproducible after reboot.
## 5. Additional observations
Attempting to start Unbound manually with:
`service unbound start`
returns a message indicating that unbound_enable is not set to YES in /etc/rc.conf.
Using:
`service unbound onestart`
produces a socket-buffer warning:
`SO_SNDBUF was not granted: No buffer space available`
Attempting to start lighttpd manually with onestart fails.
The exact lighttpd error still needs to be collected.
The Listen Interfaces setting is already set to "All (recommended)".
Available OPNsense updates have been installed, but the problem remains.
No manual changes have been made to /etc/rc.conf or kernel network-buffer settings.
## 6. Questions for the OPNsense developers
1. Is this a known issue with OPNsense 26.7.7 running under QEMU/KVM?
2. Could this be related to the boot sequence or service dependencies?
3. Why do Unbound and lighttpd fail to remain running after boot?
4. Is the SO_SNDBUF warning relevant to the Unbound startup failure?
5. Is there a recommended diagnostic procedure for this situation?
6. Is there a supported way to execute a service reload after the network initialization phase?
7. Could this be a regression in the current release?
## 7. Requested assistance
We would appreciate guidance on identifying the underlying cause.
We would prefer a permanent correction in the normal startup process rather than relying on a manual reload of all services after every reboot.
Thank you for your assistance.
**Subject:** Unbound and WebGUI (lighttpd) fail to start automatically after reboot. Reload all services (console option 11) restores functionality.
## 1. Environment
- OPNsense version: 26.7.7
- FreeBSD: 15.1
- Virtualization: QEMU/KVM with libvirt
- Host operating system: Lubuntu
- Network adapters: VirtIO
- WAN: libvirt NAT network
- LAN: isolated libvirt network
## 2. Network configuration
OPNsense WAN:
- IP address: 192.168.122.23
- Gateway: 192.168.122.1
OPNsense LAN:
- IP address: 192.168.100.1
Debian 13 client:
- IP address: 192.168.100.184
- Default gateway: 192.168.100.1
Both OPNsense interfaces receive their expected IP addresses.
## 3. Problem description
After a normal OPNsense reboot:
- The WAN and LAN interfaces appear to be configured.
- The routing table contains the expected routes.
- configd is running.
- Unbound is not running.
- lighttpd is not running.
- The WebGUI is unavailable.
- The Debian client cannot access the Internet.
The OPNsense console boot log displays:
"Starting web GUI......done."
However, lighttpd is subsequently found not running.
## 4. Reproduction and recovery
The problem occurs after rebooting the OPNsense virtual machine.
Using console option 11, "Reload all services", restores functionality.
After this operation:
- The WebGUI becomes accessible.
- Unbound starts working.
- Debian regains Internet connectivity.
This behaviour is reproducible after reboot.
## 5. Additional observations
Attempting to start Unbound manually with:
`service unbound start`
returns a message indicating that unbound_enable is not set to YES in /etc/rc.conf.
Using:
`service unbound onestart`
produces a socket-buffer warning:
`SO_SNDBUF was not granted: No buffer space available`
Attempting to start lighttpd manually with onestart fails.
The exact lighttpd error still needs to be collected.
The Listen Interfaces setting is already set to "All (recommended)".
Available OPNsense updates have been installed, but the problem remains.
No manual changes have been made to /etc/rc.conf or kernel network-buffer settings.
## 6. Questions for the OPNsense developers
1. Is this a known issue with OPNsense 26.7.7 running under QEMU/KVM?
2. Could this be related to the boot sequence or service dependencies?
3. Why do Unbound and lighttpd fail to remain running after boot?
4. Is the SO_SNDBUF warning relevant to the Unbound startup failure?
5. Is there a recommended diagnostic procedure for this situation?
6. Is there a supported way to execute a service reload after the network initialization phase?
7. Could this be a regression in the current release?
## 7. Requested assistance
We would appreciate guidance on identifying the underlying cause.
We would prefer a permanent correction in the normal startup process rather than relying on a manual reload of all services after every reboot.
Thank you for your assistance.
