don't click here

Help Apache2 not booting up

Discussion in 'Technical Discussion' started by segamaniac, Jul 24, 2023.

  1. I'm trying to get my web server to boot up, but instead gives me this error:

    Jul 23 19:44:34 segamaniac-HP-Notebook apachectl[6103]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
    Jul 23 19:44:34 segamaniac-HP-Notebook apachectl[6103]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
    Jul 23 19:44:34 segamaniac-HP-Notebook apachectl[6103]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
    Jul 23 19:44:34 segamaniac-HP-Notebook apachectl[6103]: no listening sockets available, shutting down
    Jul 23 19:44:34 segamaniac-HP-Notebook apachectl[6103]: AH00015: Unable to open logs
    Jul 23 19:44:34 segamaniac-HP-Notebook apachectl[6100]: Action 'start' failed.
    Jul 23 19:44:34 segamaniac-HP-Notebook apachectl[6100]: The Apache error log may have more information.
    Jul 23 19:44:34 segamaniac-HP-Notebook systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE

    This just started happening when I turned off then turned on my server, don't know what could've suddenly caused this. Any help is greatly appreciated, thank you in advance.
     
  2. President Zippy

    President Zippy

    Zombies rule Belgium! Member
    I don't know which other problems may manifest, but one problem is that you're listening on 127.0.1.1, rather than 127.0.0.1 (the IP addr of localhost).

    As an aside, if you want to test IPv6 support, you can also add [::1] to your listener addresses.
     
  3. I actually got this fixed somehow on the same day I posted this and I have no clue how I fixed this, it was even around the point where I was about to call quits on Apache2 and install Nginx lol. But speaking of which, I realized that minidlna now isn't working for some reason in strange nature much like Apache2 was, it's running, but not showing within the LAN network, and I now I suspect it's something to do with what you said.

    Thank you btw!