Jtdylktuy

I am facing a problem with my SSL/443 port. I setup a website which is currently being hosted on Apache, port 80. I do have an SSL certificate and was able to redirect HTTP to HTTPS -- but after a while port 443 stops responding to requests and I have to revert back to using port 80. Somehow 443/HTTPS works for little bit and then stops working.

On the modem (Actiontec C2100T - CenturyLink) - I have both port 80 and 443 open. However when I check online if 443 is open, I get the following: Error: I could not see your service on 97.118.xx.xx. on port (443)

On the webserver (RasberryPi) - I ran an nmap scan:

Starting Nmap 7.40 ( https://nmap.org ) at 2019-02-08 17:50 UTC

Nmap scan report for Unknown.domain (192.168.0.30)

Host is up (0.000051s latency).

Not shown: 996 closed ports

PORT    STATE SERVICE   VERSION

22/tcp  open  ssh       (protocol 2.0)

80/tcp  open  http      Apache httpd 2.4.25 ((Raspbian))

85/tcp  open  http      Apache httpd 2.4.25 ((Raspbian))

443/tcp open  ssl/https Apache/2.4.25 (Raspbian)

So I don't think it's the server -- but I could be wrong. Here is my Apache config as well. I've commented out VirtualHost 443 for now until I can figure out why the port becomes inactive after being initially configured.

<VirtualHost *:80>

    ServerName blissisit.com

    #ServerName localhost

    ServerAlias www.blissisit.com

    DocumentRoot /var/www/html



    #Redirect permanent / https://blissisit.com/

    #Redirect permanent / https://192.168.0.30/

</VirtualHost>



#<VirtualHost *:443>

   #ServerName      blissisit.com

   #ServerAlias     www.blissisit.com

   #DocumentRoot    /var/www/html

   #SSLCertificateFile      /etc/ssl/blissisit_com.crt

   #SSLCertificateKeyFile  /etc/ssl/private/blissisit.key

   #SSLCertificateChainFile /etc/ssl/blissisit_com.ca-bundle

   #SSLEngine On



   #ErrorLog ${APACHE_LOG_DIR}/error.log

   #CustomLog ${APACHE_LOG_DIR}/access.log combined

#</VirtualHost>

Any help is much appreciated! Thank you in advance.

Understanding the network topology goes a long way with nailing down these problems.

Is this server exposed to the internet (e.g. in the DMZ) or is in on a private network with ports forwarded? If the latter, when the server fails to respond, is it failing both externally and internally (e.g. with the servers local private IP)?
Confirm by testing both scenarios. Furthermore you can check the local loopback from the server.

Server logs can help as well. For apache these will be access.log and error.log. Location may vary by distro but generally located in var/log/apache/ or /var/log/apache2/ or /var/log/httpd/

Finally, you can try removing and re-adding the forwards, and possibly rebooting the modem/firewall. Also note that some ISPs do some trickery with their provided equipment as they may wish to deter non-business accounts from running servers.