I have RPI4 Model B Rev 1.5 (b03115). My problem is that on boot the RPI either connects to 2.4 GHz Wlan, or there is no way to connect to it afterwards, unless I restart the system.
I create the network using cloud-init/network-configI am using 2025-12-04-raspios-trixie-armhf-lite.img. so 32bit OS with 64bit kernel. ip link shows “wlan0: state DOWN mode DORMANT”. nmcli connection shows the connection as present, TYPE: wifi, DEVICE 00.
nmcli connection up <NAME> takes very long, and prints eventually Error: Connection activation faled: Secrets were required, but not provided, Hind: use journalctl -xe …“
nmcli device wifi shows the connection, singnal can change but is e.g. shown as 50, and BARS is `**`.
wpa_cli: scan, scan_results shows the network, but list_network does not show it.
However if I do nmcli connection up <NAME>, then for a while `nmcli connection` shows the connection in orange colour and assigns DEVICE: wlan0. In wpa_cli: list_network lists the network. Moreover wpa_cli reportsWhatever I do I cannot connect to the network. But if I restart Raspberry Pi, then on the next boot from the beginning . I am aware there are interferences with RPI4 but I do not move the device, it has the same distance to the router, I just restart it and it either connects or does not connect. When it connects the the signal is something like 57 or -62 (wpa_cli scan_results and nmcli device wifi show different numbers). Moreover I invested time in this more than a year ago and came to the same conclusion: it either can connect to wifi during boot or never afterwards.
For me this means that there must be something in the order of the boot process, which determines if the device can connect to Wifi after it boots.
* How can I convince Raspberry Pi 4 to connect to a WiFi network, if it does not connect to it during the boot.
* Why the configured network sometimes is not shown as available in `wpa_cli list_networks`?
I create the network using cloud-init/network-config
Code:
network: version: 2 renderer: NetworkManager wifis: wlan0: regulatory-domain: DE dhcp4: false dhcp6: false addresses: [192.168.0.12/24] nameservers: addresses: [192.168.0.1] access-points: M123: password: ABCDEFG7 routes: - to: default via: 192.168.0.1nmcli connection up <NAME> takes very long, and prints eventually Error: Connection activation faled: Secrets were required, but not provided, Hind: use journalctl -xe …“
nmcli device wifi shows the connection, singnal can change but is e.g. shown as 50, and BARS is `**`.
wpa_cli: scan, scan_results shows the network, but list_network does not show it.
However if I do nmcli connection up <NAME>, then for a while `nmcli connection` shows the connection in orange colour and assigns DEVICE: wlan0. In wpa_cli: list_network lists the network. Moreover wpa_cli reports
Code:
CTRL-EVENT-ASSOC-REJECT bssid=… status_code 16CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid=… auth_failures=2 duration=20 reason=CONN_FAILEDFor me this means that there must be something in the order of the boot process, which determines if the device can connect to Wifi after it boots.
* How can I convince Raspberry Pi 4 to connect to a WiFi network, if it does not connect to it during the boot.
* Why the configured network sometimes is not shown as available in `wpa_cli list_networks`?
Statistics: Posted by dpa — Thu Jan 15, 2026 9:19 am — Replies 0 — Views 38