Jon Bishop
New Pleskian
Just try renaming it;
# mv /root/.my.cnf /root/.my.cnf.disabled
Okay that worked... Do I need to put it back, or does the upgrade create a new one?
Just try renaming it;
# mv /root/.my.cnf /root/.my.cnf.disabled
I'll start stupid and just ask - You have Nginx installed, correct? HTTP/2 and Apache require some hacking.
What's the error?
@MitchellvB995 if you are still under Debian I think the "rpm -qa | grep courier" you previously did doesn't makes much sense: try "dpkg --list | grep courier" instead...
Exactly what Sergio had.... this will remove it;
# dpkg -r psa-courier-unicode
mod_php, mod_perl, mod_python Apache modules drop
- Previously these modules were very popular and widely distributed, but nowadays usage of these components is deprecated and is not recommended. Using these modules in a shared hosting environment is a security risk for the following reasons:
- File security. mod_php, mod_perl, and mod_python run under the identity of Apache server itself, and therefore scripts executed by these engines can potentially access anything the server user can. For example, files containing highly confidential personal data could be read by a script from another domain.
- Security of database connections. DBI connections of other users can be hijacked, and since all users can read each other’s code, database usernames and passwords could be visible to every user.
- Potential system compromise. Security issues in the Apache code can lead to compromising the whole server in general.
- What to do? If you are updating to Plesk Onyx 17.8 from previous Plesk versions and you have these modules installed, you will still have these modules available on your servers and will be able to manage them until you switch to a different, recommended, module like mod_fcgid. However, new Plesk Onyx 17.8 installations will not have mod_php, mod_perl, and mod_python modules available. We strongly recommend avoiding usage of these modules to keep your servers safe and secure.
Besides this, my Plesk 17.8.10 server updated to 17.8.11 this morning, automatically. Where are the release notes of this version?
Hi,
does plesk 17.8 support http2 with apache? If no, is there a way to enable http2 for apache?
Thanks, will try it tomorrow. It's gonna be an "errors party"CentOS? Check my other post; Why is Plesk using multiple protocols?