# Zero w WIFI died on new image

**URL:** <https://forum.core-electronics.com.au/t/zero-w-wifi-died-on-new-image/3050>\
**Category:** Raspberry Pi\
**Created:** [6 July 2018 02:00 UTC](https://forum.core-electronics.com.au/t/zero-w-wifi-died-on-new-image/3050 "2018-07-06T02:00:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg62756](https://avatars.discourse-cdn.com/v4/letter/g/8dc957/32.png) [@Greg62756](https://forum.core-electronics.com.au/u/Greg62756)\
**Post date:** [6 July 2018 02:01 UTC](https://forum.core-electronics.com.au/t/zero-w-wifi-died-on-new-image/3050/1 "2018-07-06T02:01:00Z")

</div>

I did a fresh install of stretch lite, added a blank ssh and the following wpa\_supplicant.conf to the sd, booted but get no wifi. If you go into raspi-config and set locale etc, reboot and then go to the wifi section it errors “could not communicate with wpa\_supplicant” if you do an ifdown it said “unknown interface” Tried a new sd but same issue. Was working fine until I had to do a reimage of the card…tried the stretch lite from June and the latest (2018-06-27-raspbian-stretch-lite) but no difference…I’m a noobie (more or less) so hoping it is an oversight on my part.  
wpa\_supplicant.conf is  
country=AU  
ctrl\_interface=DIR=/var/run/wpa\_supplicant GROUP=netdev  
update\_config=1  
Network={  
ssid=“my router name”  
psk=“my wpa password”  
key\_mgmt=WPA-PSK  
}

SOLVED:  
I did another reimage with the old stretch-lite (18-4-2018), booted it and went straight into raspi-config, wifi, set country code, set it to AU and exited …wifi came up and I can ssh to it again…don’t know what changed between working\not working\working. I rebooted the wifi router so maybe something was out of synch there? copying the wpa\_supplicant.conf & ssh to the boot sd doesn’t seem to work…I had to set it in raspi-config and activate ssh for it all to work.

---

<div class="post-metadata">

**Author:** ![Clinton](https://yyz2.discourse-cdn.com/flex028/user_avatar/forum.core-electronics.com.au/clinton/32/1515_2.png) [@Clinton](https://forum.core-electronics.com.au/u/Clinton)\
**Post date:** [6 July 2018 03:02 UTC](https://forum.core-electronics.com.au/t/zero-w-wifi-died-on-new-image/3050/2 "2018-07-06T03:02:46Z")

</div>

Hi Greg  
Try adding ap\_scan=1 on the line before update\_config=1 this tells the pi to look for networks.  
Though I think your problem is being caused by the capital ‘n’ in Network. So this would look like:  
country=AU  
ctrl\_interface=DIR=/var/run/wpa\_supplicant GROUP=netdev  
scan\_ap=1  
update\_config=1  
network={  
ssid=“my router name”  
psk=“my wpa password”  
key\_mgmt=WPA-PSK  
}

---

<div class="post-metadata">

**Author:** ![Greg62756](https://avatars.discourse-cdn.com/v4/letter/g/8dc957/32.png) [@Greg62756](https://forum.core-electronics.com.au/u/Greg62756)\
**Post date:** [6 July 2018 03:41 UTC](https://forum.core-electronics.com.au/t/zero-w-wifi-died-on-new-image/3050/3 "2018-07-06T03:41:48Z")

</div>

Thank goodness for guru’s!!! I changed the capital N to lower case n and it booted wifi…well done Clinton 😄

---

<div class="post-metadata">

**Author:** ![Clinton](https://yyz2.discourse-cdn.com/flex028/user_avatar/forum.core-electronics.com.au/clinton/32/1515_2.png) [@Clinton](https://forum.core-electronics.com.au/u/Clinton)\
**Post date:** [6 July 2018 05:10 UTC](https://forum.core-electronics.com.au/t/zero-w-wifi-died-on-new-image/3050/4 "2018-07-06T05:10:52Z")

</div>

No worries at all, glad I could get you out of trouble! Case errors on keywords are a necessary step on the path to guru.