Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Not able to access AEM publisher with HTTPS enable using IP

Avatar

Level 2

Hi,

I followed the following article [0] to enable HTTPS on publish and its successfully done. Now, I am trying to access the publish server from other machine, I am able to access using its public IP without https [1], however I am not able to access https [2]. Below are the urls. Please suggest what am i doing wrong here?

[0] Article: SSL By Default

[1] Become A Member For Free | Cornerstones4Care®

[2] https://54.173.93.90:433/content/cornerstones4care/en/sign-up.html

I have configured https on 443, however same is accessible on local machine using localhost

Message was edited by: Pankaj Girotra

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

please, do not expose your AEM instances directly to the internet, without having secured them according to the security checklist; and the most important aspect being: add a dispatcher in front of it. And in most cases you can safely terminate the HTTPS connection there, and use unencrypted HTTP from dispatcher to AEM; but you can also choose to encrypt this connection.

But in any way, please add a dispatcher!

Regarding the connection: Maybe this connection is blocked somehow via a firewall?

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

please, do not expose your AEM instances directly to the internet, without having secured them according to the security checklist; and the most important aspect being: add a dispatcher in front of it. And in most cases you can safely terminate the HTTPS connection there, and use unencrypted HTTP from dispatcher to AEM; but you can also choose to encrypt this connection.

But in any way, please add a dispatcher!

Regarding the connection: Maybe this connection is blocked somehow via a firewall?

Avatar

Level 10

Most likely your listener IP is different than your public IP or otherwise its an internal network/firewall issue.

logon to that box, check the hosts file for that IP

As mentioned by Jörg​, secure it ASAP