Which ethernet interface did you use for the IP address, private or public? Also, I would suggest using a shorter hostname, like "idp-test.civi.com" and then use a hostname to map it to the internet facing ip address. Also, if you don't need Asimba or CAS, you might not want to install it... just takes up memory.

Hello Michael, Thanks! I'll try it out and give you guys an update. I used the Private IP from AWS (stated from your docs). "Also, I would suggest using a shorter hostname, like "idp-test.civi.com" and then use a hostname to map it to the internet facing ip address." Do I need to configure anything from the AWS Instance? or do I just need to set a hostname and just map it to the hostname of the chroot container? Thanks in advance.

I would set the hostname in your the /etc/hosts file and make sure you update your local workstation hosts file too (i.e. in your laptop).

I see. Thanks! I'll give you an update once I'm done.

Hi, Karl. How is it going? Were you able to resolve your issue, do you still need any help? Regarding issue you described first. Did you disable SElinux on this host? How many active network interfaces it has? Please provide output of `# ifconfig -a` or/and `# ip addr`, then `# cat /etc/hosts` and `# cat /etc/resolv.conf` (all commands must be run inside container). Are you sure port 443 is accessible from outside and/or correctly mapped to this AWS instance? Like, may be it runs in some internal network behind some kind of NAT? Or may be iptables/firewalld on that very host (where your Gluu runs) blocks access to port 443? You can make sure it's not the case in many ways, like, you could start monitoring Apache's access logs **inside of the container**, and then try to access Gluu's web UI. At least you must see some HTTP(S) activities in logs during your attempt. If connectivity is not an issue, let's proceed to checking the setup itself. Please provide output of `# netstat -nlpt` and `# ps aux | grep -i java` **from inside container**. Then stop the Tomcat service `# service tomcat stop`, rename wrapper log `# mv /opt/tomcat/logs/wrapper.log /opt/tomcat/logs/wrapper.log.bak`, start the service `# service tomcat start`, tail the log `# tail -F /opt/tomcat/logs/wrapper.log` (will be recreated shortly). You may see some Java error traces right away. If it will start successfully, then continue tail-ing the log and try to access web UI, see if any errors will pop-out. You can also check `oxauth.log` and `oxtrust.log` too. Please provide us `wrapper.log` and any other logs containing any clues of what is happening.

Hi Aliaksandr, Thanks for the follow up. Everything is okay now. Thanks guys!