LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   can not use https (https://www.linuxquestions.org/questions/linux-general-1/can-not-use-https-4175484996/)

ust 11-18-2013 07:45 AM

can not use https
 
I have newly setup redhat web server - apache , php , I tried to use http , it works fine , but when use https , the browser link https is crossed by a red line , and the web page can not be loaded , I sure the ssl cert is correct , the error log show nothing , could advise what is the possible reason ? thanks

Ser Olmy 11-18-2013 08:12 AM

Clicking on the SSL icon in the address line (the exact location depends on the browser being used) should provide further clues at to why the SSL/TLS connection fails. It could be as simple at the date/time settings on the client computer.

Are you using a self-signed certificate?

ust 11-18-2013 08:46 AM

Quote:

Originally Posted by Ser Olmy (Post 5066581)
Clicking on the SSL icon in the address line (the exact location depends on the browser being used) should provide further clues at to why the SSL/TLS connection fails. It could be as simple at the date/time settings on the client computer.

Are you using a self-signed certificate?

yes , self-signed certificate

Ser Olmy 11-18-2013 08:51 AM

Well, there's your problem.

Most browsers choke on self-signed certificates. To view the page, you'll have to create an exception manually.

sundialsvcs 11-18-2013 08:53 AM

Just walk through the error-logs (usually somewhere in /var/log, and study the error-messages that you will see there.

You need to ascertain why the connection is being refused, and by which party (client or server). "Self-signed" is a red-herring because your browser would be complaining ... asking if you want to accept it ... if you were actually getting that far, which you are not. Therefore, it will be something in your Apache config, and/or in the files and/or the permission-settings for those files [i](i.e., can Apache=nobody see/read them?). And, the error-logs will contain the necessary clue.

ust 11-18-2013 09:38 AM

Quote:

Originally Posted by sundialsvcs (Post 5066604)
Just walk through the error-logs (usually somewhere in /var/log, and study the error-messages that you will see there.

You need to ascertain why the connection is being refused, and by which party (client or server). "Self-signed" is a red-herring because your browser would be complaining ... asking if you want to accept it ... if you were actually getting that far, which you are not. Therefore, it will be something in your Apache config, and/or in the files and/or the permission-settings for those files [i](i.e., can Apache=nobody see/read them?). And, the error-logs will contain the necessary clue.

I checked apache error_log , but do not show error , what logs else can check ? thanks

ericson007 11-18-2013 04:37 PM

When the warning comes up in your browser click on get certificate so that it can be added. Simple as that.

byran cheung 11-18-2013 10:03 PM

Quote:

Originally Posted by sundialsvcs (Post 5066604)
Just walk through the error-logs (usually somewhere in /var/log, and study the error-messages that you will see there.

You need to ascertain why the connection is being refused, and by which party (client or server). "Self-signed" is a red-herring because your browser would be complaining ... asking if you want to accept it ... if you were actually getting that far, which you are not. Therefore, it will be something in your Apache config, and/or in the files and/or the permission-settings for those files [i](i.e., can Apache=nobody see/read them?). And, the error-logs will contain the necessary clue.

thx reply ,

which directive that I should change ? thanks


All times are GMT -5. The time now is 07:59 AM.