Questions

SSL redirection

Tags:
+
0 Votes
Locked

SSL redirection

kiran.maan
Scenario:-
A.COM, B.COM, C.COM... A & B are registered with SSL. All sites are on single Linux server and host entries made in /etc directory.

Problem:-
C.COM works fine with http BUT, it redirects to A.COM when I type https://C.COM.

Can someone help me why is this happening ?
  • +
    1 Votes
    robo_dev

    The DNS resolution order in host (dot) conf needs to have hosts first

    Perhaps FQDN is mismatched between server and client?

    Does nslookup return expected result?

    +
    0 Votes
    Rob Kuhn

    Is there a redirect in the root of C.COM ?

    Is this happening internally and externally? In other words on the LAN side instead of on the otherside of the firewall? What I'm getting at is is there perhaps a proxy server in place?

    What webserver are you running on the Linux box? If it's Apache/Tomcat, recheck the config file too.

    +
    0 Votes
    kiran.maan

    All three sites are on single Linux box with Apache/Tomcat and happening on web.

    +
    0 Votes
    Rob Kuhn

    Recheck and verify the config file including the bindings.

    +
    0 Votes
    ahadenfeldt

    Assuming you're running all these sites on a single IP address, then +1 on checking your Apache config. It sounds like you're being redirected to the default host. The rules Apache follows can be confusing. Here is a link that may be of some help: http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI.

    +
    0 Votes
    chplatt

    DNS resolution should be fine if HTTP is working and not redirecting. I would check to see how IP and Ports are bound to the server. Sounds like the host A.COM is bound to all HTTPS protocols, port 443.

    Are you using multiple IPs or host name resolution to identify the destination site?

    +
    0 Votes
    kiran.maan

    This seems close to issue. Server host file is OK and entries are made proper.
    I am planning to do,
    1. Check domain registration details with GoDaddy
    2. check entries (C.COM in A.COM certificate registration) made while installing certificate

    I will update this post and activities with results...

    thanx

    +
    0 Votes
    EzeXpl01t

    If you figure it out post the solution here, I have had a similar issue, but I forgot what I did to fix it. I think @chplatt has it right though.

    +
    0 Votes
    jaysoni86

    Since its Linux server, I'm guessing you are running Apache and its because of Apache.

    Lets say there are 3 domains: a.com, b.com & c.com and ONLY b.com has SSL. So https://a.com, https://c.com and https://<IP address> (if its shared IP for all), will resolve to https://b.com [it will always show website with HTTPS]

    However, if you resolve http://<ip address>, it will show the alphabetically first website on that IP i.e. http://a.com in this case.

    +
    0 Votes
    kiran.maan

    I doubt for it.

  • +
    1 Votes
    robo_dev

    The DNS resolution order in host (dot) conf needs to have hosts first

    Perhaps FQDN is mismatched between server and client?

    Does nslookup return expected result?

    +
    0 Votes
    Rob Kuhn

    Is there a redirect in the root of C.COM ?

    Is this happening internally and externally? In other words on the LAN side instead of on the otherside of the firewall? What I'm getting at is is there perhaps a proxy server in place?

    What webserver are you running on the Linux box? If it's Apache/Tomcat, recheck the config file too.

    +
    0 Votes
    kiran.maan

    All three sites are on single Linux box with Apache/Tomcat and happening on web.

    +
    0 Votes
    Rob Kuhn

    Recheck and verify the config file including the bindings.

    +
    0 Votes
    ahadenfeldt

    Assuming you're running all these sites on a single IP address, then +1 on checking your Apache config. It sounds like you're being redirected to the default host. The rules Apache follows can be confusing. Here is a link that may be of some help: http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI.

    +
    0 Votes
    chplatt

    DNS resolution should be fine if HTTP is working and not redirecting. I would check to see how IP and Ports are bound to the server. Sounds like the host A.COM is bound to all HTTPS protocols, port 443.

    Are you using multiple IPs or host name resolution to identify the destination site?

    +
    0 Votes
    kiran.maan

    This seems close to issue. Server host file is OK and entries are made proper.
    I am planning to do,
    1. Check domain registration details with GoDaddy
    2. check entries (C.COM in A.COM certificate registration) made while installing certificate

    I will update this post and activities with results...

    thanx

    +
    0 Votes
    EzeXpl01t

    If you figure it out post the solution here, I have had a similar issue, but I forgot what I did to fix it. I think @chplatt has it right though.

    +
    0 Votes
    jaysoni86

    Since its Linux server, I'm guessing you are running Apache and its because of Apache.

    Lets say there are 3 domains: a.com, b.com & c.com and ONLY b.com has SSL. So https://a.com, https://c.com and https://<IP address> (if its shared IP for all), will resolve to https://b.com [it will always show website with HTTPS]

    However, if you resolve http://<ip address>, it will show the alphabetically first website on that IP i.e. http://a.com in this case.

    +
    0 Votes
    kiran.maan

    I doubt for it.