Sitecore Serialization - Error connecting to /.well-known/openid-configuration: Bad Gateway

Hi Team,

Recently, I faced an issue where for the new project my Sitecore serialization started giving me following error.

Error: "Error connecting to https://sc10.dev.local/.well-known/openid-configuration: Bad Gateway"

My identity server when browsed above url was also not working and showing following.

Well, I tried seeing logs and different things, I also followed what is given on these links.

https://sitecore.stackexchange.com/questions/34744/open-id-configuration-issue-with-sitecore-cli

https://tekkishare.azurewebsites.net/pages/sitecore-clilogin-error-badgateway

https://www.stockpick.nl/english/sitecore-cli-login-error/

But I was still getting the same error.

Solution

If you see above screenshot of my identity server, in "Troubleshooting steps" it is mentioned that "Check the system event log for error messages."

It triggered me, I opened event log of windows, and I could see following error.

Now, i already update my .net run time version according to identity server's config file, which given on following path (also above blog link also mentioned the same step, which i performed but still it did not work)

C:\inetpub\wwwroot\sc10IdentityServer.dev.local/Sitecore.IdentityServer.Host.runtimeconfig.json

But it was showing me to download 3.1.0 which I already did, but somehow something was missing, so now what helped me was

in the event log itself, it provides link to missing part, you just click that link, and it downloads that version, for me the link was pointing to following.

After downloading the runtime, it worked like a charm for me & serialization is working and identity server error of 502 was also gone

Comments

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right? Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging 1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for Leprechaun and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1) In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!

Daivagna Nanavati

Search This Blog