If a WiFi agent is not able to associate to the WiFi network, first make sure that the Ethernet interface is connected to the network and that the agent is reporting to the dashboard.
Example of a wifi agent connected to the dashboard but not associated with any WiFi network.
On the Agent Wireless tab, you can hover over the WiFi Timing bar graph to get more information on the failure reasons:
Potential erros are:
"Authentication failed, check password spelling": check if the password is correct by editing the WiFi profile
"No suitable network": check the following
SSID spelling (SSID is case sensitive)
SSID is in range by doing an SSID scan
WiFi SSID security settings matches the broadcasted SSID's security settings (e.g. PMF (required/optional/disabled), WPA3 vs. WPA2)
If the agent supports the SSID broadcasted band (e.g. WiFi5 agents don't support 6GHz)
At the bottom of the Wireless tab you can found more detailed WPA Supplicant logs that could help you troubleshoot WiFi connectivity issues. These logs are filtered to reduce verbosity and make them more user friendly.
If you want access to the full WPA Supplicant logs, you can check via the console the log file by following this procedure (agent root access is required):
Go to the Agents tab
Click on the WiFi agent that can't associate to the WiFi network
Click on the Console tab within the Agent detailed view
Type the following command: tail -n 50 /tmp/wpa_supplicant.log
See what's the error reported by the WPA supplicant process.
In cases where a new WiFi profile was just applied to the agent, it's always good to reboot once the agent.
