Hi everyone,
We are trying to access this below POST request for the Acrolinx on the direct author on the production, but we see
Internal error (no exception to report)
whereas when we access the same request on the staging environment it works fine.
Production - http://<production-domain>/apps/acrolinx/proxy/api/v1/auth/sign-ins
Stage - http://<stage-domain>/apps/acrolinx/proxy/api/v1/auth/sign-ins
Is there any configuration/permission or something else we can check which might deal with the blocking of the request?
解決済! 解決策の投稿を見る。
トピックはコミュニティのコンテンツの分類に役立ち、関連コンテンツを発見する可能性を広げます。
表示
返信
いいね!の合計
The issue is resolved now. This was due to an old archived issue of Acrolinx where it creates an empty folder path in CRX-DE
/apps/acrolinx/proxy/api/v1/auth/sign-ins
which needs to be deleted to restore the functionality.
Thank you all of you for helping and providing your valuable suggestions !!
@somen-sarkar @sarav_prakash @PGURUKRISHNA @tushaar_srivastava @Jineet_Vora @Anudeep_Garnepudi Curious to hear your perspectives on this question. Do you all mind sharing your thoughts?
表示
返信
いいね!の合計
Can you please add more context?
The issue is resolved now. This was due to an old archived issue of Acrolinx where it creates an empty folder path in CRX-DE
/apps/acrolinx/proxy/api/v1/auth/sign-ins
which needs to be deleted to restore the functionality.
Thank you all of you for helping and providing your valuable suggestions !!
@Jangra98 , can you please add more details to it, because yes we need Compare Configuration {Could be : OSGi, Dispatcher, or maybe firewall rules}
Also, we may need to check
User Permissions: Ensure that the user or service account making the request has the necessary permissions in the production environment.
Access Control Lists (ACLs): Verify that the ACLs in the production n environment are not restricting access to the Acrolinx endpoint.
if you could provide me with more details on your usecases.