#R-628

1 messages · Page 1 of 1 (latest)

obsidian sail
#

Good morning,

Since yesterday (after installing the latest a shadow update from jan 22) I'm getting the R-628 error code when trying to start Shadow. Yesterday morning I contacted the support team (ticket 477896) around 10am about this and was waiting for a solution. Around noon I tried connecting again and Shadow connected like normal so I closed my ticket thinking the issue had resolved itself on your end and it continued to work like normal the whole day after that.

Today, I tried to connect and same story: R-628 again.

So today I would like to repeat yesterday's inquiry to support:

Good morning,

After updating USB-drivers this morning, my Shadow will fail to connect and returns error code R-628, "Shadow PC connection timeout". I've tried restarting the Shadow app, my mac and my Shadow PC but with no success.

When I start my Shadow app it appears to be booting my Shadow PC like normal but just when I would normally switch to Shadow view, it fails and gives me this error.

I'm not sure what to do at this point so please help.

Best regards,

Additionally, I've tried unplugging my ethernet cable and connecting via WiFi and I also reset my router, to no avail.

I'm using on an old 27" iMac (Catalina 10.15.7) that otherwise has 0 issues with anything.

Please help, this is getting really frustrating.

obsidian sail
#

Update - got in contact with support via e-mail and Quintin suggested I install the BETA version. I did that, updated my Shadow but got the same error. Switched back to the official version and that didn't work. Rebooted my iMac and started the official version of Shadow and it immediately started my Shadow without any problems. What's going on? Seems to be a totally random error on the server-side of things.

brisk cosmos
#

R-628 and R-617 are tied, are you on Power Tier with Windows 11 ?

#

it works once every full shutdown, issue is with Windows 11 latest update, IPv6 on Shadow VM is not renewed and remains same, it prevent users from connecting to their VM using IPv6. There's 2 known workaround for now (as switch to IPv4 fallback in Shadow launcher doesn't work all the time).

  1. on error, shutdown shadow from launcher help pane, wait, start again (Windows seems to usualy attempt to renew6 every 2 cold boot)
  2. disable IPv6 on your local machine to force usage of IPv4
#

this workaround usualy leave the VM without or with broken IPv6 connectivity.
to test :

ping -6 www.google.com

if it works, nothing to do, if it fails (this also restore IPv6 connection from launcher) :

ipconfig /renew6
pseudo zephyr
#

How does the QA team let this by when there is clearly an issue, i reported this in chat. Kept dropping out, tried the IPV4 still not much luck. I have 1gb/1gb never had issues before. Shadow i ask you to do more duedilligance on update rollouts.

scenic river
#

I've had the service for about 2 weeks now and barely got it to work

pseudo zephyr
#

ave had it for over 3yrs

brisk cosmos
obsidian sail
#

The issue has not returned today and seems to have resolved itself without any further changes on my part.

#

And thank you @brisk cosmos for all you input in this issue. If the error ever returns, I'll be sure to follow up on your suggestions!

obsidian sail
#

@brisk cosmos just now I got the R-617 error. I disabled ipv6 on my local machine and that instantly fixed it (after rebooting). Thanks again!!