Skip to main content

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

Popular posts from this blog

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...

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error One or more exceptions occurred while processing the subscribers to the 'item:creating' event Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following Solution: 'Name' should consist only of letters, digits, dashes or underscore Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it, Solution I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in "App_Config\Sitecore\Mar...

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...