XMail-WAI 4.0 SSL

I have WAI 4.0 working. When the login screen comes up is states that SSL is available and provides a link. When I click on it I get the "Page cannot be found" error. I have port 8080 set up on IIS for the website.

Anything else I'm missing? ... Besides brain?

Firewall blocking the port 8080 ?

All on local network right now, so firewall isn't involved.

I am strictly using IP addresses. Could that be the problem?

Did you set-up the website for SSL? I assume you're running the non-SSL version on port 8080. I'm not sure why WAI assumes you've also got an SSL-version, but if you didn't manually set one up, I assume you don't have one.

Where does the link point to? To https://10.0.0.1 (where 10.0.0.1 obviously would be the IP-address you used in http://10.0.0.1:8080). That would mean the browser would try to make an SSL connection to port 443 on the same machine. But you'll have to set that up in your webserver for it to work.

Well maybe that's where my problem is...

It's W2K3 Web server edition. Here's how I have it setup:

IP: 10.76.1.141
TCP Port: 80
SSL Port: 443

http works fine. https displays Page cannot be displayed. I changed SSL Port to 8080. Still doesn't work.

I added another IP:
IP: 10.76.1.143
TCP Port: 8080
SSL Port: 443

Still doesn't work. I've got to be missing something simple.

Could you post the exact location to link points to?

Normal WAI page http://10.76.1.141

Link on page comes up as:

https://10.76.1.141:8080/default.aspx

Is this what you are looking for?

OK, so http still goes to the default port 80 and https goes to 8080....

Where did you do that? And why?

And one more obvious question: does default.aspx exist?

I would advice you to put everything to their default ports again (80 for http and 443 foor https) and try if both https://10.76.1.141 and http://10.76.1.141 work. If they do, all we have is a link in WAI pointing in the wrong direction, which should be easy to fix.

I thought I replied to this already, sorry.

Still no change. I think I've got something screwed up in IIS.

I'll have to do some more testing...

Thanks for the help.

Hi,

you did the whole "create a certificate request, sign it myself with openssl and reimport it to IIS"-routine?

Regards, Manuel Martin

(BTW, I like to use XCA http://www.hohnstaedt.de/xca.html to manage certificates.)

Of course I didn't!

I thought of that on the way home tonight. I told you it was something stupid I did...or didn't do.

I think I'm going to start on my new project of time compression by adding 8 hours to the average day. If I'm successful, I should be a millionaire in 3.2 minutes, but by that time being a millionaire will mean that I can afford to go to the movies...by myself.

I'll have a look at the keys tomorrow. I'll keep you posted.

Time for a

I just wanted to follow-up that this was resolved a while back. Just forgot to reply.

Windows Server 2003 resource kit includes an easy utility called selfssl.exe. It is a command-line utility that automatically creates the certificate and installs it. 30 seconds to create and install!

http://www.microsoft.com/downloads/details...&DisplayLang=en

Enjoy!

Thanks 4 the feedback!