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

Is Garmin Connect down at the moment?

Former Member
Former Member
Hi

When connecting to https://connect.garmin.com/modern/ using firefox, I get the following response (inside the blue border):

Internal Error

Sorry, we encountered an internal error.

Details
User doesn't have proper roles.
com.garmin.web.DashboardController.populateDefaultModel(DashboardController.java:626)
com.garmin.web.DashboardController.dashboard(DashboardController.java:142)
sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)
org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:219)
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:746)
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:687)
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80)
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:915)
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:811)
javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:796)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.garmin.web.service.util.XHttpMethodOverrideFilter.doFilterInternal(XHttpMethodOverrideFilter.java:62)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.garmin.web.filter.sso.AuthenticationFilter.doFilter(AuthenticationFilter.java:161)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:44)
org.jasig.cas.client.util.AssertionThreadLocalFilter.doFilter(AssertionThreadLocalFilter.java:63)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
org.jasig.cas.client.util.HttpServletRequestWrapperFilter.doFilter(HttpServletRequestWrapperFilter.java:86)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.validation.AbstractTicketValidationFilter.doFilter(AbstractTicketValidationFilter.java:389)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.authentication.UnprotectedAuthenticationFilter.doFilter(UnprotectedAuthenticationFilter.java:98)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.session.SingleSignOutFilter.doFilter(SingleSignOutFilter.java:92)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.util.ExcludedURLDetectionFilter.doFilter(ExcludedURLDetectionFilter.java:68)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.web.filter.sso.ConditionalFilter.doFilter(ConditionalFilter.java:81)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:197)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1805)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
java.lang.Thread.run(Thread.java:745)


Will this explain the sync issues I'm having (via mobile app and express)
Werner
  • Yeah, a cloud service should never be down.


    +1 to this. Very disappointing!
  • Former Member
    0 Former Member over 9 years ago
    Pretty gutted

    I'm new to Garmin, just bought my Forerunner 920XT yesterday... been dying to sync my activities and get it all working. Hope this downtime doesn't last too much longer!!

    Does this happen very often??
  • Sorry, there's no english text on Garmin pages:
    http://www.garmin.com/de/support
    Aufgrund von Wartungsarbeiten kann es in der Nacht von Mittwoch, den 11.11.2015 auf Donnerstag, den 12.11.2015 für eine Dauer von ca. drei Stunden (von ca. 4:00 Uhr bis 7:00 Uhr) zu Einschränkungen bei der Erreichbarkeit von Garmin Connect kommen. Vielen Dank für Ihr Verständnis.


    You can check status on https://connect.garmin.com/de-DE/status

    Google translation:
    Due to maintenance work it can on the night of Wednesday, 11/11/2015 on Thursday 11/12/2015 for a period of about three hours (approximately 4:00 clock until 7:00 clock) to restrictions on the accessibility of Garmin Connect come. Thank you for your understanding.


    Does this happen very often??


    Oh no, apart from the fact that some maintenance on german Garmin forum took about a week - scheduled downtime.
  • Former Member
    0 Former Member over 9 years ago
    I am also new to the great world of Garmin. On all the reviews of their products I have read everyone loves the product and only complains about Connect. Let's just hope this is the update that fixes everything.
  • Former Member
    0 Former Member over 9 years ago
    fingers crossed they don't lose all of our data
  • Garmin in poor communication shock.....

    If Apple ever nail a sports watch Garmin will be in trouble.
  • In my experience, there are always bugs and growing pains when a major change in any computer system is implemented. It will be interesting to see what happens here.

    What I have found with Garmin and Connect is that there are issues from time-to-time but they mostly tend to be fixed relatively quickly. Often those issues are created by them implementing improvements or adding new functionality. Connect is a lot better these days vs. what it was 6 months ago.

    This is the first time in years that I recall a planned maintenance shutdown.
  • Former Member
    0 Former Member over 9 years ago
    If your business is depending on cloud (and Garmin is moving in that direction), then you need parallel servers, so you can play with one while users are using other.

    Garmin has best smartwatches on market, with battery life over 3 weeks and great sports features, but don't know how to market (and design) them, so Samsung and Apple are selling more. Connect problems suggest they also don't realize how important is this service for user experience. They are currently ahead of competition with their products, but in the end it might prove not to be enough.
  • Former Member
    0 Former Member over 9 years ago
    It would have been nice to have known this was occurring, maybe a push notification on your connect app and maybe a splash screen online saying down for maintenance. But I do agree that a cloud based serve should never be down. And you should always be able to login and shnc with your phone etc even if the website is being maintenanced this way once it's back up your phone just syncs with the Web. This is very frustrating because it practically make the device on my wrist nothing more than a fancy watch.
  • It's still down, 9 to 10 hours after they started, there must be great improvements.
    It will certainly be interesting to see what they have accomplished.


    I'm loving this blind optimism ! let us see, then...

    There was a warning when i was last on GC on Tuesday am, that there would be downtime in the early hours of Thursday (European time), so it's not out of the blue.

    MB