• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Contribution Site Import Extension with ModSecurity - Tip

trialotto

Golden Pleskian
Plesk Guru
@Everyone,

When using the Site Import Extension when having the Web Application Firewall (WAF/ModSecurity) activated with the Advanced ModSecurity Rules by Atomicorp, one will encounter some problems.

In essence, the following issues are present:

ROOT CAUSE OF THE PROBLEM: ModSecurity disallowing access

SYMPTOMS:
- file transfer and/or database transfer fails
- Fail2Ban database can become corrupted

SOLUTION:

1 - Go to the source server and login into the Plesk Panel,

2 - Go to "Tools & Settings > Web Application Firewall (ModSecurity) > Tab: Settings"

3 - add under "Configuration > Custom directives":

SecRule REMOTE_ADDR "@ipMatch <IP destination server>" id:101,phase:1,t:none,nolog,allow

and make sure to replace <IP destination server> with the proper IP.


Finally, with respect to the potential Fail2Ban database corruption, note that an additional thread will follow.

Hope the above helps a bit.

Regards........
 
Back
Top