What exactly did you try? Did you do a particle keys server and particle keys doctor <device_id>? What was the console output when running those commands?
Since the underlying issue with the Cores was a DNS resolution problem, are you behind a DNS proxy of some sort (more common on a corporate network)? If so, clearing the DNS cache may help.
yes I did particle keys server and particle keys doctor <device_id>
oputput was…
New Key Created!
Saved!
Saved!
attempting to add a new public key for device
submitting public key succeeded!
Okay! New keys in place, your device should restart.
I am just doing this at home, dont think there has been made any changes regarding the router… how can I clear DNS cache?
FYI: In a corporate network, we typically host our own internal DNS servers. Depending on the config, internal DNS servers may purposefully retain older, expired, DNS entries. We can set those servers to a set retention period which overrides the TTL settings that Particle may specify. If you don’t have a DNS server, and your router does not cache DNS entries, then you most likely don’t have any control over DNS resolution. You may also find that DNS servers hosted by your ISP also retain DNS entries past their designated expiration period. If that is the case, again, you have no control over the server… but you could change your router’s DNS server to something like 1.1.1.1 (cloudfare) or 8.8.8.8 (google). Again, DNS caching may or may not be your issue.
I’ll let someone like @ScruffR or @rickkas7 diagnose further. I don’t know all the CLI commands or the intricacies at this level.
@Mquist, have you also followed the other instructions to reflash/update the CC3000 firmware and flash a new user firmware and cleared and reapplied the WiFi credentials.
particle flash --usb cc3000
particle flash --usb tinker
particle keys server
particle keys doctor
And then in Listening Mode reapply the WiFi credentials
@Mquist, I am having the same issue on one of my Cores which ran fine until recently. I also tried the exact same things you did without success. It may still be a DNS issue. I pinged @jvanier to see if he had any insights.
now I was just opening an old photon (bought it 2 years ago or something) and I was having problem with it stuck at auto-updata end breating magenta, I did some search and ended trying
particle keys server
particle keys doctor
but with no success… this was the output
c:\OpenSSL-Win32\bin>particle keys server
Okay! New keys in place, your device will not restart.
c:\OpenSSL-Win32\bin>particle keys doctor 320040000447343337373739
New Key Created!
Saved!
Make sure your device is in DFU mode (blinking yellow), and that your computer is online.: Error writing key to device.: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Error during download get_status
C:\Users\bjarn_000\Downloads>particle flash --serial bootloader-0.7.0-photon.bin
! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE
sending file: bootloader-0.7.0-photon.bin
Flash success!
but still no success, it fast blinks cyan and then red
EDIT!!
Now I could use the particle keys doctor with success…
now it breaths cyan and I can upload program to it thanks @peekay123