Home

[Resolved] WVD web client connection errors in Google Chrome and Microsoft Edge (Chromium)

%3CLINGO-SUB%20id%3D%22lingo-sub-1242555%22%20slang%3D%22en-US%22%3ERe%3A%20WVD%20web%20client%20connection%20errors%20in%20Google%20Chrome%20and%20Microsoft%20Edge%20(Chromium)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1242555%22%20slang%3D%22en-US%22%3EHi%2C%20probleem%20seems%20to%20be%20resolved%3F%20Our%20users%20can%20log%20back%20in%20using%20Chrome%2FEdge%20Chromium.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1248021%22%20slang%3D%22en-US%22%3ERE%3A%20WVD%20web%20client%20connection%20errors%20in%20Google%20Chrome%20and%20Microsoft%20Edge%20(Chromium)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1248021%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20fixed%20in%20Production.%20A%20fix%20for%20pre-production%20environments%20will%20roll%20out%20on%20the%20normal%20update%20schedule.%20Users%20in%20production%20should%20not%20be%20impacted%20any%20longer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1233810%22%20slang%3D%22en-US%22%3E%5BResolved%5D%20WVD%20web%20client%20connection%20errors%20in%20Google%20Chrome%20and%20Microsoft%20Edge%20(Chromium)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1233810%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EUPDATE%3A%26nbsp%3B%3C%2FSTRONG%3EThis%20issue%20has%20been%20%3CSTRONG%3E%3CEM%3Eresolved%20in%20Production%3C%2FEM%3E%3C%2FSTRONG%3E.%20A%20fix%20for%20pre-production%20environments%20will%20roll%20out%20with%20normal%20service%20updates.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20number%20of%20users%20have%20reported%20issues%20connecting%20to%20the%20WVD%20web%20client%20using%20both%20Microsoft%20Edge%20(Chromium)%20and%20Google%20Chrome.%20The%20February%20release%20of%20the%20new%20Chromium%2080%20engine%20-%20used%20by%20both%20Edge%20and%20Chrome%20-%20included%20changes%20SameSite%20cookie%20classification.%20More%20information%20can%20be%20found%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fblog.chromium.org%2F2020%2F02%2Fsamesite-cookie-changes-in-february.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EChromium%20blog%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Fweb.dev%2Fsamesite-cookies-explained%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EChromium%20developer%20guidance%3C%2FA%3E.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20working%20on%20rolling%20out%20a%20fix%20to%20production.%20In%20the%20interim%2C%20please%20use%20the%20following%20workarounds%20to%20continue%20using%20the%20web%20client%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EUse%20%3CA%20href%3D%22https%3A%2F%2Fwww.mozilla.org%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMozilla%20Firefox%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EIn%20your%20Microsoft%20Edge%20(%3CSTRONG%3EEdge%3A%2F%2Fflags%3C%2FSTRONG%3E)%20or%20Google%20Chrome%20(%3CSTRONG%3EChrome%3A%2F%2Fflags%3C%2FSTRONG%3E)%20browser%2C%20disable%20both%20the%20%3CSTRONG%3ESameSite%20by%20default%20cookies%3C%2FSTRONG%3E%20and%20%3CSTRONG%3ECookies%20without%20SameSite%20must%20be%20secure%3C%2FSTRONG%3E%20flags.%26nbsp%3BPlease%20note%20the%20warning%20presented%3A%20%22%3CSPAN%3E%3CEM%3EBy%20enabling%20these%20features%2C%20you%20could%20lose%20browser%20data%20or%20compromise%20your%20security%20or%20privacy.%20Enabled%20features%20apply%20to%20all%20users%20of%20this%20browser.%3C%2FEM%3E%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EWe%20will%20post%20an%20update%20on%20this%20thread%20when%20a%20fix%20is%20available%20in%20production.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1233810%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChrome%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EEdge%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eweb%20client%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWVD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Microsoft

UPDATE: This issue has been resolved in Production. A fix for pre-production environments will roll out with normal service updates.

 

A number of users have reported issues connecting to the WVD web client using both Microsoft Edge (Chromium) and Google Chrome. The February release of the new Chromium 80 engine - used by both Edge and Chrome - included changes SameSite cookie classification. More information can be found on the Chromium blog and Chromium developer guidance

 

We are working on rolling out a fix to production. In the interim, please use the following workarounds to continue using the web client:

 

  • Use Mozilla Firefox
  • In your Microsoft Edge (Edge://flags) or Google Chrome (Chrome://flags) browser, disable both the SameSite by default cookies and Cookies without SameSite must be secure flags. Please note the warning presented: "By enabling these features, you could lose browser data or compromise your security or privacy. Enabled features apply to all users of this browser."

We will post an update on this thread when a fix is available in production.

2 Replies
Highlighted
Hi, probleem seems to be resolved? Our users can log back in using Chrome/Edge Chromium.
Highlighted

This is fixed in Production. A fix for pre-production environments will roll out on the normal update schedule. Users in production should not be impacted any longer.