Difference between revisions of "CentOS 8.x apache troubleshooting"
m |
m |
||
Line 1: | Line 1: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x web servers]] > [[CentOS 8.x apache web server]] > [[CentOS 8.x apache troubleshooting]] | |||
==Apache fails to start with unable to bind to port 443== | ==Apache fails to start with unable to bind to port 443== | ||
Line 32: | Line 31: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x web servers]] > [[CentOS 8.x apache web server]] > [[CentOS 8.x apache troubleshooting]] | |||
Revision as of 17:36, 15 May 2022
Home > CentOS > CentOS 8.x > CentOS 8.x web servers > CentOS 8.x apache web server > CentOS 8.x apache troubleshooting
Apache fails to start with unable to bind to port 443
It is possible that apache fails to start with unable to bind to port 443 error. In such cases if we look at
ss -alnpt | grep 443
We can see which program is listening on port 443 already and try to stop it. However, it is possible to receive this error even when:
- There is no program listening on port 443
- There is no SELinux based blocking
- You are trying to start apache as root user (Not related to Linux permissions for port numbers less than 1024).
It was found that this can happen when there are multiple:
Listen 443
at different places in apache configuration. For example one such line could be there in custom SSL certificate configuration file and one such could be there in /etc/httpd/conf.d/ssl.conf.
Hence to look for duplicate "Listen 443" use:
cd /etc/httpd grep -r -i "listen" conf conf.d
If you find "Listen 443" at more than one place and then one of them needs to be commented to be able to start properly.
Refer:
Home > CentOS > CentOS 8.x > CentOS 8.x web servers > CentOS 8.x apache web server > CentOS 8.x apache troubleshooting