Fix/Update wifi device name

Hello Start9 community,

I recently setup start9 on an x86 computer at home. I first setup start9 on an HP Elitedesk 800 g3 mini while I waited for my final hardware to arrive. With the HP everything went without issue and I was able to use the WIFI.

The trouble started when my final hardware…the GMKtec NucBox G3 Plus arrived. I thought it would be as simple as moving the NVMe SSD from the HP to the GMKtec but I was wrong. The first issue I ran into was fixed by following this guide. After that I was able to boot but startd was failing to start with these logs:

2025-09-20T21:02:51-06:00 2025-09-21T03:02:51.266805Z  INFO inner_main:setup_or_init: startos::bins::start_init: Loaded Disk
2025-09-20T21:02:51-06:00 2025-09-21T03:02:51.310417Z  INFO inner_main:setup_or_init:init:secret_store:init_postgres:bind: startos::disk::mount::util: Binding /embassy-data/main/postgresql to /var/lib/postgresql
2025-09-20T21:02:53-06:00 2025-09-21T03:02:53.657679Z  INFO inner_main:setup_or_init:init: startos::init: Opened Postgres
2025-09-20T21:02:53-06:00 2025-09-21T03:02:53.659946Z  INFO inner_main:setup_or_init:init: startos::init: Synced SSH Keys
2025-09-20T21:02:53-06:00 2025-09-21T03:02:53.680277Z  INFO inner_main:setup_or_init:init: startos::init: Opened PatchDB
2025-09-20T21:02:54-06:00 2025-09-21T03:02:54.651868Z DEBUG inner_main:setup_or_init:init:synchronize_wpa_supplicant_conf: startos::net::wifi: persistent: "/embassy-data/main/system-connections"
2025-09-20T21:02:54-06:00 2025-09-21T03:02:54.651969Z  INFO inner_main:setup_or_init:init:synchronize_wpa_supplicant_conf:bind: startos::disk::mount::util: Binding /embassy-data/main/system-connections to /etc/NetworkManager/system-connections
2025-09-20T21:02:54-06:00 2025-09-21T03:02:54.753168Z ERROR inner_main: startos::bins::start_init: wlp1s0: ERROR while getting interface flags: No such device
2025-09-20T21:02:54-06:00 2025-09-21T03:02:54.753911Z DEBUG inner_main: startos::bins::start_init: wlp1s0: ERROR while getting interface flags: No such device
2025-09-20T21:02:57-06:00 2025-09-21T03:02:57.532761Z ERROR inner_main:init: startos::context::diagnostic: Error: WiFi Internal Error: wlp1s0: ERROR while getting interface flags: No such device
2025-09-20T21:02:57-06:00 : Starting diagnostic UI
2025-09-20T21:02:57-06:00 2025-09-21T03:02:57.532844Z DEBUG inner_main:init: startos::context::diagnostic: Error { source:
2025-09-20T21:02:57-06:00 0: wlp1s0: ERROR while getting interface flags: No such device
2025-09-20T21:02:57-06:00 0: 
2025-09-20T21:02:57-06:00 Location:
2025-09-20T21:02:57-06:00 startos/src/util/mod.rs:163
2025-09-20T21:02:57-06:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2025-09-20T21:02:57-06:00 0: startos::net::wifi::synchronize_wpa_supplicant_conf
2025-09-20T21:02:57-06:00 at startos/src/net/wifi.rs:781
2025-09-20T21:02:57-06:00 1: startos::init::init
2025-09-20T21:02:57-06:00 at startos/src/init.rs:192
2025-09-20T21:02:57-06:00 2: startos::bins::start_init::setup_or_init
2025-09-20T21:02:57-06:00 at startos/src/bins/start_init.rs:23
2025-09-20T21:02:57-06:00 3: startos::bins::start_init::inner_main
2025-09-20T21:02:57-06:00 at startos/src/bins/start_init.rs:198
2025-09-20T21:02:57-06:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2025-09-20T21:02:57-06:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Wifi, revision: None }

Essentially the issue is that I was previously using wifi on the HP, but the GMKTec device uses a Realtek wifi card which does not work in start9. Since the wifi device does not work in start9 the wifi device was missing, and therefore causing start9 service to fail to start. After searching through the start9 rust code (thank you for making it OSS!) I was able to find the wifi device was being read from /media/embassy/config/config.yaml. In the config.yaml comment out or delete the line that says: wifi-interface: wlp1s0, then reboot and you should be good to go.

Hope this helps others.

1 Like

Do keep in mind that we donΒ΄t recommend using a WiFi connection for a server, which should have the most reliable connection available (Ethernet cable), since an intermittent or flaky Wifi signal can cause a whole lot of headaches.

WiFi connectivity will be deprecated in upcoming versions of StartOS for this very reason.

Being a server that should be accessed remotely from any number of client devices (Phones, Laptops etc) either on your LAN or remotely, this makes having your server sitting next to your router with an ethernet cable and out of the way, the best option.