• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by JazZ

  1. J

    Resolved Server get flooded - DDos using OpenDNS resolver

    I see ! This looks useful. The only thing that doesn't work is the type check but I do without it. = ) Thank you again @danami !
  2. J

    Resolved Server get flooded - DDos using OpenDNS resolver

    Great ! Sorry, you were right, u32 is case insensitive. The problem was coming from the last 4 bytes (there is only 3 last bytes). I think it was out of range. How to match them so ? The daemon.log file doesn't get flooded anymore. Thank you !
  3. J

    Resolved Server get flooded - DDos using OpenDNS resolver

    Thank you very much ! I wish I could build something like this myself. I'm trying to understand the syntax and how it works. Could you help me break it down ? 0>>22&0x3C@20&0xFFFFFFDF=0x01320953 From what I read, the first part (0>>22&0x3C@) jumps over the IP header (dynamically). The...
  4. J

    Resolved Server get flooded - DDos using OpenDNS resolver

    Hum, no, I can't base the iptable rule on the Domain Name because the case is random too. I'm failing to find a solution for this...
  5. J

    Resolved Server get flooded - DDos using OpenDNS resolver

    Alright, after read the link content several times, I think I understood the point. In the presented case, he base the iptable rule on DNS Transaction ID, DNS Type, Domain Name and the Flag. In my case, the DNS transaction ID is always different. Do you think I can build the iptable rule...
  6. J

    Resolved Server get flooded - DDos using OpenDNS resolver

    Hello, thank you for your reply. You're right, it's technical and unfortunately, I'm not skilled enough to build the right iptable rule following the link you shared. Another solution would be to disabled OpenDNS Resolver. But, I'm not sure if I can do that and keep hosted websites accessible...
  7. J

    Resolved Server get flooded - DDos using OpenDNS resolver

    Hello, Since two days, my server running on Debian Wheezy with Plesk 12.5 is getting flooded by an attacker using OpenDNS resolver to DDos Avast Secure DNS. Those queries are correctly denied but it generates huge I/O level while writing the denied queries in log files (daemon.log and syslog)...
  8. J

    Resolved Problem with rights in Webserver

    Ok. So, like Peter said, it must be an application issue. I don't think it's php fpm relative… Contact the application developper to report this issue.
  9. J

    Resolved Problem with rights in Webserver

    You are saying that you connect to the server through SSH as root user to launch the script isn't it ? You could create ssh access for the domain user under the plesk domain access configuration, connect with its creds and execute the script as that user. That way, the owner and the group of...
  10. J

    Resolved Random 403 error

    Hello, I was inspecting the top stats and found that the memory use was pretty high. Here is more info : There is about 25 Pretashop CMS on the server and 25 Wordpress CMS. CPU: Intel Xeon E3-1220 3.10Ghz + ILO RAM: 16GB Disks: 2x 2000GB HW RAID 1 OS: Debian 7 Wheezy, 64 Bit Bandwidth...
  11. J

    Resolved Random 403 error

    I got news about this. We migrated the problematic domain on another server and the issue is resolved for this one. But today, we face the same issue on other domains on the old server. It's not only one domain. I really need help on this and it would be appreciated. Thank you.
  12. J

    Resolved Random 403 error

    Sorry to bump up this but I'm really stuck and need help…
  13. J

    Resolved Random 403 error

    Hello, I face a weird issue since one month with Plesk 12.5.30 on a dedicated Debian Wheezy server. There are several domains hosted there (Prestashop and Wordpress) but only one face this (a Prestashop) : Randomly, the response is "403 Forbidden". I inspected the logs and the only relevant...
Back
Top