• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

Resolved General precautions and known caveats for updating 12.5.3 to 17?

Bitpalast

Bitpalast

Plesk addicted!
Plesk Guru
We are seeking a list of precautions and known bugs/caveats to plan the update from 12.5.30 to Onyx. For example is it recommended to de-activate ModSecurity and Fail2Ban before trying the upgrade? Are there any known risks, e.g. services that might not start after the upgrade because of changed configuration file locations or other reasons? How do we have to understand that update? Does it replace system libraries or does it only replace Plesk-owned scripts?
 
You must log in or register to reply here.

Similar threads

learning_curve
Resolved Fail2Ban IPv6 banning in Obsidian. Correct Plesk Configuration?
Replies
4
Views
6K
Guido
G
D
Input Very Slow Advisor - Plesk Update time out
Replies
0
Views
2K
Daniel Richards
D
Bitpalast
Input Upgrade experience 12.5.3 -> 17.5.3 on CentOS 7.3
Replies
0
Views
2K
Bitpalast
Bitpalast
N
Make error installing Memcached 72 (Debian 9)
Replies
11
Views
5K
NicolasUni
N
Bitpalast
Resolved "The System Updates tool is already installing updates in automatic mode. Please try later."
Replies
5
Views
9K
UFHH01
U
Back
Top