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

GE does not communicate with servers - update not possible

Version 6.1.1.0 doesn't communicate since some hours with the Garmin servers. --> no update of my new fenix 5x is possible. :-( :(
  • Come on Garmin, this is getting ridiculous!

    This is the third time I have communicated this issues on this forum and have tried various ways from my end to fix it. The latest update of GE had me hoping this issue would be resolved - noting v5.8 said it had.

    So why after several updates, reinstalls, changing proxies- checking proxies - wifi v ethernet the list goes on to why each and every time I plug my Fenix 5x in I get this issues? Let alone the Maps Update that hasn't worked for months as well!!!

    It seems there is a growing mass of people have reached a point where those of us who have been long paying customers have to start looking elsewhere. I appreciate the Beta's etc etc, but from my own experience I have had more issues with the F5X compared to the previous Fenix' I have owned.

    If anyone, anyone has any ideas that I haven't tried please one last try and if anyone from Garmin reads this please reach out, I have tried contacting from Australia and even spoke to the retalier I purchased the device from and alas no joy.

    For a $700 dollar product and now the release of the FR645 I am justifiably nervous if the FX5 plus or what next model comes in this line goes the same pathway to have any faith in.

    Cam
    Australia
  • I've never seen that issue in years of owning Garmin products. The FAQ for it is here https://support.garmin.com/faqSearch/en-US/faq/content/uZQHyc3C4s2S0wfUYR2QY9 and often the cause is at the users end. If after following the FAQ you still cannot connect call Product Support for detailed troubleshooting of your system.
  • Thanks, on this users end I have tried as you have previously suggested the FAQ in relation to this.

    Just now another piece of advice was to remove F5X and re-add it, now I can't even 'sign in' to add device as its saying ' we are having issues communicating with our servers'.

    When I check whether I can access said servers, sure enough I can.

    I'm at a loss.

    CAM
  • Then call Product support for help so they can, if necessary, remotely access your PC.
  • SUSSAMB, I will message / call Garmin and advise outcome.

    Thanks
  • Former Member
    0 Former Member over 7 years ago
    I've had the same issue, and submitted a help request to Garmin a week ago - but still have had no response. Any idea if GE writes any information to log files so I can attempt to resolve it myself? The FAQ provides nothing useful.
  • This seems to be am issue that is getting worse and worse over the last few months. I never had "communication with server" issues and now I seems to get them all the time. I generally retry and retry and it eventually works.
  • This seems to be am issue that is getting worse and worse over the last few months. I never had "communication with server" issues and now I seems to get them all the time. I generally retry and retry and it eventually works.


    I too have contacted Garmin, nothing heard yet either. On Monday I will try and ring again. I have tried everything stated here and in the FAQ section. Interesting it doesn't happen on my Fenix 3HR or any other Garmin product its just the F5X that this issue consistently happens with.

    Now I have also the 'maps cannot be authenticated' issue occurring!
  • Maps cannot be authenticated means that your device doesn't have the necessary unlock file, if so either the device is faulty or the file is missing or corrupted. Try downloading the map again.

    Given too that you only get the server issue with your 5X then I suspect it has an issue.
  • This seems to be am issue that is getting worse and worse over the last few months. I never had "communication with server" issues and now I seems to get them all the time. I generally retry and retry and it eventually works.


    Never seen that error, and as noted here and elsewhere it normally points to a local issue rather than a Garmin one.