Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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.
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.
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.
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
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.