Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
CentOS-WebPanel Bugs / BUG: Nginx Vhosts created with shared IP when set to other IPs
« on: July 07, 2020, 09:13:17 PM »
This is on an AWS server, created on the the latest Centos base AMI.
My webservers are setup as:
HTTP: Nginx (80) --> Varnish (82) --> Apache (8181)
HTTPS: Nginx (443) --> Varnish (82) --> Apache (8181)
We have added two elastic IPs and they both show up on the command line as private IPs:
172.31.44.10
172.31.36.240
In CWP Settings > Edit Settings, I have set the primary Elastic IP as the shared IP and the corresponding private IP as the Nat Local IP. I have also checked off the Activate NAT-ed network configuration:
The result is that everything seems to work correctly when using the shared Elastic IP.
This issue is when I go to make a new account link so:
If I select the shared IP or the corresponding private IP (172.31.44.10) everything works as expected. If I select the other IP address (172.31.36.240) all http connections to the new account are refused. After much debugging, I found the issue was that in the nginx conf file (/etc/nginx/conf.d/vhosts/DOMAIN.conf), the new vhosts are all being set to the shared IPs private address despite the fact that the account is set to use a different IP address. Manually editing this file to be the selected private IP address for the account and restarting nginx corrects the issue.
Is there something I am doing incorrectly here? Is there anything that can be done so that I don't have to manually edit the vhosts file for each new account created that isn't using the shared IP?
Thanks for any/all help you guys might be able to provide!
Cheers,
Ajar
My webservers are setup as:
HTTP: Nginx (80) --> Varnish (82) --> Apache (8181)
HTTPS: Nginx (443) --> Varnish (82) --> Apache (8181)
We have added two elastic IPs and they both show up on the command line as private IPs:
172.31.44.10
172.31.36.240
In CWP Settings > Edit Settings, I have set the primary Elastic IP as the shared IP and the corresponding private IP as the Nat Local IP. I have also checked off the Activate NAT-ed network configuration:
The result is that everything seems to work correctly when using the shared Elastic IP.
This issue is when I go to make a new account link so:
If I select the shared IP or the corresponding private IP (172.31.44.10) everything works as expected. If I select the other IP address (172.31.36.240) all http connections to the new account are refused. After much debugging, I found the issue was that in the nginx conf file (/etc/nginx/conf.d/vhosts/DOMAIN.conf), the new vhosts are all being set to the shared IPs private address despite the fact that the account is set to use a different IP address. Manually editing this file to be the selected private IP address for the account and restarting nginx corrects the issue.
Is there something I am doing incorrectly here? Is there anything that can be done so that I don't have to manually edit the vhosts file for each new account created that isn't using the shared IP?
Thanks for any/all help you guys might be able to provide!
Cheers,
Ajar
Pages: [1]
