Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

Unable to access author instance through https

serdman
Level 1
Level 1

We just set up a load balancer in our test environment to test failing over to a standby Author instance. As part of the process, we copied our Author environment from an old server to a new one and redirected the load balancer to point to the new server. Even though we haven't made any changes to the configurations on the author or the load balancer, we are unable to access the author through https at https://authorservername:4502 or https://loadbalancername.com. Everything seems to work correctly when we access the author instance through http at http://authorservername:4500. We've done this same process of copying over the instance and updating the load balancer destination on our publisher instances and everything has worked out smoothly.

 

The error.log files have a repeating error message that reads:

*INFO* [qtp624383331-2189] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

 

When accessing the instance through https://authorservername:4502 we get-

ERR_INVALID_HTTP_RESPONSE in the browser and nothing showing up in the error.log file

1 Reply
vanegi
Employee
Employee

 

Please check OSGI service  Apache Felix Jetty Based Http Service. [Move entire author or publish instance to https] 
  • Go to Felix console system configurations http://localhost:4502/system/console/configMgr 
  • Search for Apache Felix Jetty Based Http Service.
  • Open Apache Felix Jetty Based Http Service configuration. Enter below details
vanegi_0-1594712986760.png

 

 

  • Click Save
  • Note:- If you get an ajax error on saving check error logs and make sure you are not getting error of port already in use. If port is not available try saving the configuration with some other port name.
Now your AEM instance can be opened over SSL.