I have a web application deployed as a container in Linux server in production. A certificate is from GeoTrust. It is a simple Python server using pfx. The web application is limited to internal only. The Linux server has a physical IP address: 172.20.100.11 and a IP virtual: 172.16.100.162. The domain is linked to the virtual IP address.Also:
- The web application can be reached through HTTP, so there is no network connection problem
- The Linux server has correct certificate store.
- The same web application works no problem in QA environment with the same pfx file for HTTPS, so the certificate should have no problem.The differences between the QA and production:
- The QA has only one physical IP, while the production has physical IP and virtual IP
- The production has two domains for the same virtual IP address. When PING with mydomain, the response shows responding from the other domain, vise vesa.
In the production, I can't make the HTTPS work, when runcurl -v https://mydomainIt returns following error:** Rebuilt URL to: https://mydomain
- Trying 172.16.100.162...
- TCP_NODELAY set
- connect to 172.16.100.162 port 443 failed: Connection timed out
- Failed to connect to mydomain port 443: Connection timed out
- Closing connection 0curl: (7) Failed to connect to mydomain port 443: Connection timed out
I am thinking either the double IP addresses for the same server or the double domains for the virtual IP could causing the problem for reaching HTTPS.Can someone provide some help? Since I have no access to the production, it is difficult to do trouble shooting. But is it OK to support two domains on the same virtual IP? What is the correct way to make sure the setup to support physical IP and virtual IP for the same server?
Any help is greatly appreciated.