Can't connect via https:// after setting require https://

[primate]

I setup Secure Gateway and all was working using both

http://server.company.com

and

https://server.company.com.

I wanted to restrict access to the web interface to just https:// so I selected Require Secure Channel and require 128-bit encryption in directory security on the root of the website. I selected to apply this to the folders beneath the root folder.

After doing this I can no longer connect using the https:// URL, all I get is a 404 file not found error. Connecting to the http:// URL returns the expected "you must view this over a secure connection" error.

I tried unselecting the Require Secure Channel option and I can reconnect again using http:// but still can't connect using https://

Any suggestions?

 

[byteya]

https uses port 443, while http uses port 80. Are these BOTH open on your firewall/router?



*J*

 

[primate]

Yup - "I setup Secure Gateway and all was working using both

http://server.company.com

and

https://server.company.com.

 

[byteya]

Duh - sorry I missed that first line.

We had problems with users that had old versions of IE accessing our site via HTTPS. Before IE6 you could install 56-bit versions of IE, which don't work when you are requiring 128-bit encryption. Might be worth checking out.



*J*