https not working

[ajw_doc]

I've created an SSL request and imported the cert from my SSL provider however https doesn't work. When I go to https://www.domain.com I get


Safari can’t open the page “https://www.domain.co.uk/” because it can’t find the server “www.domain.co.uk”.

I obviously have SSL enabled. What else do I need to do?

Thanks,

AJ

[ajw_doc]

In Firefox I get this:


Secure Connection Failed

An error occurred during a connection to www.domain.co.uk.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)

The page you are trying to view can not be shown because the authenticity of the

received data could not be verified.


I've double checked the information and it is the same. The cert is vaild for one year so the I've got 365 days.

[ajw_doc]

"SSL received a record that exceeded the maximum permissible length."

This generally indicates that the remote peer system has a flawed implementation of SSL, and is violating the SSL specification.

If anyone can tell me what I need to do to sort that out that would be great! I'm running Fedora 9 installed using the guide on here.

[ajw_doc]

Firefox is now showing:
Data Transfer Interrupted

The connection to www.domain.co.uk has terminated unexpectedly. Some data may have been transferred.

[ajw_doc]

After all that it was a simple mend - mod_ssl wasn't installed ;)

[ajw_doc]

Still not working - I now have it showing as a self signed cert although the cert key is the one from the company. What is going on?!

[falko]

Did you read this short guide? http://www.howtoforge.com/faq/14_49_en.html

[ajw_doc]

I did but it fails to tell you about the bug that doesn't restart httpd so the new certificate can kick in. I found it after some googling. It has been addressed apparently but in my version 2.2.23 it is still there and us tempting as it is to ugrade to 2.2.24 I dont see any easy upgrade instructions so I'm not going to risk it !!

All sorted now though!

[falko]

that doesn't restart httpd
I think this resolves itself after you restart ISPConfig manually on the shell. It seems to be a problem with environment variables.