LinuxQuestions.org - [SOLVED] SSL timing out to outside world

- Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)

- - SSL timing out to outside world - works on LAN. (RHEL,APACHE) (https://www.linuxquestions.org/questions/linux-server-73/ssl-timing-out-to-outside-world-works-on-lan-rhel-apache-4175495283/)

SSL timing out to outside world - works on LAN. (RHEL,APACHE)

Hello all,

For the life of me I can not figure out where I have gone wrong in this setup.
I installed the certs from the providers like I was instructed.
My server serves SSL on the LAN with no issue or warning, but outside it times out.
Web services that check for SSL certs told me I did not have one at all.

I do know that port 443 is open.

here are my configs:

httpd.conf:

Code:

<VirtualHost *:80>

        ServerName sub.domain.com

        Redirect permanent / https://sub.domain.com

</VirtualHost>

the ssl.conf is included at the foot of the httpd.conf

Code:

LoadModule ssl_module modules/mod_ssl.so



Listen 443



AddType application/x-x509-ca-cert .crt

AddType application/x-pkcs7-crl    .crl



SSLPassPhraseDialog  builtin



SSLSessionCache        shmcb:/var/cache/mod_ssl/scache(512000)

SSLSessionCacheTimeout  300



SSLMutex default



SSLRandomSeed startup file:/dev/urandom  256

SSLRandomSeed connect builtin



SSLCryptoDevice builtin



<VirtualHost sub.domain.com:443>



DocumentRoot "/path/to/domain/"

ServerName sub.domain.com:443



SSLEngine on



SSLProtocol all -SSLv2



SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW



SSLCertificateFile /path/to/crt

SSLCertificateKeyFile /path/to/key

SSLCertificateChainFile /path/to/intermediate



</VirtualHost>

Am I missing something?

Thanks in advance.

-mtlhd

Maybe try doing a reverse lookup on your sub.domain.com ip address and changing your config to either

111.222.333.444:80/443

or

sub.comain.com:80/443

Whatever your server cert returns.

Been a while since I had my head into apache conf's but maybe worth looking at.

P.S.; I am presuming you've already ensured that there is not a firewall ruleset somewhere that's blocking your connections.

Thank you for the reply,

after much research, much to my dismay, I discovered the port was indeed closed in the firewall. I was told it was open but that's what I get for assuming the info was correct.
Sorry to waste time!

-mtlhd

Np. Glad you got it sorted.