Getting resource not found error for Experience fragments | Community
Skip to main content
A
Abbirami
Level 2
September 12, 2024
Solved

Getting resource not found error for Experience fragments

  • September 12, 2024
  • 2 replies
  • 777 views

While accessing the Experience fragments we are getting 404 Resource at '/content/pagenotfound.html' not found: No resource found . Able to edit the same yesterday.

As far as my knowledge no changes were made.

 

Please advise what might be causing the issue.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

Hi @abbirami 
Are you getting this error on AEM Author, Publish or when accessing via dispatcher?

If its dispatcher then check filter rules.

2 replies

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
September 12, 2024

Hi @abbirami 
Are you getting this error on AEM Author, Publish or when accessing via dispatcher?

If its dispatcher then check filter rules.

Arun Patidar
    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    September 13, 2024

    @abbirami Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

    Kautuk Sahni
    RiteshY18
    Community Advisor
    RiteshY18Community Advisor
    Community Advisor
    September 13, 2024

    adding to the solution suggested by @arunpatidar 

    - check log and error file 

    - Clean dispatcher cache in case of dispatcher 

    - check permission / env specific to author/publish?

    - if on the publisher, check the replication 

      Terms & ConditionsAccessibility statement

      Loading footer...