Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author nexyadev

    (@nexyadev)

    Merci pour les commentaires heureux que le plugin vous plaise 🙂

    nexyadev

    (@nexyadev)

    Two details in the .htaccess part are worth fixing:

    1. The file is xmlrpc.php, with no hyphen. <Files xml-rpc.php> matches nothing, so XML-RPC is still open.
    2. Order allow,deny / Deny from all is Apache 2.2 syntax. On 2.4 it only works through a compatibility module. Use Require all denied inside the <Files> and <FilesMatch> blocks instead.

    Also check that your Duplicator packages don’t stay only on the same server. Download them or send them off-site, or a hack can take the backups with it.

    For the daily checks you mentioned: we make nexya, so take this with that in mind. Every day it compares the WordPress core files and your wordpress.org plugins with the originals, and e-mails you if something changed. It also flags PHP files dropped in uploads, locks out repeated failed logins (from 15 minutes up to 24 hours), hides user names from visitors and sets security headers.

    It isn’t a firewall, though, so keep your Cloudflare rule in place.

    • This reply was modified 1 day ago by nexyadev.
    • This reply was modified 1 day ago by nexyadev.

    This pattern usually comes from one of two things. Either the web server thinks it hosts your domain’s mail, so it delivers locally and never looks at your MX records (common when the mailbox lives at Google/Microsoft and the site is on cPanel).

    In that case set Email Routing to “Remote Mail Exchanger” in cPanel, or ask the host to do it.

    Or your mail provider rejects or quarantines mail claiming to come from your domain without passing SPF/DKIM.

    Check its quarantine and make sure the mailer you use is in your SPF record and signs with DKIM. In WP Mail SMTP, sending through your mailbox provider’s own SMTP or API usually fixes both, and the email log shows the response.

Viewing 3 replies - 1 through 3 (of 3 total)