There could be several reasons for the error.

Reasons for Apache not listening on port 443Īpache not listening on port 443 is a common issue that we see while handling server. However, server will accept connection on port 443 only if inbound traffic is allowed via firewall too.

Here, we replace IP with the specific IP address of the server that need to handle secure traffic. Or, if for security reasons, we need to restrict https connection on a specific IP, we set the Apache config directive as Listen :443 For example, to make the server accept connections on both port 80 and port 443, on all interfaces, we need to use: Listen 80 In Apache, the Listen directive tells the server to accept incoming requests only on the specified ports. And for this to work, 443 port must be open on the server and Apache should listen on this port.ĭata transferred across such https connections are highly resistant to eavesdropping. When you go to a website which uses the link containing at the beginning, you are connecting to port 443 of the web server. This secure transaction works using the SSL certificate. But, when it has to deal with secure web transactions, it uses the port 443. Today, we’ll see how Bobcares’ Engineers diagnose and fix Apache not listening on port 443 error.īy default, Apache uses port 80 for normal web traffic. This can happen due to many reasons like wrong Apache settings, firewall blocks and more.Īt Bobcares, we often get requests from customers to fix Apache related errors as part of our Technical Support Services. And, when the error affects multiple websites, things go for a toss.Īpache not listening on port 443 is a typical error that happens after turning ON SSL on websites. Web server errors often put users in a panic situation.

Apache tomcat 8 and svn