Skip to main content

httpd failing unable to connect to port 80 connection died

Comments

10 comments

  • userarray user

    I have the exact same with my cPanel 124.0.34 (on CloudLinux v8.10.0), tried refresh, restart but still doing, I get message every 5-10 hours.

    0
  • mtindor

    Probably related to the following thread, given the references to traffic-apache.log

    https://support.cpanel.net/hc/en-us/community/posts/31634624163735

    Of course, if you are running Ubuntu then your instructions for handling the package change would be different.

    You might be able to fix it by making sure that /var/log/cpanel-server-traffic/web exists.

    /var/log/cpanel-server-traffic is chmod 700 and owned by root

    /var/log/cpanel/server-traffic/web is chmod 700 and owned by root

    At any rate, if you make sure the directory exists and then restart apache that'll probably fix your problem if it exists on Ubuntu.

    If on RH-based CL then follow the instructions in the article.

    0
  • maestroc

    Those directories were not present on my system.  I just added them and chmodded them to 700 as you said.  I'll let you know.

     

    1
  • cPRex Jurassic Moderator

    Let us know if you still see issues!

    0
  • maestroc

    I am still getting the same httpd crashes.  Random times.  Twice more so far since I added those folders and restarted httpd.  I can confirm the folders are owned by root and 700 for permissions but it doesn't seem to have had any effect.

    0
  • maestroc

    If it makes any difference this server started on Alma Linux then converted to Cloud Linux.

    0
  • cPRex Jurassic Moderator

    Could you make a ticket so we can investigate this directly?  It's always possible there could be something happening besides that case.

    0
  • maestroc

    My license is through my VPS provider so I'm unable to get your direct support anymore.  I've asked my provider but they are unsure of what to do as well...

    0
  • cPRex Jurassic Moderator

    If your provider can't resolve the issue they should escalate the ticket to us so we can take a look directly.

    0
  • maestroc

    I believe they have now put in a ticket on this.  Just be aware that now it is happening on another server that I am responsible for.  Same exact error.

    0

Please sign in to leave a comment.