Using single-board computers Raspberry Pi as servers, media centers or smart home nodes often require operation in the mode headless, meaning no monitor or input peripherals are connected. This significantly saves space and resources, turning the device into an unobtrusive yet powerful tool on your network. However, initial wireless connection setup presents difficulties for many users, as a standard graphical interface is unavailable.
To get started successfully, you don't need complex equipment or specialized programming skills. All you need is a microSD memory card, a computer with access to the file system, and a text editor. The entire process is based on creating a special configuration file in the boot partition of the memory card, which the system reads upon first boot.
In this guide, we will go through a step-by-step algorithm of actions that is guaranteed to help establish communication between your Raspberry Pi and home network. We'll cover file system features, configuration file syntax, and diagnostic methods if automatic connection doesn't work the first time.
Preparation of equipment and software
Before you begin any manipulation of the file system, you need to make sure you have all the necessary components. You will need the board itself. Raspberry Pi (compatible with models Zero, 3, 4, and newer), a microSD memory card with at least 8 GB of storage, and a card reader to connect the card to your PC. You will also need a power supply that meets the requirements of your model.
Preparing the operating system is a critical step. It is recommended to use an official image. Raspberry Pi OS Lite, as it doesn't contain a graphical shell and loads faster, making it ideal for headless mode. However, the full desktop version is also suitable if you plan to use a graphical interface in the future.
To write the image to the memory card, use proven utilities such as Raspberry Pi Imager or EtcherThese programs automatically verify the integrity of the written data, minimizing the risk of file system corruption during initial launch. Do not use standard operating system file copying tools, as this may cause bootloader errors.
Creating a WiFi configuration on the boot partition
After the operating system image is written to the memory card, the computer can recognize two new disks: one with Linux files (not readable in Windows without special software) and a small partition boot. It is at the root of the section boot We need to create a network configuration file.
Create a text file and name it wpa_supplicant.confPlease note that the file extension must be missing and the name must be spelled exactly, respecting the letter case. In newer versions Raspberry Pi OS This file can be created directly in the setup wizard window. Raspberry Pi Imager before recording the image, which greatly simplifies the process.
You need to place the following code inside the file, replacing the data with your own:
country=US
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
ssid="YOUR_SSID"
psk="YOUR_PASSWORD"
key_mgmt=WPA-PSK
}
Parameter country=US indicates the region, which is important for compliance with legal regulations on WiFi frequency usage. If you are in Russia, replace US on RU. Field ssid — this is the name of your wireless network, and psk — the password for it. Quotes are required if the network name or password contains spaces or special characters.
What to do if the network is hidden?
If your WiFi network is hidden (does not broadcast the SSID), add the line scan_ssid=1 inside the network block before the closing bracket.
Enabling SSH protocol for remote access
After setting up the network, you need to enable remote control of the device. By default, in modern versions Raspberry Pi OS protocol SSH (Secure Shell) is disabled for security reasons. To enable it without access to the interface, simply create an empty file named ssh (without extension) in the root of the partition boot.
Just create a text file, name it ssh Don't write anything inside. Upon boot, the system will detect this file, enable the SSH daemon, and immediately delete the marker file itself. This is a standard "trigger" mechanism for one-time service activation.
☑️ Checklist before the first launch
Completed: 0 / 4
An alternative way is to use a file system-boot or setup via Raspberry Pi Imager, where you can immediately set a username and password and enable SSH. This is a more secure method, as it allows you to change the user's default password right away. pi, which is a well-known fact for all attackers.
⚠️ Warning: Never use a device with a default password on an open network. Change the password immediately after the first login using the command passwd or create a new user with administrator rights.
First launch and searching for the device on the network
Insert the prepared memory card into the slot Raspberry Pi and apply power. The LEDs on the board should blink: the green (or yellow) activity LED will blink when reading data, and the red one will be solid, indicating power is present. The initial boot process and applying WiFi settings may take between 30 seconds and 2 minutes.
After waiting, you need to find the IP address the router assigned to your device. The easiest way to do this is through your router's interface. Log into the router's admin panel (usually at 192.168.0.1 or 192.168.1.1), and find the list of connected clients (Connected Devices, DHCP Client List) and find the device with a name starting with raspberrypi.
If you cannot access your router, use network scanners such as Advanced IP Scanner for Windows or utility nmap for Linux/macOS. Team nmap -sn 192.168.1.0/24 (replace the subnet with your own) will show all active devices on the local network.
Search method
Tool
Complexity
Reliability
Router interface
Web browser
Low
High
Network scanner
Advanced IP Scanner
Low
Average
Command line
nmap / arp -a
Average
High
Mobile application
Fing / Network Analyzer
Low
Average
Once the IP address is found (e.g. 192.168.1.45), try connecting to it through the terminal with the command ssh pi@192.168.1.45When you first connect, the system will ask you to confirm the key fingerprint - enter yesIf you haven't changed your password, the default is raspberry, but in newer OS versions it may require creation upon first boot via the monitor.
Setting up a static IP address
For server tasks, it is critical that the address Raspberry Pi The IP address assigned via DHCP may not change after rebooting the router. This may result in loss of connection to the device. There are two possible solutions: reserving the address on the router or setting up a static IP address on the board itself.
Configuring this on the router (DHCP Reservation) is preferable as it eliminates address conflicts. You need to find your Raspberry Pi's MAC address (it's listed in the router's client list) and assign it a specific IP address in the router's DHCP server settings.
If you need to configure a static IP directly in the system Raspberry Pi OS, use the utility dhcpcdOpen the configuration file with the command:
sudo nano /etc/dhcpcd.conf
At the end of the file, add a block for your interface (usually eth0 for cable or wlan0 for WiFi):
interface wlan0
static ip_address=192.168.1.200/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1 8.8.8.8
After making changes, reboot the networking service or the card itself. Make sure the selected IP address is outside the router's DHCP range; otherwise, a conflict will occur and one of the devices will lose network connectivity.
Diagnosing connection problems
If the device still doesn't appear online after all these steps, you'll need to run diagnostics. Reconnect the memory card to your computer and check the file. wpa_supplicant.conf Check for typos. A common error is an incorrect escape character or extra spaces in the password.
It's also worth paying attention to frequency compatibility. Older models Raspberry Pi (e.g., Zero W or Pi 3) only support the 2.4 GHz band. If your router broadcasts a 5 GHz network with the same SSID, the device may attempt to connect to an incompatible frequency.
⚠️ Please note: Router interfaces and settings are constantly being updated. The exact menu name for IP address assignment may vary depending on your router model (Keenetic, TP-Link, Asus, Mikrotik). Please consult the manufacturer's official documentation.
For a more thorough diagnosis, you can connect the board to a monitor, at least temporarily, to see the boot logs. Errors in the file /var/log/syslog or the command output dmesg will indicate the cause of the WiFi module failure. The problem is often resolved by updating the router firmware or changing the wireless network channel to a less congested one.
Why isn't WiFi working on 5 GHz?
WiFi modules in older Raspberry Pi versions only operate at 2.4 GHz. Separate networks on your router by giving them different names, or use an external USB WiFi adapter with 5 GHz support.
Frequently Asked Questions (FAQ)
Is it possible to configure WiFi without creating a wpa_supplicant.conf file?
Yes, if you use Raspberry Pi Imager Version 1.6 and higher. In the settings menu (gear icon), before burning the image, you can enter WiFi information and enable SSH. The program will automatically create the necessary files on the memory card.
What should I do if Raspberry Pi can't see my WiFi network?
Check whether your router model supports the correct frequency (2.4 GHz or 5 GHz). Ensure that the network name (SSID) does not contain Cyrillic characters or special symbols that may be incorrectly processed by the driver. Try temporarily disabling MAC address filtering on your router.
How do I find out my IP address if I can't access my router?
Use a mobile network scanner app (such as Fing) or the command line on your PC. On Linux/macOS, the command arp -a will display a table of IP and MAC address mappings. Look for a MAC address starting with the Raspberry Pi manufacturer prefix (e.g., B8:27:EB or D8:3A:DD).
Is it safe to leave SSH enabled all the time?
Within a home network with a strong WiFi password and a complex user password, yes. However, for internet access, it's best to use Fail2Ban to block brute-force attacks or change the default SSH port from 22 to another one.