Sorry for bumping my own post, but I'm really in need of help here. I'm at a
loss. Maybe it's because folks are on holiday given the time of year, but if
anyone thinks they can help, I'd very much appreciate it. :o)

Thanks,
Chris

On Dec 27, 2007 3:30 PM, Chris Jordan <chris.s.jordan@gmail.com> wrote:
[color=blue]
> Hi folks,
>
> I'm a complete newbie to this stuff, and I need a little more help.
>
> I'm running apache 2.2.4 on a Fadora Core 6 (2.6.20-1.292.fc6). My first
> problem after I installed the certificate is that we apparently had an old
> self-signed certificate installed. So, once I figured out that the SSL
> directives were in the conf.d/ssl.conf and not in conf/httpd.conf, I was
> able to put my certificate information in that file and now our server is
> using our real certificate and not the self-signed one.
>
> Our server runs multiple domains using virtual hosting, and I've read
> through the archives enough to find out that I can't do named virtual host
> with SSL. That's fine. My problem now is that when I browse to:
> [url]https://mysecuredomain.com[/url], I'm getting sent to another one of our other
> domains (wrongdomain.com -- for the sake of discussion) except that the
> URL in the address bar still says: [url]https://mysecuredomain.com[/url].
>
> I'm confused. I've searched through the archives, but can't seem to find
> out how this is happening.
>
> Here's another strange bit. We've got an old version and a newer version
> of " wrongdomain.com" and when I browse to [url]http://wrongdomain.com[/url] I get
> the new version. When I browse to [url]https://wrongdomain.com[/url] I get the *old*
> version of the site -- just as I do when I browse to
> [url]https://mysecuredomain.com[/url]...
>
> I hope I'm explaining this well enough. I really need help on how to get
> things working properly.
>
> The other thing that I'm curious about is whether we'll be able to secure
> any of our other domains hosted from this box in the future if we need to.
> From the reading I've done I'm thinking that's going to be a 'No', but what
> if we use the same certificate for all sites? That may be a dumb question,
> but again, I'm a genuine newbie here.
>
> My main concern is about the first part of this post... the side question
> about multiple domains is less important to me, but I'd still like to know.
> I sure hope someone can help me.
>
> Thanks heaps,
> Chris
>
>
> --
> [url]http://cjordan.us[/url][/color]

Sorry for bumping my own post, but I&#39;m really in need of help here. I&#39;m at a loss. Maybe it&#39;s because folks are on holiday given the time of year, but if anyone thinks they can help, I&#39;d very much appreciate it. :o)
<br><br>Thanks,<br>Chris<br><br><div class="gmail_quote">On Dec 27, 2007 3:30 PM, Chris Jordan &lt;<a href="mailto:chris.s.jordan@gmail.com">chris.s.jordan@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi folks,<br><br>I&#39;m a complete newbie to this stuff, and I need a little more help.<br><br>I&#39;m running apache 2.2.4 on a Fadora Core 6 (2.6.20-1.292.fc6). My first problem after I installed the certificate is that we apparently had an old self-signed certificate installed. So, once I figured out that the SSL directives were in the
conf.d/ssl.conf and not in conf/httpd.conf, I was able to put my certificate information in that file and now our server is using our real certificate and not the self-signed one.<br><br>Our server runs multiple domains using virtual hosting, and I&#39;ve read through the archives enough to find out that I can&#39;t do named virtual host with SSL. That&#39;s fine. My problem now is that when I browse to:
<a href="https://mysecuredomain.com" target="_blank">https://mysecuredomain.com</a>, I&#39;m getting sent to another one of our other domains&nbsp; (<a href="http://wrongdomain.com" target="_blank">wrongdomain.com</a> -- for the sake of discussion) except that the URL in the address bar still says:
<a href="https://mysecuredomain.com" target="_blank">https://mysecuredomain.com</a>.<br><br>I&#39;m confused. I&#39;ve searched through the archives, but can&#39;t seem to find out how this is happening.<br><br>Here&#39;s another strange bit. We&#39;ve got an old version and a newer version of &quot;
<a href="http://wrongdomain.com" target="_blank">wrongdomain.com</a>&quot; and when I&nbsp; browse to <a href="http://wrongdomain.com" target="_blank">http://wrongdomain.com</a> I get the new version. When I browse to <a href="https://wrongdomain.com" target="_blank">
[url]https://wrongdomain.com[/url]
</a> I get the *old* version of the site -- just as I do when I browse to <a href="https://mysecuredomain.com." target="_blank">https://mysecuredomain.com.</a>..<br><br>I hope I&#39;m explaining this well enough. I really need help on how to get things working properly.
<br><br>The other thing that I&#39;m curious about is whether we&#39;ll be able to secure any of our other domains hosted from this box in the future if we need to. From the reading I&#39;ve done I&#39;m thinking that&#39;s going to be a &#39;No&#39;, but what if we use the same certificate for all sites? That may be a dumb question, but again, I&#39;m a genuine newbie here.
<br><br>My main concern is about the first part of this post... the side question about multiple domains is less important to me, but I&#39;d still like to know. I sure hope someone can help me.<br><br>Thanks heaps,<br>Chris
<br><font color="#888888">
<br>
<br>-- <br><a href="http://cjordan.us" target="_blank">http://cjordan.us</a>
</font></blockquote></div><br><br clear="all"><br>-- <br><a href="http://cjordan.us">http://cjordan.us</a>