Try our conversational search powered by Generative AI!
AI OnAI Off
Real-time update error after upgrading to Episerver 11.11.3.0
Hello,
As you mentioned that Websockets is enabled on the server so is both sites(11.11.2.0 and 11.11.3.0) on the same server?
Thanks
Ravindra
Apr 06, 2019 7:25
@Quan Mai:
The console shows something like this message:
widgets.js:2 WebSocket connection to 'wss://zzz.zzz.nl/EPiUI/Shell/socket/endpoint/' failed: Error during WebSocket handshake: Unexpected response code: 200
@Ravindra:
Both sites are on the same server.
Apr 09, 2019 9:22
I've just tested another upgraded site: the message popup did not show at 11.11.2, but after upgrading to 11.11.3 it did.
11.11.2
Request URL: wss://zzz.zzz.nl/EpiserverUI/Shell/socket/endpoint/
Request Method: GET
Status Code: 101 Switching Protocols
11.11.3
Request URL: wss://zzz.zzz.nl/EpiserverUI/Shell/socket/endpoint/
Request Method: GET
Status Code: 200 OK
After downgrading Episerver.CMS to 11.11.2 and Episerver.CMS.UI to 11.17.0 the problem did not occur anymore.
Edited,
Apr 09, 2019 14:11
Is this error registerer as a bug so Episerver can solve this in a future release?
May 03, 2019 14:55
It is not registered as a bug, but is still being investigated by Episerver.
The problem only occurs when accessing the Episerver backend through our load balancer.
May 03, 2019 14:58
It happens in our test enviroment as well. We don't have a load balancer but we do have a reverse proxy.
Upgraded today from 11.11.1 to 11.11.3 and it was working fine before that.
Edited,
May 03, 2019 15:02
Don't think we do actually, but like I said it was working fine with version 11.11.1 (and earlier releases).
May 03, 2019 15:29
Added a bug report...
For us this occurs in load balanced production sites, and even in production-like non-load-balanced in customers staging environments. It doesn't occur locally.
The only difference noticed is that we have netstandard + netstandard2.0 etc. on local dev environments, but not on stage etc.
Worth notice anyway... Don't know if that has any relevancy, but it could help track the issue, if it has any relevancy...
May 14, 2019 9:14
@jonas, @john, @alexander - could you please check and give me the exact versions of each EPiServer nuget package that you had before and after the upgrade.
the minor upgrade 11.11.2 to 11.11.3 could not have caused this on its own. something else must have been also upgraded.
thanks
May 17, 2019 9:06
EPiServer.CMS 11.11.1 => 11.11.3
EPiServer.CMS.AspNet 11.11.1 => 11.11.3
EPiServer.CMS.Core 11.11.1 => 11.11.3
EPiServer.CMS.TinyMce 2.7.1 => 2.8.0
EPiServer.CMS.UI 11.17.0 => 11.19.2
EPiServer.CMS.UI.AspNetIdentity 11.17.0 => 11.19.2
EPiServer.CMS.UI.Core 11.17.0 => 11.19.2
EPiServer.Commerce 12.16.0 => 13.2.0
EPiServer.Commerce.Core 12.16.0 => 13.2.0
EPiServer.Commerce.FindSearchProvider 10.0.2 => 10.1.0
EPiServer.Commerce.UI 12.16.0 => 13.2.0
EPiServer.Commerce.UI.CustomerService 12.16.0 => 13.2.0
EPiServer.Commerce.UI.ManagerIntegration 12.16.0 => 13.2.0
EPiServer.Find.Commerce 11.0.2 => 11.1.0
EPiServer.Framework 11.11.1 => 11.11.3
EPiServer.Framework.AspNet 11.11.1 => 11.11.3
May 17, 2019 9:15
EPiCode.InspectInIndex 1.4.0 => 1.5.0
EPiServer.AddOns.Helpers 0.3.0.0 => 0.4.0.0
EPiServer.Azure 9.4.2 => 9.4.4
EPiServer.CMS 11.3.3 => 11.11.3
EPiServer.CMS.AspNet 11.3.3 => 11.11.3
EPiServer.CMS.Core 11.3.3 => 11.11.3
EPiServer.CMS.TinyMce 1.0.0 => 1.0.0
EPiServer.CMS.UI 11.2.5 => 11.19.1
EPiServer.CMS.UI.Core 11.2.5 => 11.19.1
EPiServer.Find 12.7.1 => 13.0.5
EPiServer.Find.Cms 12.7.1 => 13.0.5
EPiServer.Find.Framework 12.7.1 => 13.0.5
EPiServer.Forms 4.10.0 => 4.10.0
EPiServer.Forms.Core 4.10.0 => 4.10.0
EPiServer.Forms.UI 4.10.0 => 4.10.0
EPiServer.Framework 11.3.3 => 11.11.3
EPiServer.Framework.AspNet 11.3.3 => 11.11.3
EPiServer.Logging.Log4Net 2.2.1 => 2.2.2
EPiServer.Packaging 3.4.0 => 3.4.0
EPiServer.Packaging.UI 3.4.0 => 3.4.0
EPiServer.Search 9.0.1 => 9.0.3
EPiServer.ServiceLocation.StructureMap 2.0.0 => 2.0.1
Geta.SEO.Sitemaps 2.0.2 => 2.0.13
As mentioned previously:
After downgrading Episerver.CMS to 11.11.2 and Episerver.CMS.UI to 11.17.0 the problem did not occur anymore.
May 17, 2019 9:47
would it be possible for you to downgrade just the CMS.UI to 11.19.0?
CMS.UI 11.19.1 is supposedly the one that introduced the issue you are facing
once we confirm I will schedule a fix in the upcoming CMS.UI package
May 17, 2019 9:56
No, if I try to do that I am asked to also downgrade Episerver.CMS to 11.11.2, and Episerver.CMS.UI.Core to 11.19.0
Edited,
May 17, 2019 10:07
I've just tried on a clean Alloy installation and I managed to downgrade to CMS.UI 11.19.0 without touching the Core packages.
My packages.config:
before:
<package id="EPiServer.CMS.AspNet" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.CMS.Core" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.CMS.TinyMce" version="2.6.5" targetFramework="net461" />
<package id="EPiServer.CMS.UI" version="11.19.2" targetFramework="net461" />
<package id="EPiServer.CMS.UI.AspNetIdentity" version="11.19.2" targetFramework="net461" />
<package id="EPiServer.CMS.UI.Core" version="11.19.2" targetFramework="net461" />
<package id="EPiServer.Framework" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.Framework.AspNet" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.Search" version="9.0.1" targetFramework="net461" />
<package id="EPiServer.Search.Cms" version="9.0.1" targetFramework="net461" />
<package id="EPiServer.ServiceLocation.StructureMap" version="2.0.1" targetFramework="net461" />
after:
<package id="EPiServer.CMS.AspNet" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.CMS.Core" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.CMS.TinyMce" version="2.6.5" targetFramework="net461" />
<package id="EPiServer.CMS.UI" version="11.19.0" targetFramework="net461" />
<package id="EPiServer.CMS.UI.AspNetIdentity" version="11.19.0" targetFramework="net461" />
<package id="EPiServer.CMS.UI.Core" version="11.19.0" targetFramework="net461" />
<package id="EPiServer.Framework" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.Framework.AspNet" version="11.11.3" targetFramework="net461" />
<package id="EPiServer.Search" version="9.0.1" targetFramework="net461" />
<package id="EPiServer.Search.Cms" version="9.0.1" targetFramework="net461" />
<package id="EPiServer.ServiceLocation.StructureMap" version="2.0.1" targetFramework="net461" />
The last time we upgraded our internal dependency on Core's packages was in https://nuget.episerver.com/package/?id=EPiServer.CMS.UI.Core&v=11.14.0
All versions after that depend on EPiServer.CMS.AspNet (≥ 11.11.0 && < 12.0.0)
May 17, 2019 11:13
I've managed to downgrade, I'm now using
<package id="EPiServer.CMS.UI" version="11.19.0" targetFramework="net472" />
<package id="EPiServer.CMS.UI.Core" version="11.19.0" targetFramework="net472" />
The problem does not occur anymore.
May 17, 2019 11:58
And after I upgraded only EPiServer.CMS.UI.Core to 11.19.1 the problem came back again.
Edited,
May 17, 2019 12:43
Am I to understand this is a confirmed bug in 11.19.1? Any information on when the upcoming release with the fix will be available? This issue is stopping us from releasing an upgraded version of our site...
May 22, 2019 12:38
According to a colleague an upgrade was available at Nuget-feed today and it worked perfectly by just doing the Nuget-upgrade...
Edited,
May 28, 2019 17:33
Please use https://nuget.episerver.com/package/?id=EPiServer.CMS.UI&v=11.20.1
It contains the fix you need, let me know if you encounter any issues.
May 28, 2019 20:25
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Hello,
After upgrading to Episerver 11.11.3.0 I get the "real-time update" error when switching from the admin panel to the edit panel.
Websockets is enabled on the server. A similar Episerver site which was recently upgraded to 11.11.2.0 does not show this error.
Any ideas, anyone?
John Ligtenberg