Ok I telnetted to the web server and I'm seeing that 8822 is the only web port open I thought 80 was still open too and that's why https was working internally. I now understand it was forwading like you explained. But if I already have one webserver running on port 80 I have to redirect traffic too port 8822 for the 2nd webserver. I can't have both servers on port 80. I only have one public IP. So I can't use https://domain/mail that would be asking my first web server where do I go. So then I redirect it to https://IP:8822/mail that's when it fails. So how can I get both web servers running and have the pointer work to the 2nd webserver for https. Sorry I now GRASP what everyone is saying I just can't explain things very well.

Thanks

I think something is getting lost in translation here. By default, http is on port 80 and https is on port 443. You are correct that you can't run both on port 80, and that is why there are two different port assignments for http and https. There is no port forwarding involved. Using https://domain/mail is still using port 443 which is ok. It doesn't involve port 80 at all.

You realize that you have two services and one IP address. What I don't think you realize is that http automatically goes to port 80 and https automatically goes to port 443 unless you reconfigure them. Unless you have a special need to use non-default ports, there is no need to change SSL from port 443.

Apparently you've tried to reconfigure https to listen on port 8822 instead of the default. It appears instead that you have move plain http.

So the question is how do I get the 2nd webserver to run with a SSL if I already have one web server running on port 80 already? This is something I wil have to think about I'm running IIS on port 80 and I want to use apache for my mail / web server for mail. Just trying to figure it out Yes I know I shouldn't be running IIS. Maybe one day I will migrate away from it!!

You already have a second server running. The second runs on port 443. SSL is not an application. It's an addition protocol handled by the webserver, in this particular case Apache.

I didn't pick earlier that you have an IIS server also involved. I guess that's where the two servers and one IP address comes in. I was under the impression that you had two services on the same system.

In any case, if you are going to use IIS for http only and Apache for https, then there is no need to use non-default ports. If you want to run two http servers or two https server, then you'll need to switch one to a non-default port. I'm assuming that you're doing port forwarding through some sort of DSL/cable gateway.

Yes I have a port forwarding setup. I scanned my IP and the proper ports are up. Would leaving apache at port 80 and opening port 80 to both web servers work just to have ssl work on the 2nd webserver? I know I can't have both servers on 80 so how do I get around this problem? I would rather have apache on a different port if at all possible.

I glanced at your site! I like it simple and sharp. I believe you hit the nail on the head for open source for small companies!! I deal with smaller companies day in and out and they really can't afford MS products but certain applications push them into having to run MS OS's anyways! Bill owns most companies. But I'm beginning to see a change and I love it! Keep up the good work!

If you want to have two http servers then you'll need to move one of them to another port and forward that port also. If you are only going to access the Apache server from the outside via https then don't worry about forwarding port 80 to it. It's not needed for SSL.

So all I need to do is https://IP:443 and it should work? I will test it tomorrow and hopefully my very dumb post will be done with

Thanks Again,

BiG

Since my domain server is my 1st server I just made a virtual directory that points to the 2nd web server to https://ip.com/mail and it works fine. I'M AN IDIOT AND FOR SOME REASON I COULD NOT GRAPS WHAT WE WERE TALKING ABOUT. Yes I'm a newbie and the only port I needed open the whole time was 443 right to the apache box. Thanks for your PATIENCE on this!

BiG

I kind of skimmed through this post. I don't think I saw this addressed so if it has been I appologize.

Here is what the problem is that I see. We are having nothing more than a typing problem.

when you type http://www.whatever.com it looks for the post apache is running on, port 80. When you type http://www.whatever.com:8822 it then sends the request to port 8822. If you type https://www.whatever.com it looks to the port that ssl is running on, port 443. If you type hhtps://www.whatever.com:8822 then it tries to establish an ssl connection on port 8822 which it can't because ssl is not listening on that port, apache is.

type http to get the port apache is on
type http... : port# to force a specific port
type https to get the ssl port
type https ... : port# to force an ssl port


Does that help?

Yes I finally figured this after testing All I had to do was open port 443 to the mail server and then I just typed https:\\domain\mail. I was totally over completing the question!!