@Sebahat.hadzhi
I am asking in reference to the MariaDB Upgrade tool.
There is no specific set of custom config files that I am referring to, since it is a general question.
However, I can state the following.
In many test scenario's, I use two types of customizations :
1 - inline...
@Sebahat.hadzhi
I am aware of the fact that one has to - forcefully - remove some files.
However, my main concern was (read: back in the days that I tested the Imunify extension) that the firewall rules were "removed" in a very unpredictable way : in some cases, all entries were deleted...
@Sebahat.hadzhi
It is probably difficult or even impossible to replicate a specific symptom.
In essence, there are multiple "symptoms" which are very likely to be caused by ONE root cause of the problem.
In addition, the "symptoms" are not consistent over time - in a test environment, I...
@Sebahat.hadzhi
Are there known issues for upgrades of installations with custom config?
How are they dealt with in the process? Are backups of (custom) config files made?
I am curious .........
Kind regards....
@Sebahat.hadzhi
Problem here is that Plesk addresses one problem, being the "unwanted" installation of Imunify.
Nevertheless, this "issue" (or bug) has been present for a longer time period - removing Imunify extensions has (always) been a (tiny) bit problematic.
In addition, Imunify...
@Sebahat.hadzhi @Bitpalast
Error codes are NOT limited to 105 codes.
The random behavior of DrWeb is also resulting in other symptoms, like 109 error codes (incompatible software) and/or failures to download files (without any output of error codes whatsoever).
I have played around a bit...
@mow
First of all, thank you for the reply - I like this kind of in-depth discussions, since they do add value, even to the Plesk forum.
In my humble opinion, a rock-solid discussion is a good starting point to come to a roadmap for future development ..... come to something in agreement.
In...
@Airborne3d
This statement
would also puzzle me, if @Kaspar is right.
I have created a "ticket" many many many years ago to request the functionality of SSL secured MySQL connections.
Apparently, this ticket did not result in the functionality that is - apparently - desired by many...
@mow,
Well, yes and no.
The original idea (or concept) was - essentially - to increase security : making information available that allows the identification of "unsafe" certificates, with the "(advantageous) byproduct" of additional minimization of the attack surface by means a reduction of...
@Airborne3d
First of all, local Plesk databases are run over socket, so TLS / SSL is not necessary at all - do not attempt to install it, since that can or will cause havoc.
Secondly, if you want the external MariaDB server to function as a remote dbase for the (local) Plesk, then it is safe...
@MHC_1
Please provide some information about the server that you are working on/with.
By the way, this statement
indicates that the very likely root cause of the problem is related to some kind of IP blocking as a result of a - continuously - changing IP address.
For that reason, just...
@Sebahat.hadzhi
There are two things to distinguish :
1 - issues related to time delays, with an (authentic) MFA app on the client-side,
and this statement
addresses those issues.
I found (in the past) that the time delay is not consistent, in the sense that it was 1 second in one test...
@Sebahat.hadzhi
This statement
is a clear indication that - whenever needed (and that is almost always) - server time synchronization should be checked before installation (as a first step).
This statement
is true and this is in many ways dangerous.
For instance, if the server time is...
@Sebahat.hadzhi
The CRL implementation is a bit tricky.
Let me explain in the most simplest of terms, for the benefit of all Plesk Forum users and for the general understanding of OCSP and its alternative, the CRLs.
OCSP is effective, in the sense that it is - simply stated - equivalent to...
@Sebahat.hadzhi
I personally would NOT recommend the command : apt install --reinstall ca-certificates
That command would imply (re-)installation of a package, hence a "dirty workaround" - if that workaround would work at all.
In essence, if x numbers of repositories do work fine and y...