Search results for query: *

Argh~! They were right. :( It uses the certificate of the first VirtualHost that was defined. I lose. :( I should've read sleipnir's post...stupid me. Stupid n00b I am~! Okay, so reading some more of the posts...I was just curious...what kind of router do you have? What kind of environment? Is...

Yes, only 1 NIC but multiple IP addresses. Multiple sites on one IP address as well. I posted up portions of it so that way you won't get overwhelmed and it'll protect me a little bit so you don't see all my info. :) NameVirtualHost 12.29.124.49:80 NameVirtualHost 12.29.124.49:443...

I could be wrong, but couldn't you just do two NameVirtualHost that listens on SSL? Create certificates for both of them and do it that way? At least...that's how I used to do it and didn't have a problem...but people here keep telling me I can't do that. o_O Something along the line of...

Ah ha! I figured out the problem! WooHoo~! The answer was: <IfDefine !NOSSL> I left out the "NO" in that part. So it never ran my "NameVirtualHost" line which then would never load what I wanted it to load!! So, in conclusion, the problem was between the keyboard and the chair. The server...

RhythmAce, Thanx for chipping in. I'm pretty sure there is a VirtualHost set up that is pointing to /var/opt/blah. The Novell stuff (like in my above post). So what you're suggesting is that probably somehow Apache2 can't find my specified VirtualHost for 12.29.124.46 and is using the...

sleipnir214, There probably is a NameVirtualHost directive not applied to 443...but...hum...how do I say this. The server is running Novell Open Enterprise Server 1.0 (which is technically SuSE Linux Enterprise Server 9.3 but configured with Novell stuff.) The server originally only had one IP...

I don't know how it all really works, however on another server, I've created a bunch of Named Virtual Hosts that used a single certificate without a problem. However, my problem is not based on the certificates or SSL. I got the virtual host listening on SSL and accessible via SSL. The problem...

I am trying to create a new virtual host, and everything seems to be fine, but for some reason, it's not loading my DocumentRoot. For example, my server has two IP address. ServerRoot (if there is even such a thing) points to /var/opt/blah. I create a virtual host that has a document root that...

Alright, so after dropping this project for awhile to clear my head, I finally fixed it. I went back into WebMin, went to the Network Address portion and round and removed an option that tells it to listen on that address and port. The line must've been in httpd.conf, but I was searching for the...

I found the answer to the problem and since I've never found any posts online about how to fix this problem, I'm posting this...hopefully to help out the next guy/gal. Reason for getting a bunch of "lost connection after CONNECT from xxxx" was not because of too much rules for scanning...

I'm running Postfix 2.2.9 on SLES 10. I have MAIA Mailguard setup on this server and everything was running great as of this morning. This morning, I decided to add in rules du jour and add some sender/recipient restrictions. Stupid me, I did all these updates at the same time. After completing...

You know...that's not a bad idea. I know that it wasn't working when I used webmin to create my vhost, but before I did that, there were two listed already. o_O Maybe that's what I need to do. I'll keep you posted. :p P.S. this is the older version of SuSE. 9.x. I like the 10.1 version and...

Man, this isn't cool. I rem'd out the Listen 443 lines. I've removed the vhost-ssl.conf files. And yet...somehow somewhere, it's stilling binding to 443...somewhere in my httpd, it's binding! AHHHH~!!!

I definitely found something weird going on. I commented out the Listen 443 from Listen.conf and left the vhost-ssl.conf intact. After doing that, I was able to load Apache2, and indeed one of my site is binding to https. But checking through vhost-ssl.conf, I did not find anything that bind to...

Here's the weird thing. In my vhosts.d folder, there's only one file it's including, which is vhost-ssl.conf. There's no other files. If I remark out the line that includes the vhost directory in httpd and add "Listen 443," I get the same exact error. I've done searches in netstat and there's...

I figure it was small because of all the includes in it...but who knows. I'll go compare them and see what I can port over. :)

Here's my httpd.conf. Thanx for all your help on this. # # /etc/apache2/httpd.conf # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs-2.0/> for detailed information...

I configured those three and yet I still get the same error. :(

I changed _default_:443 to <ip>:443 and then tried to loading Apache2 again and I got the same error message still. What else should I try?

Is there a way to let it bind to all address? Well...most of it. I would like those pages to load for localhost, the private, and public side of the address. I have two public address that needs port 443 but to load up different pages. I thought _default_ would be a catch all?