I've installed Froxlor on an Ubuntu 12.04 EC2 instance at Amazon and I'm having difficulty maintaining connectivity to the domains AND the default froxlor login due to Amazon's Elastic IP and internal IP differences.
Effectively, apache's default site answers on <virtualhost *:80> and if you configure froxlor with the elastic (external) IP address, that IP gets injected into the domain virtualhosts like this: <virtualhost [elastic ip]:80>. Accessing the site domains like this delivers the user to the default Ubuntu home page in /var/www that says "It Works!"
If you bind froxlor to the internal 10.x.x.x IP address within Amazon's DMZ, the domain's get injected with virtualhost like this: <vitualhost 10.x.x.x:80> and the froxlor backend becomes unreachable at http:[elastic ip]/froxlor and at http://virtualhost.dom/froxlor. Furthermore, it appears that the NAT or the DNS connection from the outside to the inside causes the site to load slowly and unresponsively.
What's the correct way to circumvent this? a) bind the froxlor IP and Port to the external IP and the sites to the internal IP? What would the options in "Ips and ports" look like for this configuration? alias the domain/froxlor to /var/www/froxlor in the domain configuration somewhere? How would this be accomplished? c) bind froxlor to a separate port? or another elastic IP?
Question
steve_adams
I've installed Froxlor on an Ubuntu 12.04 EC2 instance at Amazon and I'm having difficulty maintaining connectivity to the domains AND the default froxlor login due to Amazon's Elastic IP and internal IP differences.
Effectively, apache's default site answers on <virtualhost *:80> and if you configure froxlor with the elastic (external) IP address, that IP gets injected into the domain virtualhosts like this: <virtualhost [elastic ip]:80>. Accessing the site domains like this delivers the user to the default Ubuntu home page in /var/www that says "It Works!"
If you bind froxlor to the internal 10.x.x.x IP address within Amazon's DMZ, the domain's get injected with virtualhost like this: <vitualhost 10.x.x.x:80> and the froxlor backend becomes unreachable at http:[elastic ip]/froxlor and at http://virtualhost.dom/froxlor. Furthermore, it appears that the NAT or the DNS connection from the outside to the inside causes the site to load slowly and unresponsively.
What's the correct way to circumvent this?
a) bind the froxlor IP and Port to the external IP and the sites to the internal IP? What would the options in "Ips and ports" look like for this configuration?
alias the domain/froxlor to /var/www/froxlor in the domain configuration somewhere? How would this be accomplished?
c) bind froxlor to a separate port? or another elastic IP?
other suggestions?
Link to comment
Share on other sites
12 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.