• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Search results

  1. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    ok - thanks. Sounds promising. I'll follow this up tomorrow. I can't stare at this screen any more today!
  2. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    Looks like I am in KVM. [root@XXXXXX ~]# cat /proc/user_beancounters cat: /proc/user_beancounters: No such file or directory [root@XXXXXXX ~]# dmesg | grep kvm kvm-clock: Using msrs 4b564d01 and 4b564d00 kvm-clock: cpu 0, msr 0:1c35941, boot clock kvm-clock: cpu 0, msr 0:2215941, primary cpu...
  3. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    @danami I'm not sure, as it was just a quick off-the-shelf VM that I bought a few years ago. Can I tell from within the VM what type of VM it is, or would this only be available via the hypervisor? I've heard back from my hosting provider. They suggest rolling back the database. They want to...
  4. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    Again... good advice. The use of Route53 was not necessarily related to preventing DDoS. I was more pointing to my current scenario being one of limited resources, compared to my enterprise / day-job setup. We use Route53 as it has the ability to serve static content from an S3 bucket (ie a...
  5. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    Wow - thanks for the great reply. That all makes a lot of sense, and is a good overview of how to deal with a DDoS. I would have switched IP if I had another IP to hand. As I mentioned, this is just my sandbox server, that I used for a few local community / experimental sites. On our main...
  6. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    Thanks Dave. I saw in the logs that there were some db dumps floating around. I have a ticket open with my hosting provider, so hopefully they will give me some additional pointers. Otherwise, i'll try to rollback the db myself. This does't seem like it will get fail2ban working though, and the...
  7. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    Thanks for replying Igor. That article contains some useful pointers, but the bootstrapper repair script doesn't work for either version, and the database is ahead of the client, not behind. How can I find out why the 12.5.30 upgrade script is failing? It seems more sensible to get the client...
  8. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    And when I navigate to the plesk interface in a browser, i see: The file /usr/local/psa/admin/htdocs/index.php is part of Plesk distribution. It cannot be run outside of Plesk environment. Any help would be gratefully received. Extra bonus points for stopping this damn DDoS!! :)
  9. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    This is the end of the 12.5.30 boostrapper.sh output: Bootstrapper repair finished. Errors occurred while performing the following actions: fix credentials for PhpMyAdmin database, upgrade Plesk business logic, cumulative Plesk upgrade and repair final stage, configure SSL ciphers and...
  10. O

    Upgrading from 12.0.18 -> 12.5.30 problems, plus fail2ban and ongoing DDoS!

    Hi, I have a VPS with a handful of sites on. Nothing that critical. Plesk has been running fine for several years. I recently started getting CPU / Apache memory errors. I found that one of my sites has been under DDoS attack for about a week (only 1 request per second, but enough to take that...
Back
Top