You are not logged in.

#1 2017-11-04 06:57:17

pancibule
Member
Registered: 2017-11-04
Posts: 6

AH00072: make_sock: could not bind to address when including httpd-ssl

Hi,

I installed the latest apache package on a new server. There is no other software running (except ufw).

I can start httpd via systemctl after installing it. But as soon as I uncomment line "Include conf/extra/httpd-ssl.conf" it fails to start.

$ apachectl graceful
httpd not running, trying to start
(13)Permission denied: AH00072: make_sock: could not bind to address [::]:80
(13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80

I searched for all "Listen" commands:

$ grep -ir "^listen" /etc/httpd/
/etc/httpd/conf/extra/httpd-ssl.conf:Listen 443
/etc/httpd/conf/httpd.conf:Listen 80

I searched for other software which uses port 80:

$ ss -tlpn | grep 80

(No Output)

I really don't know what to do now. Obviously, port 80 is not used and there is only one "Listen 443" and one "Listen 80" in the conf files. httpd runs as long as I don't include "conf/extra/httpd-ssl.conf" …

Last edited by pancibule (2017-11-04 07:21:26)

Offline

#2 2017-11-04 15:25:09

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: AH00072: make_sock: could not bind to address when including httpd-ssl

Processes need to be run as root to bind to low port numbers, you're running apachectl as a normal user.

Why are you using apachectl at all? You should be using systemctl instead.


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2017-11-09 18:30:02

pancibule
Member
Registered: 2017-11-04
Posts: 6

Re: AH00072: make_sock: could not bind to address when including httpd-ssl

slithery wrote:

Why are you using apachectl at all?

I did not use it. I used it to get the short error message. I started Apache as root with

$ sudo systemctl start httpd

Then the error occurs.

However, I fixed this in the meantime by switching to Debian. I used almost the same configuration there without encountering this error.

Thanks for your help.

Offline

Board footer

Powered by FluxBB