Hi Sheetal,
This sounds like a firewall is doing some kind of deep packet inspection which requires the traffic to be resigned with a new certificate. If this new certificate is not trusted by our connector, then it might throw an error like this.
I would like to see the output from the following command:
curl -v https://rally1.rallydev.com
You can download curl from the following site if you're on Windows: curl - Download
For Redhat and variants: sudo yum install curl
For Ubuntu and variants: sudo apt-get install curl
I'm particularly interested in the output in the Server certificate section. It should look like this:
* Server certificate:
* subject: businessCategory=Private Organization; jurisdictionC=US; jurisdictionST=Delaware; serialNumber=3413668; C=US; ST=Colorado; L=Boulder; O=Rally Software Development Corp; OU=CA Technologies; CN=rally1.rallydev.com
* start date: Jun 27 00:00:00 2017 GMT
* expire date: Jul 22 12:00:00 2019 GMT
* subjectAltName: host "rally1.rallydev.com" matched cert's "rally1.rallydev.com"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 Extended Validation Server CA
* SSL certificate verify ok.
If you see anything like "SSL certificate problem", or "self signed certificate" then that is an issue that will need to be addressed prior to being able to successfully use the connector.