Re: [users@httpd] Cannot access my webserver any longer

2015-06-26 Thread Cohen, Laurence
Thank you. We now found a couple of other users which are able to get through to the website, so now some of us can and some of us can't. I'm guessing it has to be in the browsers of those of us who can't, but why would we not be able to access from all browsers (IE, Firefox, Chrome)? I'm extreme

Re: [users@httpd] Cannot access my webserver any longer

2015-06-26 Thread Yehuda Katz
That is a generic error message when Chrome does not have a more specific error to show. Something else I would try is to use something like the openssl command line to verify the certificate. You can use the command "openssl s_client -connect server_name:443" to have OpenSSL tell you what certifi

Re: [users@httpd] Cannot access my webserver any longer

2015-06-26 Thread Cohen, Laurence
Thank you. Chrome says "You cannot visit website xxx.yyy.com right now because the website sent scrambled credentials that Chrome cannot process. I'm not sure where these credentials are coming from, but I'm assuming this is the .crt files in httpd/conf/ssl.crt. Thanks, Larry On Fri, Jun 26, 20

Re: [users@httpd] Cannot access my webserver any longer

2015-06-26 Thread Yehuda Katz
When Chrome does not show the coninue option, it usually has an additional error message where the button would be that shows more details. For example, this is an HSTS error: http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-47-13-metablogapi

Re: [users@httpd] Cannot access my webserver any longer

2015-06-26 Thread Cohen, Laurence
Thanks for the response Yehuda. Unfortunately Chrome doesn't give me this error. It just tells me that my connection isn't private. When I click on advanced there is no option to go forward to the web server like I get on some of the other servers I work with. Larry Cohen On Fri, Jun 26, 2015

Re: [users@httpd] Cannot access my webserver any longer

2015-06-26 Thread Yehuda Katz
I have seen this happen when you send an HSTS header. The Chrome error would say that specifically. A workaround would be to install that certificate on your system (with the mmc certificate snap-in) so that it becomes a trusted certificate - trusted site in IE is not enough. - Y On Fri, Jun 26,

[users@httpd] Cannot access my webserver any longer

2015-06-26 Thread Cohen, Laurence
I have a test server on which we have a self-signed certificate. I get the error "There is a problem with this website's security certificate." which is expected because I'm using a self-signed cert. Normally I click on "Continue to this website (not recommended)." and it goes through to my websi