On 05/28/2014 01:08 AM, Deepak wrote: > I am writing an in house application where my main web server is "apache " > web server hosting the main web portal which is being accessed by HTTPS. > > On one of the webpage I am establishing the connection to the socketio based > server using HTTPS again but on different port. Hostnames are same for main > URL and socketio's URL. > > If I use two different SSL certificates all goes fine. However if I try to > use the same certificate , application is unable to connect to socket io > server.
The two services will need to share not only the certificate but also
the secret key material that corresponds to the public key in the
certificate, right?
Is it possible that the socketio server doesn't have permission to read
the secret key that apache can read? Or that the socketio server is
pointing to a the wrong secret key (which would be a key/certificate
mismatch)?
Is the socketio server actually running after this change? does it have
the given port held open? are there error log messages you can inspect
and share here?
> I want to use the same certificate for both the URLs (same host , different
> ports ). Isn't it possible ?
What you're trying to do should be possible, but i don't think you've
given enough information to figure out what the specific problem is.
hth,
--dkg
signature.asc
Description: OpenPGP digital signature
