After reebot server have: Internal Server Error on visit any site

Oops! Something went wrong.

The server encountered an internal error or misconfiguration and was unable to complete your request.

Error Code: 500

apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-04-02 00:35:39 +05; 4min 5s ago
Docs: Apache HTTP Server Version 2.4 Documentation - Apache HTTP Server Version 2.4
Process: 625 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

апр 02 00:35:39 apachectl[625]: AH00558: apache2: Could not reliably determine the serve
апр 02 00:35:39 apachectl[625]: (99)Cannot assign requested address: AH00072: make_sock:
апр 02 00:35:39 apachectl[625]: no listening sockets available, shutting down
апр 02 00:35:39 apachectl[625]: AH00015: Unable to open logs
апр 02 00:35:39 apachectl[625]: Action ‘start’ failed.
апр 02 00:35:39 apachectl[625]: The Apache error log may have more information.
апр 02 00:35:39 systemd[1]: apache2.service: Control process exited, code=exited status=
апр 02 00:35:39 systemd[1]: Failed to start The Apache HTTP Server.
апр 02 00:35:39 systemd[1]: apache2.service: Unit entered failed state.
апр 02 00:35:39 systemd[1]: apache2.service: Failed with result ‘exit-code’.

or /var/log/apache2/domains and check

did you manually change the config files for apache? then there probably is a problem or something got overwritten during the last update.

as @eris suggested, you need to check your logfiles or try restarting apache2 an run journaltctl -xe directly afterwards which might hold more detailed information on the error. we simply can’t diagnose that from here for you :wink:

the problem is that apache doesn’t start automatically after the system boots up

[Fri Apr 02 01:34:14.922523 2021] [mpm_event:notice] [pid 789:tid 140225804841024] AH00492: caught SIGWINCH, shutting down gracefully

systemctl is-enabled apache2

check this error:

99)Cannot assign requested address: AH00072:

no that’s not the problem but the impact.

you need to figure the real problem by researching the log files or getting more information by looking at journalctl as suggested - magic eight ball is out for maintenance, so I think you need to do it all by yourself :man_shrugging:t2:

in first post log from journalctl

@qwxpr please check this.

need to start apache2 after loading all services. How did it? Or restart on crush

There is an issusse with the avilbiltiy of your IP. We are not able to debug your server with out any access. So go look and find what the issue is…

if i run service apache2 start ALL run ok
ports are not busy

When the system starts the ip is not availble for a short period you need to find out why. …

is hard i dont cnow how, delay for apache is easy i think

closing this up here. enough advise has been given, please solve YOUR issues using YOUR sysadmin skills and knowledge. we can’t further support with things that are clearly not related to Hestia anyway.