cant acces server 2 with vestacp
Posted: Tue Feb 05, 2019 7:52 pm
Hi,
i read all the board and seen this issue in several topics, but it doesnt solve my problem, and topics are very old 2015 or 2017 and closed.
Also i am dealing with this for 30 days now and dont know what else to try.
There are several issues, but i realy need to solve this one:
system info: ubuntu 18.04, apache2 only.
- i have configured first virtual machine: hostsrv1.mydomain.com and everything goes well. I must say it was a straight forward and easy installation.
- i created another virtual machine: hostsrv2.mydomain.com and i cant get to it in the browser.
a. I get a message of "SUSPENDED This website has been suspended. Please contact the technical support department." when accessing "http: //hostsrv2.mydomain.com"
b. and i get redirected to "mydomain.com" when accesing "https: //hostsrv2.mydomain.com"
c. and when typing "8083 -> hostsrv2.mydomain.com:8083 " i get redirect to "hostsrv1.mydomain.com:8083" so i can only manage vestacp in console.
suposing hostsrv1 its on ip "1.1.1.1.":
- I created a DNS A record in "mydomain.com" pointing "hostsrv2" to "1.1.1.2"
- i created the IP in the "IP" section of vestacp
- i tried creating the web domain "hostsrv2.mydomain.com" in "hostsrv1"
Nothing works, cant get to see vestacp admin board on "hostsrv2" and i cant see any of the test websites in "hostsrv2".
VestaCP documentacion in "How to set up master-slave DNS cluster" its obsolete, its missing 2 needed parameters "master/slave" and "dns-cluster". It always throws a error without them. And "How to remove Nginx on a RHEL or CentOS" should be updated because it throws errors so its better to not install nginx from start to avoid headaches.
Say if more information is needed. Good job till now.
Edit:
Server its totaly independent computer in a private network divided in several virtualized OS. Its not hosted in any third party hosting provider. No limitations in any aspect apart of my lack of knowledge. Connection its full PassThrough no NAT, all ports opened and ping hostsrv2 goes well from LAN, but when from outside DNS does some strange thing and always connects to hostsrv1. Maybe i have it missconfigured, but i never changed anything besides setting TEMPLATE as "ns-child" in "mydomain.com"; or maybe its with Apache2, at some point of virtualhosts, but i checked every .config file and cant see any thing wrong.
I only changed in "/home/user/config/web/mydomain.com.apache2.ssl.conf" file, the first line "<virtualhost ip:443 ssl>" because without the ssl Mozilla Firefox will not connect to the web page using "https"; and made same change in vesta template file so it aplys it to every domain.
The thing is, as my logic says, should occur:
1. visitor ask for web page "hostsrv2.mydomain.com"
2. domain registrar of "mydomain.com" points to the ip "1.1.1.1"
3. in IP "1.1.1.1" answers "hostsrv1.mydomain.com"
4. "hostsrv1" should forward the request of "hostsrv2"
5. so apache2 in "hostsrv1" checks for virtualhost and finds 1 pointing to "1.1.1.2"
6. apache2 its not forwarding the request to "hostsrv2" either because of a apache2 missconfiguration or bind9 DNS not pointing to the new ip "1.1.1.2"
I am not able to find whats going wrong in that step. I only see apache2 serving 3 diferent pages depending on the type of request (http/https) and the port (80/8083)
i read all the board and seen this issue in several topics, but it doesnt solve my problem, and topics are very old 2015 or 2017 and closed.
Also i am dealing with this for 30 days now and dont know what else to try.
There are several issues, but i realy need to solve this one:
system info: ubuntu 18.04, apache2 only.
- i have configured first virtual machine: hostsrv1.mydomain.com and everything goes well. I must say it was a straight forward and easy installation.
- i created another virtual machine: hostsrv2.mydomain.com and i cant get to it in the browser.
a. I get a message of "SUSPENDED This website has been suspended. Please contact the technical support department." when accessing "http: //hostsrv2.mydomain.com"
b. and i get redirected to "mydomain.com" when accesing "https: //hostsrv2.mydomain.com"
c. and when typing "8083 -> hostsrv2.mydomain.com:8083 " i get redirect to "hostsrv1.mydomain.com:8083" so i can only manage vestacp in console.
suposing hostsrv1 its on ip "1.1.1.1.":
- I created a DNS A record in "mydomain.com" pointing "hostsrv2" to "1.1.1.2"
- i created the IP in the "IP" section of vestacp
- i tried creating the web domain "hostsrv2.mydomain.com" in "hostsrv1"
Nothing works, cant get to see vestacp admin board on "hostsrv2" and i cant see any of the test websites in "hostsrv2".
VestaCP documentacion in "How to set up master-slave DNS cluster" its obsolete, its missing 2 needed parameters "master/slave" and "dns-cluster". It always throws a error without them. And "How to remove Nginx on a RHEL or CentOS" should be updated because it throws errors so its better to not install nginx from start to avoid headaches.
Say if more information is needed. Good job till now.
Edit:
Server its totaly independent computer in a private network divided in several virtualized OS. Its not hosted in any third party hosting provider. No limitations in any aspect apart of my lack of knowledge. Connection its full PassThrough no NAT, all ports opened and ping hostsrv2 goes well from LAN, but when from outside DNS does some strange thing and always connects to hostsrv1. Maybe i have it missconfigured, but i never changed anything besides setting TEMPLATE as "ns-child" in "mydomain.com"; or maybe its with Apache2, at some point of virtualhosts, but i checked every .config file and cant see any thing wrong.
I only changed in "/home/user/config/web/mydomain.com.apache2.ssl.conf" file, the first line "<virtualhost ip:443 ssl>" because without the ssl Mozilla Firefox will not connect to the web page using "https"; and made same change in vesta template file so it aplys it to every domain.
The thing is, as my logic says, should occur:
1. visitor ask for web page "hostsrv2.mydomain.com"
2. domain registrar of "mydomain.com" points to the ip "1.1.1.1"
3. in IP "1.1.1.1" answers "hostsrv1.mydomain.com"
4. "hostsrv1" should forward the request of "hostsrv2"
5. so apache2 in "hostsrv1" checks for virtualhost and finds 1 pointing to "1.1.1.2"
6. apache2 its not forwarding the request to "hostsrv2" either because of a apache2 missconfiguration or bind9 DNS not pointing to the new ip "1.1.1.2"
I am not able to find whats going wrong in that step. I only see apache2 serving 3 diferent pages depending on the type of request (http/https) and the port (80/8083)