Hi, me again.
OK, I got my 2 external IPs and 2 internal IPs
I also have 2 certs.
Now when I edit httpd.conf and chnage the _default_:443 to 192.168.1.2:443
and copy that secton and paste it and modify the IP, root path and cert path
I get this and apach will not start with ssl
[Thu Sep 14
In what format is your certificate file. Is it PEM? Something is
definitely wrong with it.
On 9/14/06, milktoast [EMAIL PROTECTED] wrote:
Hi, me again.
OK, I got my 2 external IPs and 2 internal IPs
I also have 2 certs.
Now when I edit httpd.conf and chnage the _default_:443 to
I have read up on using multiple SSL certs on one server but the thing that
no one addresses is how this works on a server behind a router that uses
NAT.
Example
Server 1 has two domains www.foo.com and www.bar.com
Both are functional using IP based virtual hosts using 192.168.1.50
The
If both server share one IP using NameVirtualHost feature then there
is no way to have different certificates for them.
On 9/12/06, milktoast [EMAIL PROTECTED] wrote:
I have read up on using multiple SSL certs on one server but the thing that
no one addresses is how this works on a server
How should this look?
Here the virtual part of my httpd.conf
VirtualHost _default_:443
DocumentRoot /home/htdocs/foo
ServerName www.foo.com
ServerAdmin [EMAIL PROTECTED]
ErrorLog /usr/local/apache/logs/error_log
TransferLog /usr/local/apache/logs/access_log
# Block TRACE/TRACK XSS vector
If it looks like this then it will work perfect for www.foo.com but
won't work for bar com. User will receive an error saying that bar.com
uses certificate for foo.com.
The rool is easy: one cert per one IP.
See http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html
On 9/12/06, milktoast [EMAIL
I am aware of this... thus my question how should it look to get two
certs on one server?
If it looks like this then it will work perfect for www.foo.com but
won't work for bar com. User will receive an error saying that bar.com
uses certificate for foo.com.
The rool is easy: one cert per
On 9/12/06, milktoast [EMAIL PROTECTED] wrote:
I am aware of this... thus my question how should it look to get two
certs on one server?
Look like we do not understand each other. Once more: THERE IS NO WAY
TO HAVE 2 CERTIFICATES ON ONE SERVER WITH ONE IP ADDRESS.
As I understand your
Right,
Can I get a second IP address on the router and pass that traffic to a
second IP on the server and get it to work?
Serge Dubrouski wrote:
On 9/12/06, milktoast [EMAIL PROTECTED] wrote:
I am aware of this... thus my question how should it look to get two
certs on one server?
That's possible. You have to have 2 VirtualHoosts in your httpd.conf
(or ssl.conf, or vhosts.conf whatever you prefer), one per each IP
(VirtualHost IP:443). Do not enable NameVirtualHosts for them. Place
SSLCertificateFile and SSLCertificateKeyFile directives inside your
VirtualHosts. Remove
Right on! Thanks. I was hoping not to have to do that ... but I guess I
will.
Thanks again.
Serge Dubrouski wrote:
That's possible. You have to have 2 VirtualHoosts in your httpd.conf
(or ssl.conf, or vhosts.conf whatever you prefer), one per each IP
(VirtualHost IP:443). Do not enable
Serge Dubrouski wrote:
If it looks like this then it will work perfect for www.foo.com but
won't work for bar com. User will receive an error saying that bar.com
uses certificate for foo.com.
The rool is easy: one cert per one IP.
That, or multiple names per certificate, ie multiple names
12 matches
Mail list logo
