Facebook
Twitter-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Resolved Problem apache after upgrade to debian 8
- Thread starter garcue
- Start date
U
UFHH01
Guest
Hi garcue,
pls. note, that an error like:
If logs are not created at the standard paths, you might consider to restart the depending services ( here: service apache2 restart ). Pls. consider as well, to verify, that the definitions at your Fail2Ban - jails match your current settings for the depending service(s). A example control command like:
... could help you to investigate, if the defined log - paths are still valid and the log(s) existent. 
To reconfigure your webserver - configuration files, you could use the Plesk Repair Utility, with an example command like:
pls. note, that an error like:
... indicates, that Fail2Ban can't be started, as one jail ( => apache-overflows ) can't find the configured log - definitions.
If logs are not created at the standard paths, you might consider to restart the depending services ( here: service apache2 restart ). Pls. consider as well, to verify, that the definitions at your Fail2Ban - jails match your current settings for the depending service(s). A example control command like:
Code:
ls -lah /var/log/apache2To reconfigure your webserver - configuration files, you could use the Plesk Repair Utility, with an example command like:
Code:
plesk repair web -y -v
U
UFHH01
Guest
Hi garcue,
as you experience issues with Fail2Ban in the first place, pls. consider to DE- and RE-install the component. A detailled suggestion how to do that has been given here: => #50
If you experience, that your apache webserver didn't create the serverwide logs at "/var/log/apache2" ( on Debian/Ubuntu - based systems ), pls. consider to investigate the reason(s).
as you experience issues with Fail2Ban in the first place, pls. consider to DE- and RE-install the component. A detailled suggestion how to do that has been given here: => #50
If you experience, that your apache webserver didn't create the serverwide logs at "/var/log/apache2" ( on Debian/Ubuntu - based systems ), pls. consider to investigate the reason(s).
- Restart the apache2 - webserver with the command ( logged in as user "root" over SSH ):
... and watch out for possible issues/errors/problems at the command line.Code:
service apache2 restart - Use an example FIND - command like
and make sure, that an entry like:Code:
find /etc/apache2 -type f -name "*.conf" -exec grep --color -Hni "/error.log" {} \;
... is existent and not commented with an "#" in front at your "apache2.conf".Code:ErrorLog ${APACHE_LOG_DIR}/error.log
- Use an example FIND - command like
and make sure, that an entry like:Code:
find /etc/apache2 -type f -name "*.conf" -exec grep --color -Hni "/access.log" {} \;
... is existent and not commented with an "#" in front at your "/etc/apache2/sites-available/000-default.conf" and "default-ssl.conf"Code:ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined - Pls. check, that at least ONE symbolic link for "000-default.conf" or/and "default-ssl.conf" is existent at "/etc/apache2/sites-enabled"
Similar threads
