HowToFixWiFiSimple fixes  •  Better connection
Wifi Guide

How to Connect Wifi Ubuntu Server? Detailed Connection Method In Minutes

Introduction Ubuntu Server is a powerful, lightweight operating system, but it does not assume you will always have an Ethernet cable plugged in. Many server deployments run on compact hardware, single-board computers, or machines tucked away in places where r

HowToFixWiFi

Introduction

Ubuntu Server is a powerful, lightweight operating system, but it does not assume you will always have an Ethernet cable plugged in. Many server deployments run on compact hardware, single-board computers, or machines tucked away in places where running a cable is impractical. If you find yourself asking How to Connect Wifi Ubuntu Server?, you are not alone. The process is straightforward once you know which tools to use and which configuration files to edit.

Unlike Ubuntu Desktop, Ubuntu Server does not include a graphical network applet by default. You will be working entirely from the terminal. This guide explains how to check your wireless hardware, identify the correct interface name, install the necessary packages, and connect to a WiFi network using three proven methods: Netplan, nmcli, and wpa_supplicant. Each method is explained step by step so you can choose the one that fits your environment.

By following this tutorial, you will be able to get your Ubuntu Server online over WiFi in minutes, verify the connection, and troubleshoot common issues if something goes wrong.

Table of Contents

What Is Ubuntu Server WiFi?

When people talk about Ubuntu Server WiFi, they mean the ability of a server edition of Ubuntu to associate with a wireless access point and obtain an IP address without using a wired Ethernet connection. Ubuntu Server supports WiFi through standard Linux wireless subsystems, including the kernel drivers, firmware, wpa_supplicant, and network configuration utilities such as Netplan and NetworkManager.

It is important to understand that WiFi on a server is not always enabled out of the box. Depending on the installation method and the hardware, the wireless interface may be present but unconfigured. Some server images omit wireless tools entirely to keep the footprint small. That is why learning How to Connect Wifi Ubuntu Server? involves installing packages and editing configuration files rather than clicking an icon.

WiFi is especially useful for headless servers, home lab setups, Raspberry Pi projects, and edge devices where Ethernet is unavailable. However, for production servers, a wired connection is still preferred for stability and performance. Treat WiFi as a convenient alternative when cabling is not an option.

Prerequisites Before You Begin

Before you start configuring WiFi, make sure you have the following items ready:

  • A machine running Ubuntu Server (any recent LTS version such as 22.04 or 24.04).
  • A built-in or USB WiFi adapter that is supported by Linux.
  • The name (SSID) and password of the wireless network you want to join.
  • Administrative access to the server, either through a local monitor and keyboard or via SSH over an initial Ethernet connection.
  • Patience to work with the command line and text editors such as nano or vim.

If you do not have physical access to the server, it is wise to complete the initial setup over Ethernet first. Once WiFi is working, you can disconnect the cable and manage the server remotely. Having a temporary wired connection also makes it easier to install packages if the wireless adapter drivers are missing.

Check Your Wireless Hardware

The first step in answering How to Connect Wifi Ubuntu Server? is confirming that the system can see your wireless adapter. Run the following commands to inspect hardware and radio status:

lspci | grep -i network
lsusb | grep -i wireless
rfkill list

The lspci command lists PCI devices. If you see an entry labeled as a wireless controller or network controller, your internal WiFi card is detected. The lsusb command does the same for USB WiFi adapters. The rfkill list command shows whether the wireless radio is blocked. A soft block means the radio is disabled by software, while a hard block usually means a physical switch or keyboard shortcut has disabled it.

If rfkill list shows a soft block, you can unblock it with:

sudo rfkill unblock wifi

If there is a hard block, check for a physical switch on the laptop or server chassis, or a function key combination that toggles wireless. Without the radio enabled, no software configuration will establish a connection.

Identify Your Wireless Interface Name

Modern Ubuntu versions use predictable network interface names. Instead of the old wlan0, you might see something like wlp2s0, wlan1, or wlp0s20f3. You need the exact name before configuring WiFi.

Run this command to list all network interfaces:

ip link show

Look for an interface that starts with w or wl. It will usually have a state of DOWN until you bring it up. You can also use:

iw dev

This command shows wireless interfaces and their capabilities. Once you identify the interface name, note it down. You will use it in Netplan YAML files, nmcli commands, and wpa_supplicant configurations.

Install Required WiFi Tools

Ubuntu Server may not include all WiFi utilities by default. Update your package list and install the tools you need:

sudo apt update
sudo apt install -y wireless-tools wpasupplicant netplan.io

If you plan to use NetworkManager, install it as well:

sudo apt install -y network-manager

wireless-tools provides legacy commands like iwconfig. wpasupplicant handles WPA and WPA2 authentication. netplan.io is the default network configuration backend on modern Ubuntu Server. NetworkManager provides the nmcli command-line tool, which is often the easiest way to connect to WiFi interactively.

After installation, reboot the server or restart networking services to ensure all drivers and modules are loaded properly.

Method 1: Connect Using Netplan (Recommended)

Netplan is the default network configuration utility on Ubuntu Server. It uses YAML files to define network settings and applies them through a backend such as systemd-networkd or NetworkManager. For most server administrators, Netplan is the best answer to How to Connect Wifi Ubuntu Server? because the configuration is declarative, persistent, and easy to version control.

Step 1: Locate or create the Netplan configuration file

Netplan configuration files are stored in /etc/netplan/. List the directory to find the existing file:

ls /etc/netplan/

You will typically see a file named 01-netcfg.yaml, 50-cloud-init.yaml, or something similar. Open it with a text editor:

sudo nano /etc/netplan/01-netcfg.yaml

Step 2: Edit the YAML file for WiFi

A minimal Netplan configuration for WiFi using networkd looks like this:

network:
  version: 2
  wifis:
    wlp2s0:
      dhcp4: true
      access-points:
        "Your_SSID":
          password: "Your_Password"

Replace wlp2s0 with your actual interface name. Replace Your_SSID with the exact name of your wireless network, including capitalization and special characters. Replace Your_Password with the WiFi passphrase. If your SSID contains spaces or special characters, keep it inside double quotes.

If you want to use NetworkManager as the renderer instead, the structure changes slightly:

network:
  version: 2
  renderer: NetworkManager
  wifis:
    wlp2s0:
      dhcp4: true
      access-points:
        "Your_SSID":
          password: "Your_Password"

Step 3: Apply the configuration

Before applying, validate the YAML syntax:

sudo netplan try

The netplan try command applies the configuration and automatically reverts it if you do not confirm within a timeout period. This is a safety net in case you make a mistake that breaks connectivity. If everything looks good, run:

sudo netplan apply

Step 4: Check the connection

Use ip addr to see if the wireless interface has received an IP address. Then test connectivity with ping:

ping -c 4 1.1.1.1

Netplan configurations persist across reboots, so your server will reconnect to the same WiFi network automatically after a restart.

Method 2: Connect Using nmcli

nmcli is the command-line interface for NetworkManager. It is often the fastest way to connect to WiFi on Ubuntu Server because it can scan for networks, handle passwords, and manage connections interactively.

Step 1: Install NetworkManager

If you did not install it earlier, do so now:

sudo apt install -y network-manager
sudo systemctl enable NetworkManager
sudo systemctl start NetworkManager

Step 2: Scan for available networks

List visible WiFi networks:

nmcli device wifi list

This command shows SSIDs, signal strength, security flags, and channel information. Identify the SSID you want to join.

Step 3: Connect to the network

Run the following command, replacing the placeholders with your values:

nmcli device wifi connect "Your_SSID" password "Your_Password"

If the connection succeeds, NetworkManager creates a persistent connection profile. The system will attempt to reconnect to this network automatically on boot.

Step 4: Manage the connection

You can view active connections with:

nmcli connection show

To disconnect:

nmcli device disconnect wlp2s0

To reconnect:

nmcli device connect wlp2s0

Using nmcli is ideal if you prefer not to edit YAML files by hand or if you need to switch between multiple WiFi networks frequently.

Method 3: Connect Using wpa_supplicant

wpa_supplicant is the lower-level tool that handles WPA/WPA2 authentication. It is useful on minimal server installations where you do not want to run NetworkManager or Netplan. This method is more manual but gives you full control over the authentication process.

Step 1: Generate a pre-shared key

Use wpa_passphrase to create a network configuration block:

wpa_passphrase "Your_SSID" "Your_Password"

This command outputs a network={ block containing the SSID and a hashed PSK. Copy the output.

Step 2: Edit the wpa_supplicant configuration

Open or create /etc/wpa_supplicant/wpa_supplicant.conf:

sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

Add the following content, adjusting the interface and network block as needed:

ctrl_interface=/run/wpa_supplicant
update_config=1

network={
    ssid="Your_SSID"
    psk=hashed_key_from_wpa_passphrase
    key_mgmt=WPA-PSK
}

You can use the plaintext psk="Your_Password" instead of the hashed key, but the hashed version is more secure.

Step 3: Start wpa_supplicant

Run wpa_supplicant in the background:

sudo wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf

Replace wlp2s0 with your interface name.

Step 4: Obtain an IP address

Use DHCP to get an IP address:

sudo dhclient wlp2s0

Or, if you use systemd-networkd, restart the interface:

sudo networkctl reload

This method is best for advanced users or embedded systems where minimal overhead is required.

Verify Your WiFi Connection

After applying any of the methods above, you should verify that the server is actually online. Run these checks in order:

  1. Check the interface IP address: ip addr show wlp2s0. Look for an inet address assigned to the wireless interface.
  2. Check the default route: ip route. Ensure there is a default gateway pointing through the WiFi interface.
  3. Ping a public IP: ping -c 4 8.8.8.8. This tests basic IP connectivity.
  4. Test DNS resolution: ping -c 4 google.com. If this fails but the IP ping works, you have a DNS issue.
  5. Check wireless link quality: iwconfig wlp2s0 or iw dev wlp2s0 link. These show signal strength, SSID, and bit rate.

If all checks pass, your Ubuntu Server is successfully connected to WiFi.

Troubleshooting Common Issues

Even with careful configuration, WiFi on Ubuntu Server can be finicky. Here are the most common problems and how to fix them.

No wireless interface found
If ip link show does not display a wireless interface, the driver or firmware may be missing. Install linux-firmware and reboot:

sudo apt install -y linux-firmware
sudo reboot

Authentication failure
Double-check the SSID and password. Remember that WiFi passwords are case-sensitive. If you are using Netplan, ensure the YAML indentation is correct. A single misplaced space can break the entire file.

Interface is down
Bring the interface up manually:

sudo ip link set wlp2s0 up

DNS not resolving
Check /etc/resolv.conf or use resolvectl status to see which DNS servers are in use. You can set static DNS in Netplan:

nameservers:
  addresses: [8.8.8.8, 1.1.1.1]

Connection drops after a few minutes
WiFi power management may be causing the adapter to sleep. Disable it with:

sudo iwconfig wlp2s0 power off

To make this persistent, create a systemd hook or add it to a dispatcher script.

Netplan apply fails
Run sudo netplan try first. If it reports a YAML error, fix the indentation and try again. Netplan is strict about spacing; use spaces, not tabs.

Comparison of Connection Methods

The table below compares the three methods discussed in this guide. Use it to decide which approach fits your situation best.

Method Ease of Use Best For Persistence Tools Required
Netplan Moderate Production servers, headless setups Yes, survives reboots netplan.io, text editor
nmcli Easy Quick testing, desktop-like workflow Yes, via NetworkManager profiles NetworkManager, nmcli
wpa_supplicant Advanced Minimal installations, embedded devices Manual, requires scripts wpasupplicant, dhclient

Tips and Best Practices

Follow these recommendations to keep your Ubuntu Server WiFi connection stable and secure:

  • Use a wired connection for the initial installation whenever possible. It makes troubleshooting much easier if WiFi fails.
  • Back up your Netplan configuration before making changes: sudo cp /etc/netplan/01-netcfg.yaml /etc/netplan/01-netcfg.yaml.bak.
  • Disable WiFi power management on servers to prevent unexpected disconnections.
  • Use strong, unique passwords for your wireless network. Avoid WEP; use WPA2 or WPA3.
  • If your router broadcasts both 2.4 GHz and 5 GHz networks under different SSIDs, choose the one with better signal at the server location.
  • Keep the system updated: sudo apt update && sudo apt upgrade -y ensures you have the latest wireless drivers and security patches.
  • Document your interface name and SSID in a secure location so you can reconfigure quickly after a reinstall.
  • If you move the server to a new location, update the Netplan or NetworkManager profile with the new SSID and password.

Frequently Asked Questions

Does Ubuntu Server support WiFi out of the box?
Not always. The kernel includes many wireless drivers, but the configuration tools may not be installed. You may need to install wpasupplicant, netplan.io, or network-manager manually.

Can I use a USB WiFi adapter with Ubuntu Server?
Yes. Most USB WiFi adapters work on Linux, but check compatibility before purchasing. Run lsusb to confirm the adapter is detected.

How do I find my WiFi interface name?
Run ip link show or iw dev. Look for an interface starting with w or wl.

What if my SSID is hidden?
You can still connect. In Netplan, add the SSID under access-points as usual. In wpa_supplicant, set scan_ssid=1 inside the network block.

Can I connect to both Ethernet and WiFi at the same time?
Yes, but only one should be the default gateway. Use interface metrics in Netplan or NetworkManager to prioritize the connection you prefer.

Does WiFi work during Ubuntu Server installation?
The Ubuntu Server installer can detect WiFi on some images, but it is often simpler to install with Ethernet and configure WiFi afterward.

How do I make the WiFi connection start automatically on boot?
Netplan and NetworkManager profiles are persistent by default. With wpa_supplicant, you may need to create a systemd service to launch it at boot.

Is WPA3 supported on Ubuntu Server?
Yes, if your wireless adapter and access point support WPA3. Configure the key management accordingly in wpa_supplicant or Netplan.

Conclusion

Learning How to Connect Wifi Ubuntu Server? is a valuable skill for anyone managing headless machines, home servers, or edge devices. Ubuntu Server does not provide a graphical WiFi menu, but the command-line tools are powerful and flexible. Netplan offers a declarative, persistent configuration that fits most production environments. nmcli provides a quick, interactive way to get online. wpa_supplicant serves minimal and embedded setups where every megabyte counts.

Start by checking your hardware and identifying your interface name. Install the necessary packages, choose a configuration method, apply the settings, and verify the connection with ping and ip addr. If something goes wrong, the troubleshooting section covers the usual suspects, from missing firmware to DNS errors.

With this guide, you should be able to connect your Ubuntu Server to WiFi in minutes and keep it online reliably. Whether you are running a media server, a home automation hub, or a development box, wireless connectivity removes the need for cables and gives you more freedom in where you place your hardware.