Wifi Client option fails to activate, and makes web server inaccessible.

[spideramn1987]

Prerequisites

• I have read CONTRIBUTING.md

Bug Report Details

Rayhunter Version: v0.11.1
Capture Date: 2026-05-13
Capture Location: United States
Device and Model: Orbic 400L_V1.2.0_BVZRT
What happened? When attempting to activate Wifi Client Mode, no connection is made, and webserver becomes inaccessible.
Expected behavior: Device connects to wifi ap, for internet access/notifications.
Relevant log output:

R A Y H U N T E R 🐳
[2026-05-14T00:58:29Z INFO rayhunter_daemon] Starting Diag Thread
[2026-05-14T00:58:29Z INFO rayhunter_daemon] Starting UI
[2026-05-14T00:58:29Z INFO rayhunter_daemon] Starting Key Input service
[2026-05-14T00:58:29Z INFO rayhunter_daemon] create shutdown thread
[2026-05-14T00:58:29Z INFO rayhunter_daemon] spinning up server
[2026-05-14T00:58:29Z INFO rayhunter_daemon::diag] Using configuration for device: Orbic
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] Diag device initialization succeeded after 0 retries
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] retrieving diag logging capabilities...
[2026-05-14T00:58:29Z WARN rayhunter::diag] warning: 329 leftover bytes when parsing Message
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] enabled logging for log type 1
[2026-05-14T00:58:29Z WARN rayhunter::diag] warning: 298 leftover bytes when parsing Message
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] enabled logging for log type 4
[2026-05-14T00:58:29Z WARN rayhunter::diag] warning: 140 leftover bytes when parsing Message
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] enabled logging for log type 5
[2026-05-14T00:58:29Z WARN rayhunter::diag] warning: 168 leftover bytes when parsing Message
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] enabled logging for log type 7
[2026-05-14T00:58:29Z WARN rayhunter::diag] warning: 122 leftover bytes when parsing Message
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] enabled logging for log type 10
[2026-05-14T00:58:29Z WARN rayhunter::diag] warning: 73 leftover bytes when parsing Message
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] enabled logging for log type 11
[2026-05-14T00:58:29Z WARN rayhunter::diag] warning: 72 leftover bytes when parsing Message
[2026-05-14T00:58:29Z INFO rayhunter::diag_device] enabled logging for log type 13
[2026-05-14T00:58:29Z INFO rayhunter_daemon::diag] Starting recording with 200MB disk space available
[2026-05-14T00:58:29Z INFO rayhunter_daemon] The orca is hunting for stingrays...
[2026-05-14T01:14:15Z INFO rayhunter_daemon] Closing current QMDL entry...
[2026-05-14T01:14:15Z INFO rayhunter_daemon] Done!
[2026-05-14T01:14:15Z INFO rayhunter_daemon::diag] Diag reader thread exiting...
[2026-05-14T01:14:15Z INFO rayhunter_daemon::display::generic_framebuffer] received UI shutdown
[2026-05-14T01:14:15Z INFO rayhunter_daemon] see you space cowboy...
R A Y H U N T E R 🐳
[2026-05-14T01:14:15Z INFO rayhunter_daemon] Starting Diag Thread
[2026-05-14T01:14:15Z INFO rayhunter_daemon] Starting UI
[2026-05-14T01:14:15Z INFO rayhunter_daemon] Starting Key Input service
[2026-05-14T01:14:15Z INFO rayhunter_daemon] create shutdown thread
[2026-05-14T01:14:15Z INFO rayhunter_daemon] spinning up server
[2026-05-14T01:14:15Z INFO rayhunter_daemon::diag] Using configuration for device: Orbic
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] Diag device initialization failed 1 times, retrying in 100ms: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-05-14T01:14:15Z INFO wifi_station::diagnostics] acquired kernel wakelock
[2026-05-14T01:14:15Z INFO wifi_station::client] wlan1 not found, attempting to create it
[2026-05-14T01:14:15Z INFO rayhunter_daemon] The orca is hunting for stingrays...
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] Diag device initialization succeeded after 1 retries
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] retrieving diag logging capabilities...
[2026-05-14T01:14:15Z WARN rayhunter::diag] warning: 329 leftover bytes when parsing Message
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] enabled logging for log type 1
[2026-05-14T01:14:15Z WARN rayhunter::diag] warning: 298 leftover bytes when parsing Message
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] enabled logging for log type 4
[2026-05-14T01:14:15Z WARN rayhunter::diag] warning: 140 leftover bytes when parsing Message
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] enabled logging for log type 5
[2026-05-14T01:14:15Z WARN rayhunter::diag] warning: 168 leftover bytes when parsing Message
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] enabled logging for log type 7
[2026-05-14T01:14:15Z WARN rayhunter::diag] warning: 122 leftover bytes when parsing Message
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] enabled logging for log type 10
[2026-05-14T01:14:15Z WARN rayhunter::diag] warning: 73 leftover bytes when parsing Message
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] enabled logging for log type 11
[2026-05-14T01:14:15Z WARN rayhunter::diag] warning: 72 leftover bytes when parsing Message
[2026-05-14T01:14:15Z INFO rayhunter::diag_device] enabled logging for log type 13
[2026-05-14T01:14:15Z INFO rayhunter_daemon::diag] Starting recording with 198MB disk space available
[2026-05-14T01:14:16Z WARN wifi_station::monitor] WiFi client start attempt 1 failed: No such file or directory (os error 2), retrying in 30s
[2026-05-14T01:14:47Z WARN wifi_station::monitor] WiFi client start attempt 2 failed: No such file or directory (os error 2), retrying in 30s
[2026-05-14T01:15:17Z ERROR wifi_station::monitor] WiFi client failed to start after 3 attempts: No such file or directory (os error 2)
[2026-05-14T01:15:17Z INFO wifi_station::diagnostics] released kernel wakelock

[MoralCode]

I just recovered myself from this situation using this process

1. plug in orbic and run adb devices to ensure it is listed
2. adb shell (confirm i am on the correct device, i saw a WEBSERVER folder in the root/default directory)
3. exit adb shell and do adb forward tcp:8080 tcp:8080
4. webUI now accessible at localhost:8080

interestingly, when i went back into the config to disable client mode, i saw this message in red:
Failed: scan failed with -EIO; radio may be busy (module reload needed)

If the orbic doesnt appear to restart after clicking the option to save and restart, i just worked around that by restarting the device with the power button

This may have been as a result of me hitting the scan button before entering my SSID (unlikely) or Typing in my SSID incorrectly (probably what happened).

Hope this helps someone!

[untitaker]

Just to be sure that i understand the blast radius of this bug, does this procedure unbreak the orbic fully?

1. delete config file via adb
2. reboot device
3. install rayhunter again

i.e. is there a path to disable wifi client mode again or is the device kind of bricked?

[MoralCode]

i wouldnt consider this issue to be about a "bricked" device, just one where the wifi AP is not accessible to log into the webUI. Using ADB you can port forward the webUI port and access it essentially over USB, rather than wifi, working around the problem and letting you back in enough to change the broken setting and restore access via wifi.

i would not recommend deleting config files. While I have no experience with rayhunters codebase, i suspect that would be more likely to break something than it would help

[untitaker]

i wouldnt consider this issue to be about a "bricked" device, just one where the wifi AP is not accessible to log into the webUI.

yes i'm asking whether the wifi AP can be restored to "normal" operation (host mode) by uninstalling/disabling rayhunter through adb and rebooting.

i would not recommend deleting config files. While I have no experience with rayhunters codebase, i suspect that would be more likely to break something than it would help

I have experience with rayhunter's codebase and I recommend it ;) deleting the config file at /data/rayhunter/config.toml is a surefire way to disable rayhunter on boot until the next time you run the installer.

[MoralCode]

I have experience with rayhunter's codebase and I recommend it ;)

lol oops, i missed the "collaborator" label and the question phrasing of your procedure lol, sorry!

[spideramn1987]

Yes I was able to recover by repushing the package. I also later used usb adb to access and modify the configuration. I was able to disable it in the config and reboot. It just doesn't let me utilize the client mode for notifications. No bricking issues.

[RunningDroid]

I have a similar issue except the warning/error I get contains iw set type managed failed: command failed: Device or resource busy (-16)

Switching the hotspot from 5Ghz to 2.4Ghz seems to fix it but I suspect the other two errors have different root causes

[Huaian666]

this replaced 2 other tools in our stack. doing more with less is exactly what good software should do.

[spideramn1987]

this replaced 2 other tools in our stack. doing more with less is exactly what good software should do.

Not sure what you mean. I'm trying to use the tool, but it doesn't work on my device.

[iissmart]

Mine is also not working. After entering the wifi info and saving/restarting, the hotspot was no longer available. I connected via USB and used the adb commands from the earlier comment to regain access to the rayhunter webpage. Here are my logs:

R A Y H U N T E R 🐳
[2026-07-02T17:45:44Z INFO  rayhunter_daemon] Starting Diag Thread
[2026-07-02T17:45:44Z INFO  rayhunter_daemon] Starting UI
[2026-07-02T17:45:44Z INFO  rayhunter_daemon] Starting Key Input service
[2026-07-02T17:45:44Z INFO  rayhunter_daemon] create shutdown thread
[2026-07-02T17:45:44Z INFO  rayhunter_daemon] spinning up server
[2026-07-02T17:45:44Z INFO  rayhunter_daemon::diag] Using configuration for device: Orbic
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] Diag device initialization failed 1 times, retrying in 100ms: Failed to initialize /dev/diag: DIAG_IOCTL_SWITCH_LOGGING ioctl failed with error code -1
[2026-07-02T17:45:44Z INFO  wifi_station::diagnostics] acquired kernel wakelock
[2026-07-02T17:45:44Z INFO  rayhunter_daemon] The orca is hunting for stingrays...
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] Diag device initialization succeeded after 1 retries
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] retrieving diag logging capabilities...
[2026-07-02T17:45:44Z WARN  rayhunter::diag] warning: 329 leftover bytes when parsing Message
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] enabled logging for log type 1
[2026-07-02T17:45:44Z WARN  rayhunter::diag] warning: 298 leftover bytes when parsing Message
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] enabled logging for log type 4
[2026-07-02T17:45:44Z WARN  rayhunter::diag] warning: 140 leftover bytes when parsing Message
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] enabled logging for log type 5
[2026-07-02T17:45:44Z WARN  rayhunter::diag] warning: 168 leftover bytes when parsing Message
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] enabled logging for log type 7
[2026-07-02T17:45:44Z WARN  rayhunter::diag] warning: 122 leftover bytes when parsing Message
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] enabled logging for log type 10
[2026-07-02T17:45:44Z WARN  rayhunter::diag] warning: 73 leftover bytes when parsing Message
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] enabled logging for log type 11
[2026-07-02T17:45:44Z WARN  rayhunter::diag] warning: 72 leftover bytes when parsing Message
[2026-07-02T17:45:44Z INFO  rayhunter::diag_device] enabled logging for log type 13
[2026-07-02T17:45:44Z INFO  rayhunter_daemon::diag] Starting recording with 187MB disk space available
[2026-07-02T17:45:49Z WARN  rayhunter_daemon::update] update check failed: failed to query GitHub releases: error sending request for url (https://api.github.com/repos/EFForg/rayhunter/releases/latest)
[2026-07-02T17:45:54Z WARN  rayhunter_daemon::update] update check failed: failed to query GitHub releases: error sending request for url (https://api.github.com/repos/EFForg/rayhunter/releases/latest)
[2026-07-02T17:46:15Z INFO  wifi_station::monitor] wifi start blocked (likely AP busy), reloading module and creating STA first
[2026-07-02T17:46:15Z ERROR wifi_station::monitor] module reload failed: wlan.ko not found for kernel 3.18.48
[2026-07-02T17:46:15Z WARN  wifi_station::monitor] WiFi client start attempt 1 failed: scan failed with -EIO; radio may be busy (module reload needed), retrying in 30s
[2026-07-02T17:47:15Z INFO  wifi_station::monitor] wifi start blocked (likely AP busy), reloading module and creating STA first
[2026-07-02T17:47:15Z ERROR wifi_station::monitor] module reload failed: wlan.ko not found for kernel 3.18.48
[2026-07-02T17:47:15Z WARN  wifi_station::monitor] WiFi client start attempt 2 failed: scan failed with -EIO; radio may be busy (module reload needed), retrying in 30s
[2026-07-02T17:48:16Z INFO  wifi_station::monitor] wifi start blocked (likely AP busy), reloading module and creating STA first
[2026-07-02T17:48:16Z ERROR wifi_station::monitor] module reload failed: wlan.ko not found for kernel 3.18.48
[2026-07-02T17:48:16Z ERROR wifi_station::monitor] WiFi client failed to start after 3 attempts: scan failed with -EIO; radio may be busy (module reload needed)
[2026-07-02T17:48:16Z INFO  wifi_station::diagnostics] released kernel wakelock

It's not clear in the documentation - does it matter whether I'm trying to connect to a 2.4ghz or 5ghz network? Does it matter whether one or both of those are enabled/disabled in the device settings? Mine is set up with only the 2.4ghz hotspot checked, and I am trying to connect it to my 5ghz wifi network as a client, if that helps.