“Failed to initialize site “ Error when converting Geocortex from http to https
“Failed to initialize site “ Error when converting Geocortex from http to https
The error “Failed to initialize site “ is keep popping up at our viewer after converting Geocortex from http to https!
The error disappears temporarily after running the post installation but it gets back after a while.
What do you think about this?
The error:
“Failed to initialize site. The error was: Exception has been thrown by the target of an invocation. The server committed a protocol violation. Section=ResponseStatusLine"
Our site link: https://geomolg.ps

Best,
Alaa
0
-
Seems to load for me! Did you get everything fixed? 0 -
Hi zack,
Yes, it loads now after we run the post installation but the issue here is that the error appears many times during the day and the post installation only fix it temporarily.
Please note that this happed after converting the site from http to https
We couldn’t figure what caused this behavior. Any ideas?
Regards,
Alaa0 -
I can't speak to what adding SSL did, but my guess is that this is more of a server resource issue than an Essentials one.
If you're using IIS, you might want to examine your app pools and see if recycling the one which runs Essentials or your Viewer resolves the problem. I've seen memory issues here cause the behavior that you describe but would be surprised if SSL introduced any such resource problems. I don't know what else the problem would be though, in the case of intermittent crashes, if not a resource one.0 -
Thank you Zack for the reply.
The issue didn't appear again. Most properly, it was an error in the steps of converting the site to https.(some links wern't converted to https).
Best,
Alaa0 -
Hi Alaa and Robison,
we got the issue today. It is back there!
what is strange is that running the “post installation” resolves the issue.
What could be the behind this very unexpected behavior?
I’m not sure if the Geocortex Analytics can send an alarm as this issue appears0 -
Hi Alaa
It does sound like you were seeing a CORS issue. I should say now though I'm still not seeing your Viewer load consistently. It seems like occasionally some services fail to load. I'd suggest cutting down the number of layers in this particular viewer.0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
6 Kommentare