<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Cedric<br>
<br>
The only possible method is:<br>
<br>
Set up a site <a class="moz-txt-link-abbreviated" href="http://www.mydomain.com">www.mydomain.com</a><br>
with an alias of play.mydomain.com<br>
Set it to not redirect. <br>
Set SSL on that site. <br>
<pre wrap=""><small>
Add a .htaccess with
Options +FollowSymLinks
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^play\.</small><small><small>mydomain</small>\.com$ [NC]
RewriteRule ^ <a class="moz-txt-link-freetext" href="http://www">http://www</a>.</small><small><small><small>mydomain</small></small>.com/play%{REQUEST_URI} [L,P]
Ken Marcus
</small></pre>
<br>
<div class="moz-cite-prefix">On 6/5/2014 8:17 AM, OCEANET - Cédric
BASSAGET wrote:<br>
</div>
<blockquote cite="mid:539089EE.5040004@oceanet.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">It does not work, maybe because
Virtualhost is defined like "*:443" instead of "sitename:443".<br>
<br>
So when I ask for the "sitename2:443", I'm beeing redirected to
"sitename:443".<br>
<br>
I've tried to :<br>
1 - activate SSL on first website<br>
2 - change IP of second website<br>
3 - activate SSL on second website<br>
4 - change back the IP of the second website to the original one
(same that on the first website)<br>
-> Still get an error message : "The IP address cannot be
changed to 10.100.100.11. SSL is enabled for this site, but
there is another site with the specified IP address that also
has SSL enabled. Disabling SSL for either site will correct this
problem."<br>
<br>
<br>
Any other idea ?<br>
Thanks for your help.<br>
Regards,<br>
Cédric<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<br>
<br>
<pre class="moz-signature" cols="72">OCEANET
---------------------------------------------------------------
[AGENCE DU MANS]
7, rue des Frênes
ZAC de la Pointe
72190 SARGE LES LE MANS
[t] +33 (0)2.43.50.26.50
[f] +33 (0)2.43.72.21.14
[AGENCE D'ANGERS]
5, rue Fleming
Angers Technopole
49066 ANGERS
[t] +33 (0)2.41.19.28.65
[f] +33 (0)2.52.19.22.00
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.oceanet.com">http://www.oceanet.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.oceanet-telecom.com">http://www.oceanet-telecom.com</a></pre>
On 26/05/2014 21:02, Gerald Waugh wrote:<br>
</div>
<blockquote cite="mid:53838FBA.70902@frontstreetnetworks.com"
type="cite">
<pre wrap="">On 05/26/2014 08:13 AM, OCEANET - Cédric BASSAGET wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello Michael,
I don't understand your reply.
Do I have to set another IP address on my server to use the same
wildcard certificate on two websites (on same domain) ?
You tell me in the second step of your mail that I have to add another
IP. I don't want / have to do that !
Regards,
Cédric
OCEANET
---------------------------------------------------------------
[AGENCE DU MANS]
7, rue des Frênes
ZAC de la Pointe
72190 SARGE LES LE MANS
[t] +33 (0)2.43.50.26.50
[f] +33 (0)2.43.72.21.14
[AGENCE D'ANGERS]
5, rue Fleming
Angers Technopole
49066 ANGERS
[t] +33 (0)2.41.19.28.65
[f] +33 (0)2.52.19.22.00
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.oceanet.com">http://www.oceanet.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.oceanet-telecom.com">http://www.oceanet-telecom.com</a>
On 23/05/2014 20:58, Michael Stauber wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Cédric,
</pre>
<blockquote type="cite">
<pre wrap="">Where are the apache instructions about SSL (SSLCertificateFile,
SSLCertificateKeyFile, ...) located ? I can't find them in vhost config
files...
</pre>
</blockquote>
<pre wrap="">Sorry, I'm late to the party. What speaks against doing it this way:
1.) Have the primary site on one IP. Install the wildcard SSL
certificate there via the GUI.
2.) Create the other site via the GUI, give it a different IP and
install the wildcard SSL certificate there, too. Don't create a
subdomain for it, but a regular site.
Certificates are domain specific. Not IP specific.
</pre>
</blockquote>
</blockquote>
<pre wrap="">I believe you use a different IP while installing the certificate,
and the ip doesn't have to be working just used to get the certificate
to install.
Then change the IP to the one you desire to use
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Blueonyx mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Blueonyx@mail.blueonyx.it">Blueonyx@mail.blueonyx.it</a>
<a class="moz-txt-link-freetext" href="http://mail.blueonyx.it/mailman/listinfo/blueonyx">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a>
</pre>
</blockquote>
<br>
</body>
</html>