Aem sites locked for anonymous users

[#1]

Hi guys!

Recently under unknown modification the publisher instance can't be accessed by anonymous users. Only logged user can access the publisher instance.

How do I change that?

I'm using AEM 6.2 and I've already check user admin for anonymous user permissions.

Any suggestions?

Thanks!

-------------------------

I also get this when I start the instance:

20.07.2018 10:44:38.150 *ERROR* [qtp431714949-100] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Abort login due to apparent misconfiguration.

20.07.2018 10:44:38.150 *ERROR* [qtp431714949-100] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Possible reasons: login page not existing or not accessible

20.07.2018 10:44:38.244 *INFO* [qtp431714949-101] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

20.07.2018 10:44:38.337 *INFO* [qtp431714949-102] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

20.07.2018 10:44:38.337 *ERROR* [qtp431714949-102] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Abort login due to apparent misconfiguration.

20.07.2018 10:44:38.337 *ERROR* [qtp431714949-102] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Possible reasons: login page not existing or not accessible

[#2]

Can you check this particular config once, It should be checked

[#3]

Yep, that's checked.

[#4]

Sounds like that instance is configured as an author instance. Check to make sure its properly configured for Pub - Run Modes

[#5]

Hmm, I don't think so because If it would be an author instance it should redirect me tot the AEM login page.

But when I access any page I get this 403 error.

[#6]

302 status code would suggest an issue on the apache level or resource mapping configuration. Can you bypass the webserver and directly try hitting the author/publish instance

[#7]

Hmm, I don't think I understand.

My experience is not so vast so I don't know what are you talking about by "bypass the webserver and directly try hitting the author/publish instance.

Can you please detail?
Thanks

[#8]

Try hitting the instance with direct host port (http://HOST:PORT/<CONTENT_PATH>.html) and see if anonymous users can access the page or not

[#9]

No, I can't.  I get that 302 status code.

I'm only allowed to access it after i get login in into crx/de. when i'm logged as an administrator. And I don't understand which may be the cause.

[#10]

Has this been happening since the Server was installed or was fine then started happening.