I have been having issues with your New Zealand based CDN Edge location, the assets need to be purged at that edge location. I know this because I’ve had to use a VPN to Australia to even open the Zwift app. When i’m not using a VPN, the logs for the AKL assets are failing, but SYD is ok. It’s a bit ridiculous that I have to do this in order to open Zwift, so can you just purge the launcher assets at this location so I don’t need to use a VPN every time I want to start up Zwift?
I didn’t think that Zwift used a CDN. The services run on Amazon via AWS, but I didn’t think that CloudFront was used.
I don’t doubt that something is going wrong for you, but I’m not sure that it’s anyrhing to do with a CDN.
I realise it’s anecdotal but my son uses Zwift in NZ with no problems, as do I’m sure a lot of other people (otherwise we’d have heard a fair number of complaints here).
If this has been an ongoing issue for you - please give us some more details that we can use to figure out what’s happening. Assuming you don’t use VPN please let us know where you’re stuck during the launch:
1: How do you launch Zwift on your M1 Mac? Are you kicking off from ZwiftLauncher binary, or the ZwiftAppSiilcon binary?
2. Assuming you use ZwiftLauncher to initialize the game - are you able to get past the Let’s Go screen?
3. Do you get stuck on the blue images?
4. Do you make it to the game’s home screen?
5. Are you able to select and activity and drop into a world where your avatar spans?
That’s really not a helpful or supportive response if i’m being honest. I’m only reporting this now as i’ve been experiencing this issue for over a month and it’s only purely out of frustration of this launcher failing 9/10 times when trying to connect normally from Wellington that I seem to experience it. The logs for the ZwiftLauncher library indicate that the CDN it is trying to pull content from is based in AKL on Cloudfront. I’m sure if it was a bigger issue perhaps you would have more people reporting it, but it’s intermittent, so if you launch it enough times, you may just get through. Maybe that’s fine for others, but it’s not a great user experience for me. I’ll attach some logs so you can see the errors i’m getting when it tries to connect.
Also the times I do get to the login screen when not on VPN, it doesn’t seem to accept my password for auto-login and some of the assets are not fully loaded (like background missing). When I do get past this eventually, the game works. As I said before though, when I am connected via VPN to Sydney, I have no issues whatsoever.
I also get a lot of the below on startup, also i’m quite open to the fact that it may not be the CDN, but that’s what i’m seeing in the logs and based on behaviour when connecting to Sydney it was the most logical diagnosis.
@karls_877
I appreciate that you’re very capable of looking at logs and going down those rabbit holes on your own. You’re jumping ahead and what’s needed on my end is a description / screenshots of what’s you’re seeing.
This context you provided is what I was after, thank you.
Based on your report of losing autologin credentials - there may be some web security configurations clearing those out on your Macbook. Is this a work-issued computer, or perhaps a personal one with beefier security than the average person would have in place?
Let’s also take a secondary diagnostic tack: scanning through your server log history - I only see you log in from an M1 Macbook Pro. If you install the main Zwift app on your iPhone - are you able to log in / out succesfully without having to VPN to Sydney? On mobile devices especially - it’s important to save-and-exit (or trash-and-exit) your session to terminate the app. If you just swipe the app into the background, it neither logs you off the server nor terminates the app locally.
More context on the auto-login stuff, it seems to be when I connect to AKL50-C2, the auto-login works ok, but when I get another node, it doesn’t seem to behave and I have to re-type in my credentials.
This is a Work laptop, but I am an admin of the device and the AV software and have deactivated any security tooling and firewalls that could potentially interfere with zwift, just to be 100% sure when diagnosing. Zwift has been working perfectly fine for me for over a year on this device right up until around mid to late June. I just happened to be using the VPN by accident one day for Sydney and noticed that Zwift turned on no problems straight away, which was not a behaviour I had been used to for the past month and a half.
I don’t have Zwift on the iPhone, but i’m going to download it now and will let you know the results.
I’ve tried the iPhone and haven’t seen any specific oddness. I did notice errors in the logs, but it didn’t seem to impact the login so could be a red herring. I also wasn’t connected to any devices, just spectating.
[11:34:57] [ZNet] RRPC (GetContent) retrying...
[11:34:57] CloudSync ---UploadToCloud OK workouts.files
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 100.81.203.62 (pdp_ip0) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 10.146.212.217 (pdp_ip1) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 10.186.0.32 (pdp_ip2) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 10.146.212.217 (ipsec1) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 192.168.1.3 (en0) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 192.0.0.6 (ipsec5) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 192.0.0.6 (ipsec6) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 10.146.212.217 (ipsec7) [65] No route to host
[11:34:57] [ERROR] LAN Exercise Device: Error sending PTR query to 10.146.212.217 (ipsec8) [65] No route to host
If you pair the iPhone to your trainer and continue to test for oddness and don’t see any under normal use - we can probably rule out that iPhone and by extension - your local network and also the network between your ISP and Zwift are probably working as they should.
This brings us back to that Macbook and something on it being the culprit. Once you’ve deactivated the corporate security - what happens? Is it any better?
I have been diagnosing this for a bit, clean zwift install, clean mac install, no security tooling, different macbook etc. I noticed yesterday that I was having intermittent connectivity drops on rubygems.org, which lead me to an article about IPv6 issues for that domain. The suggestion was to set IPv6 to link-local on the Network settings in Mac. I’ve done this and it now seems to have no difficulty launching the Zwift launcher and logging in successfully. It seems like it might be an issue with my ISP Orcon and their IPv6 routing behaviour, but I can’t really say for certain.
I’m sure you can close this now as it is resolved from my end, thanks for your help!