How to Fix ‘Failed to Start Wait for Network to be Configured’ in Ubuntu

During system startup, Ubuntu servers and desktops may experience a prolonged delay of up to two minutes on the boot splash screen, followed by a red failure message in system logs: [FAILED] Failed to start Wait for Network to be Configured. Checking the systemd status log confirms that systemd-networkd-wait-online.service timed out after 120 seconds, slowing down overall system boots.

Resolving this boot stall requires understanding how network target synchronisation operates, auditing active network interfaces, adjusting wait-online timeout thresholds, and configuring single-interface binding overrides.

What Causes systemd-networkd-wait-online to Fail?

The systemd-networkd-wait-online.service unit delays the boot sequence until all configured network interfaces transition into a fully routed, routable carrier state. Failures commonly happen because:

  • Unplugged Ethernet Interfaces: A multi-port server or laptop configured with multiple physical NICs (e.g. eth0 and eth1) where one port has no cable attached. By default, the service waits for all configured interfaces to achieve link carrier state before completing.
  • NetworkManager and systemd-networkd Conflict: Both NetworkManager and systemd-networkd running simultaneously, causing race conditions during DHCP lease acquisition.
  • Slow Wi-Fi Handshakes: Wireless adapters requiring authentication after user login, causing early systemd boot timeouts.
  • Missing Default Route: Interfaces assigned static IP addresses without a defined gateway, preventing the routable state from triggering.

Step 1: Check Boot Blame and Service Status

Confirm how much time the wait-online service adds to your boot sequence:

  1. Open a terminal by pressing Ctrl + Alt + T or connecting via SSH.
  2. Analyse boot performance:
    systemd-analyze blame | head -n 10
  3. Check the exact error status of the service:
    systemctl status systemd-networkd-wait-online.service
  4. If the output displays Active: failed (Result: timeout), the service was blocked waiting for an unconnected interface.

Step 2: Bind Wait-Online to Any Interface (–any Flag)

Configuring the service to succeed as soon as any single interface connects resolves stalls caused by unused secondary ports:

  1. Create a systemd service drop-in override:
    sudo systemctl edit systemd-networkd-wait-online.service
  2. In the text editor, insert the following configuration lines between the comments:
    [Service]
    ExecStart=
    ExecStart=/lib/systemd/systemd-networkd-wait-online --any
  3. Save the file and exit the editor (Ctrl + O, Enter, Ctrl + X in Nano).
  4. Reload the systemd manager configuration:
    sudo systemctl daemon-reload

Step 3: Reduce the Service Timeout

If you prefer the service to wait briefly but not hold up the boot process for two minutes, reduce the timeout parameter:

  1. Reopen the service override:
    sudo systemctl edit systemd-networkd-wait-online.service
  2. Update the ExecStart directive to include a short timeout (e.g. 10 seconds):
    [Service]
    ExecStart=
    ExecStart=/lib/systemd/systemd-networkd-wait-online --any --timeout=10
  3. Save and exit, then reload daemon configs:
    sudo systemctl daemon-reload

Step 4: Disable the Service if Not Required

On standalone desktop installations managed by NetworkManager, the systemd-networkd wait-online unit is often completely unnecessary:

  1. Verify if NetworkManager is your primary network daemon:
    systemctl is-active NetworkManager
  2. If NetworkManager is active and your machine does not mount remote NFS or iSCSI shares during boot, disable the wait-online unit:
    sudo systemctl disable systemd-networkd-wait-online.service
    sudo systemctl mask systemd-networkd-wait-online.service
  3. Reboot your computer with sudo reboot. Ubuntu will now boot directly to the desktop without delay.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.