Apache2 and Nginx servers will not start

Hestia-chat · May 6, 2023, 9:58am

Hello,
Both Nginx and Apache will not restart

May 06 10:15:36 expressresponse.net systemd[1]: Starting nginx - high performance web server...
May 06 10:15:37 expressresponse.net nginx[1555]: nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/etc/letsencrypt/live/gldn.page/cert.pem"
May 06 10:15:37 expressresponse.net nginx[1555]: nginx: [emerg] bind() to xx.xxx.xx.xx:80 failed (99: Cannot assign requested address)
May 06 10:15:37 expressresponse.net systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
May 06 10:15:37 expressresponse.net systemd[1]: nginx.service: Failed with result 'exit-code'.
May 06 10:15:37 expressresponse.net systemd[1]: Failed to start nginx - high performance web server.

and

May 06 10:15:36 expressresponse.net systemd[1]: Starting The Apache HTTP Server...
May 06 10:15:37 expressresponse.net apachectl[1565]: (98)Address already in use: AH00072: make_sock: could not bind to address xx.xxx.xx.xx:8080
May 06 10:15:37 expressresponse.net apachectl[1565]: no listening sockets available, shutting down
May 06 10:15:37 expressresponse.net apachectl[1565]: AH00015: Unable to open logs
May 06 10:15:37 expressresponse.net apachectl[1537]: Action 'start' failed.
May 06 10:15:37 expressresponse.net apachectl[1537]: The Apache error log may have more information.
May 06 10:15:37 expressresponse.net systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
May 06 10:15:37 expressresponse.net systemd[1]: apache2.service: Failed with result 'exit-code'.
May 06 10:15:37 expressresponse.net systemd[1]: Failed to start The Apache HTTP Server.

These are my IP ads

I ran

root@expressresponse:/# ss -tnlp | grep apache2
root@expressresponse:/#

No listeners ?

ALSO tried …

root@expressresponse:/# netstat -ltnp | grep ':80'
tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN      1962/nginx: master
tcp6       0      0 :::8080                 :::*                    LISTEN      1579/pmtahttpd
root@expressresponse:/# netstat -ltnp | grep ':8085'
root@expressresponse:/#

How do I fix this ?

Thanks

MAN5 · May 6, 2023, 4:28pm

***ALERT. 
EDIT YOUR POST &
Hide your IPs 1st.

If you have not given the details of your OS/Hestia-version/What changes made / whether is suddenly or on update/ etc.,
You havnt provide anything there but waiting for support.

It seems you have made some changes in your IPs recently. Becoz your main IP (with 16 domains) & Apache’s IP request is diff. Means it may be behind NAT. You have to work on it.

Hussein · May 6, 2023, 11:49pm

check the web templates for both the backend and proxy servers.

eris · May 7, 2023, 7:56am

github.com

hestiacp/hestiacp-docs/blob/master/admin_docs/settings.rst#unable-to-bind-adress

########################
Server setting / Config
########################

.. toctree::
  :maxdepth: 2
  :glob:
  
  settings/filemanager.rst
  settings/firewall.rst

*********************************************************
I am not able to login 
*********************************************************

For installing dependencies we use Composer. As are currently not able to run it under hestia-php version. We install it via /usr/bin/php. Make sure proc_open is allowed in the main php version. In the future we look in methods to allow install via composer via hestia-php.

*********************************************************
Where can I find more information about the config files
*********************************************************

This file has been truncated. show original

2nd issue is:
(98)Address already in use: AH00072: make_sock: could not bind to address 78.110.163.102:8080

Check why this port is allready in use

Hestia-chat · May 12, 2023, 5:14pm

When I try to start apache2 it fails as it tries to use 8080 which is in use by pmtahttpd

tcp6       0      0 ::1:783                 :::*                    LISTEN      1051/perl
tcp6       0      0 :::8080                 :::*                    LISTEN      1579/pmtahttpd
tcp6       0      0 ::1:53                  :::*                    LISTEN      797/named

However, apache2 is supposed be using 8085 according to my ports.conf file

root@expressresponse:/etc/pmta# cat /etc/apache2/ports.conf
# Powered by hestia
listen 8085

Why would apache try to start on the wrong port ?