I have created a GraphQL endpoint on the author instance, and it works fine there. I’ve also published the GraphQL endpoint and the content fragment to the AEM publish instance. But when I try to access the GraphQL endpoint on the publish instance, I see the following errors.
AEM Version - AEM 6.5.17
{
"errors": [
{
"errorType": "ServletError",
"message": "Internal Servlet Failure",
"details": "No suitable endpoint found."
}
]
}
I verified both Graphql and CF present on AEM publish instance. Also I enabled below two config as per https://statics.teams.cdn.office.net/evergreen-assets/safelinks/1/atp-safelinks.html
There is no error message on log file. Is there anything else I should check ?
Solved! Go to Solution.
Views
Replies
Total Likes
hello @Mario248
This usually means that the endpoint is either not there at all or it is not readable (Eg., protected by ACLs)
Is the GraphQL Endpoint enabled and published? are there any content permissions set?
Hi @Mario248,
Please refer: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/graphql-is-not-working-cor...
Hope that helps!
Views
Replies
Total Likes
Sorry, These links does not help .
Views
Replies
Total Likes
hello @Mario248
This usually means that the endpoint is either not there at all or it is not readable (Eg., protected by ACLs)
Is the GraphQL Endpoint enabled and published? are there any content permissions set?
@muskaanchandwani Thank you for your valuable input. Yes, Both GraphQL Endpoint and Content is published. I logged into pub servlet and confirmed it is there. But the permission was not to persistent query that is inside /conf location. I set the read the permission to "anonymous" user but still I get the same error. I tried to access the endpoint as admin and get the same error.
{"errors": [{"errorType": "ServletError","message": "Internal Servlet Failure","details": "No suitable endpoint found."}]}
I also restarted the aem pub server but no luck. Any bundle that needs to refreshed ?
Views
Replies
Total Likes
I was checking persistent query publish status but forgot to check Graphql endpoint. After publishing Graphql it started working. Thanks for your input.
Views
Replies
Total Likes
Views
Replies
Total Likes
Hi @Mario248,
Did the shared solution help you out? If yes, kindly consider marking the answer as ‘correct’.
If you’re still facing any challenges, please feel free to continue the conversation here. We’re happy to support further.
Yes, Both GraphQL Endpoint and Content is published. I logged into pub servlet and confirmed it is there.
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies