Skip to main content

XM Cloud - Publish error "Invalid Authority connection string. Required parameter 'url' is missing"

Hi Team,

If you are exploring and working on XM Cloud and have set up XM Cloud instance on your local environment, You might run into following issue on publish

 

Because Sitecore XM Cloud instance works on Experience edge and there is no content delivery server which reads from WEB DB, It always publishes on experience edge

Because we are habitual (at-least i am) to publish the API KEY after creation, Because it is mentioned in the steps below url (point-6)

https://doc.sitecore.com/xp/en/developers/hd/211/sitecore-headless-development/create-a-sitecore-api-key.html


and that is why in my other non cloud XM instance (stand alone on-prem), i am habitual to create an API and publish it, and i was doing the same in my XM Cloud Local instance too.

But with local XM Cloud docker instance, It does not work that way, Because local does not work with experience edge, and when you see publishing wizard it only has one publishing target i.e "Experience edge" and that why above error comes


so when you publish anything, It gives below exception 

#Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Sitecore.ExperienceEdge.Connector.ContentHubDelivery.Exceptions.EdgeApiException: [ExperienceEdge Publishing]: An error has occurred while publishing JobStart event 93cf8ce8-8c97-4397-9e13-5fe028ada15b for publishing job '638156301229470000'. Please see inner exception for more details. ---> Sitecore.Exceptions.ConfigurationException: Invalid Authority connection string. Required parameter 'url' is missing.

Solution

1) You actually have to do nothing, because your local rendering hosts in docker for XM Cloud, runs against CM instance, so everything should work OOTB and you do not need to publish anything as there is no content delivery role concept which reads from WEB db.

2) If you still want to publish and want to play around with any use cases etc. you can create a new publishing target called "web" and while publishing select that "web" as the target and not experience edge (not sure if this support will be there in future or not as there is no content delivery role)

everything should work !!!

I saw people asking similar questions and hence thought to pen it down


Labels:

Comments

Post a Comment

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...
3 comments
Read more

Sitecore Stream - Platform DxP Evolution

Hi Team, I am absolutely Sitecore Stream enthusiast, and if you also keep following what is new in it and explore it features, This blog post is for you Since it was announced in symposium 2024 and probably the first platform DxP version package was released in FEB-2025 and we are now in Sep end and there have been significant roll outs and we are into 6th release of the platform DxP package. The purpose of this blog post is to summarize all improvements which came along with different releases for all of you and community, If you have not explored all of the packages. NOTE : Remember Stream is "AI capabilities throughout the composable stack, be it Content Hub, XMC, CDP, Personalized but this blog post is only for platform DxP package for on-prem XP/XM. If you see the image above, i have tried to show the package rollout on the timeline as an when they were released and watchout for next package rollout, For other useful features :)  Important improvements 1) Less configurations ...
Post a Comment
Read more

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!!!
1 comment
Read more