Persistent problems with our Plesk server Thursday 9th January 2025 16:21


We have noticed for some time that Plesk has some problems that obviously cannot be solved.

Accordingly, we will carry out a new installation next weekend. During this time, our websites and administrative interfaces will not be accessible.

The process does not affect the operation of our services.

We have just reinstalled the Plesk instance.

Why so late? We had made countless adjustments over the past weeks and days. Apparently, however, the server was misused for various illegal purposes, e.g. to run scans and logging services. And to distribute minimal TCP packets to various destinations. The search has taken some time, up to now we have recorded around 37 abuse reports. In addition, some errors were detected in all Plesk configurations in the early evening, which were no longer able to operate our web services.

Now that the server has been reinstalled and additional security services have been put into operation, we are continuing to monitor the situation closely and are constantly endeavouring to make further changes to our infrastructure for the future. In doing so, it plays an enormous role to phase out the solution: Plesk for our internal purposes.

The incident is over for the first time. Should we discover further problems or errors, we will initiate a new one.

We have just reinstalled the Plesk instance.

Why so late? We had made countless adjustments over the past weeks and days. Apparently, however, the server was misused for various illegal purposes, e.g. to run scans and logging services. And to distribute minimal TCP packets to various destinations. The search has taken some time, up to now we have recorded around 37 abuse reports. In addition, some errors were detected in all Plesk configurations in the early evening, which were no longer able to operate our web services.

Now that the server has been reinstalled and additional security services have been put into operation, we are continuing to monitor the situation closely and are constantly endeavouring to make further changes to our infrastructure for the future. In doing so, it plays an enormous role to phase out the solution: Plesk for our internal purposes.

The incident is over for the first time. Should we discover further problems or errors, we will initiate a new one.

We were able to narrow down the problem using a network loop.

Despite the existing possibility, we still assume a Plesk error and will endeavour to reinstall the entire Plesk instance in the coming night.

The instance is currently running without any major problems.