This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WiFi error 0300 955 Solar v15.19

When I try to sync over WiFi I get error 0300. If I test the connections from the phone, all the networks in range are successful.

I tried restarting the router and the watch and adding another network none of which made any difference. I am on 15.19. This has worked previously but I am not sure if it has ever worked on 15.19.

Anyone else seeing this? 965 users seem to be getting it.

Top Replies

All Replies

0 LinAlan over 2 years ago

I'm seeing the same here. Testing from iOS app shows okay.

I have WiFi enabled on the 955, but I guess it's probably been syncing over Bluetooth when I get in range of my phone after getting home. I even disabled Bluetooth and WiFi sync is a negative w/the 0300 error.

0 Albertone over 2 years ago

The same goes for me. By the way, I've never had any problems with the wi-fi before

0 SvH0822 over 2 years ago

dasselbe seit 06.06.2023 bei mir,
heute auf werkseinstellung gesetzt aber keine lösung,
wlan synchronisation fehlgeschlagen, fehlermeldung 0300, beim "testen" mit der app

the same for me since 6/6/2023, set to factory setting today but no solution, WLAN synchronization failed, error message 0300, when "testing" with the app

0 franks7890 over 2 years ago

I get the same error message when trying to do a software-update over Wifi.

This worked before also with version 15.19.

0 drcyclist21 over 2 years ago

Tried even connecting with the phones wifi.... After factory reset, and losing all my changes on workout profiles... It looks like a joke, because I've migrated to beta software because I couldn't sync over Bluetooth, and now it's wifi... It's a damn expensive watch to have this issues...

0 VelinDilov over 2 years ago

Same error. I tried two rooters no connection, it's from Garmin.

0 BillCQ over 2 years ago

Seeing same error, 955 Solar 15.19. Remove wifi and reconnect, no difference.

+1 Garmin-Sierra over 2 years ago

All,

This has been fixed. If you still see an error message, please start a new thread.