Can't add services - SignalR cross domain is disabled
We are running into a problem, that is getting more and more serious, as the time passes. We have the issue, that we can't add services to our Essentials map with Chrome, Firefox or Edge. It only works with Internet Explorer. The error message appearing is "SignalR cross domain is disabled". Our IT is on it but they are struggling to find a solution. So maybe someone in the community had the same issue with their company's settings and have some suggestions for us?
This is part of the fiddler log for the following URL (token cut short):
https://maps.fugro.com/Geocortex/Essentials/RestManager/signalr/send?transport=serverSentEvents&connectionToken=25_OKZ0UQg4d1VU5Acc0T_ZAkVXSDl-pxGmWi_tV84E4PknSi6vptYR6MI8-zhjd61vMuciSMZ9qW1r7NBU2ye172EMvXd8A1qBHU8G0
{"H":"servicediscovery","M":"GetServiceConnections","A":["x2i1dg4r0p"],"I":1}
HTTP/1.1 403 Forbidden: SignalR cross domain is disabled.
Date: Wed, 20 May 2020 09:31:06 GMT
Server: Microsoft-IIS/10.0
Cache-Control: private
X-Powered-By: ASP.NET
X-Frame-Options: sameorigin
Content-Length: 0
Connection: close
As usual, any help is highly appreciated and thank you in advance :)
0
-
I can only confirm that I recently ran into the same issue as well. Unfortunately no fix, but perhaps this will also help to get some attention to this thread.
My guess would be that there is an invalid header sent with the request to SignalR. In my case, there is a proxy in front of the rest endpoint, but it is impossible to trace. A pointer on how to trace the incoming request to signalR would already be very helpful.0 -
Thanks Arjan! I see that you are located in the Netherlands, as is my company's headquarter. I wonder if there could be a connection? In any case, if you or your colleagues are able to find a solution, please don't forget to post the answer here :) 0 -
I believe the difference between IE and other browsers is the use of long polling versus SSE (server-sent-events). 0 -
Our IT has made some changes: They modified the reverse proxies to remove the Origin header for requests to our ArcGIS Portal. This is because when attempting to load a map service list the request failed if the Origin header was in place.
This had the consequence that it finally worked to add map services to Geocortex Essentials in Chrome but then I couldn't log into my REST endpoint of the ArcGIS Server anymore. Here we use the same authentication via ArcGIS Portal and it was unable to do so because of the Origin header.
They reversed the changes again and we are still on it...0 -
Timing is everything. We believe that we tackled this issue just a moment ago. The client is using an Apache server as their proxy. They added the following statements to their conf.d file in a virtual directory statement, so it only applies to the Geocortex url. ProxyPreserveHost On RequestHeader unset Origin Header set Access-Control-Allow-Origin "*" 0 -
Thanks Arjan! I don't understand much of what you said but I will forward it to our IT :) 0 -
We recently had to move our virtual machine with IIS / Geocortex Essentials installed behind an Azure Application Gateway. We now also receive the same error "SignalR cross domain is disabled" when using Edge, Chrome and Firefox, like the OP everything works as expected using IE.
Has anyone else had the same issue with an Azure Application Gateway? Does anybody in the community have a resolution?
0 -
Same issue here. Malcolm Walker , any thoughts?
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
8 kommentarer