New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup should prepare CE to work with dynamic IP correctly #425

Closed
yurem opened this Issue Apr 25, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@yurem
Contributor

yurem commented Apr 25, 2018

Currently customers who install Gluu under AWS has problems with accessing it after install.
The one of the problem that setup put /etc/host with next line:

%(ip)s %(hostname)s

@yurem yurem added this to the 3.1.4 milestone Apr 25, 2018

@mzico

This comment has been minimized.

Contributor

mzico commented May 22, 2018

@yurem : For AWS, I found it best not to 'modify' any IP at the time of installation. setup.py take one IP_address which is best suited ( mostly internal IP of that AWS instance ) automatically.
And as far as I can tell, internal_ip of AWS instance never change.

To 'access' the login page from internet, if that hostname+ip is not DNS registered.. they need to map that external_ip_of_aws_instance [hostname_of_gluu_server] in their own computer's /etc/hosts file.

@ganesh-at-wiw

This comment has been minimized.

Contributor

ganesh-at-wiw commented May 23, 2018

Hi @yurem ,

Here is the analogy I used similar to AWS:

AWS provides public name like this: ec2-56-38-174-34.us-west-2.compute.amazonaws.com(I'm using a fake name!). So, I used public name of our gluu server instance as: cf.gluu.org(This one is real).

Let's say, we want to access gluu-server at https://de.gluu.org. For this, I installed the gluu-server at our VM with hostname as: de.gluu.org and at internal IP.

Next, I did set de.gluu.org as CNAME to cf.gluu.org(This too is real). Which is same like AWS would expect some hostname like de.gluu.org to create CNAME to ec2-56-38-174-34.us-west-2.compute.amazonaws.com.

Finally, you access: https://de.gluu.org which is CNAME of cf.gluu.org and it's accessible.

Is this what we want? If yes, then we do not need to do anything.

@ganesh-at-wiw

This comment has been minimized.

Contributor

ganesh-at-wiw commented May 23, 2018

So, all in all, those customers should install gluu-server with desired domain name as hostname.
Then set that hostname as CNAME to the AWS provided public domain name.

@ganesh-at-wiw

This comment has been minimized.

Contributor

ganesh-at-wiw commented Jun 26, 2018

@yurem any comments?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment