Yesterday i rode the “London loop”. I have connected to Strava and Garmin Connect, but my ride was uploaded to neither of these parties when i chose to “Save & Exit” after my ride.
Unfortunately my ride displays only 18.6km, but i rode more than 24km…
Why are my data not uploaded?
Why are my total distance cut off by approx 6km?
That sounds like you had an issue with your internet connection near the end of the ride.
No, my internet connection was working just fine. I think the data is not being uploaded because data from my Garmin Fenix 5x (for the same session) was uploaded to Strava and Garmin Connect at the same time.
When a ride displays less on your dashboard then you actually did this almost always points to an issue with your connect to the Zwift servers.
You can manually upload the .fit file to Strava or other 3rd party site. The .fit files are located in \documents\Zwift\activities on PC and Mac and you can use this for iPad and iPhone: https://zwiftinsider.com/secret-feature-how-to-access-your-list-of-ride-fit-files-in-zwift-for-ios/
I am well aware of this issue, but this is not the fact in my case.
My biggest concern though is the fact that Zwift does not automatically upload data to my Strava and Garmin Connect accounts. They both have the status “connected” in Zwift. I really appreciated this feature, which worked flawlessly about a week ago.
I’ve been having this problem for the past week or so. TrainerRoad rides upload to Strava flawlessly, so I know it’s not my internet connection. I’ve done a complete uninstall of Zwift on Mac (using AppCleaner and removing data from my user directory) and reinstall with the same result. I’ve also disconnected and reconnected my Strava account. No luck. Jonas, you are not alone. There’s a problem somewhere and obviously not everyone is affected. Uploading rides manually using .fit files is getting old.
I’ve tried creating a new user on my mac, re-installing Zwift, registered a ride - no Strava upload. I’ve tracked open TCP connections during the various stages of running Zwift. Below is the output. I’ll leave it to the developers to determine if the EC2 instance some of us are connecting to isn’t uploading to Strava.
macbook:~ user$ netstat -f inet -n | grep tcp4 ## LOADING ZWIFT ##
tcp4 0 0 192.168.1.100.50149 13.33.74.123.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50148 172.217.12.196.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50147 54.213.251.126.443 ESTABLISHED
tcp4 0 0 192.168.1.100.50146 172.217.12.196.80 ESTABLISHED
macbook:~ user$ netstat -f inet -n | grep tcp4 ## PICKING A COURSE ##
tcp4 0 0 192.168.1.100.50157 13.33.74.123.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50156 54.68.162.92.443 ESTABLISHED
tcp4 0 0 192.168.1.100.50155 13.33.74.113.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50154 13.33.74.113.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50153 13.33.74.113.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50152 13.33.74.113.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50151 13.33.74.113.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50150 13.33.74.113.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50149 13.33.74.123.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50148 172.217.12.196.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50147 54.213.251.126.443 ESTABLISHED
tcp4 0 0 192.168.1.100.50146 172.217.12.196.80 ESTABLISHED
macbook:~ user$ netstat -f inet -n | grep tcp4 ## DURING A RIDE ##
tcp4 0 0 192.168.1.100.50183 52.40.201.140.443 ESTABLISHED
tcp4 0 0 192.168.1.100.50160 54.68.162.92.443 ESTABLISHED
tcp4 31 0 192.168.1.100.50159 54.213.251.126.443 CLOSE_WAIT
tcp4 0 0 192.168.1.100.50158 54.68.162.92.443 ESTABLISHED
tcp4 0 0 192.168.1.100.50157 13.33.74.123.80 ESTABLISHED
tcp4 0 0 192.168.1.100.50156 54.68.162.92.443 ESTABLISHED
macbook:~ user$ netstat -f inet -n | grep tcp4 ## EXIT AND SAVE ##
tcp4 0 0 192.168.1.100.50156 54.68.162.92.443 TIME_WAIT
tcp4 0 0 192.168.1.100.50183 52.40.201.140.443 TIME_WAIT
tcp4 0 0 192.168.1.100.50158 54.68.162.92.443 TIME_WAIT
tcp4 0 0 192.168.1.100.50160 54.68.162.92.443 TIME_WAIT
tcp4 0 0 192.168.1.100.50157 13.33.74.123.80 TIME_WAIT
Great work David Morgan! My guess, by reading your feedback, is that someone has tampered with the network settings on their EC2 instance… If this is the case, why hasn’t this been picked up by the Zwift development team/-testers?
I ‘think’ Zwift are aware of this (unfortunately can’t find the tweet) but check your account is connected in the mobile app. I’ve noticed that connecting Strava to Zwift, exiting or pressing back and going back into connections shows its not connected again.