Search results

You could remove the .ini files named "newrelic.ini". Example: /opt/plesk/php/5.4/etc/php.d/newrelic.ini

You could add the Name Turnitinbot to the robots list of the file.

Have you also checked the permissions and ownership of your .htaccess file? It should be at least 0644 and <your subsription user>:psacln.

Make sure that your httpdocs folder has permissions 0750 and that it is owned by <your subscription user>:psaserv.

It shows in which PHP files "newrelic" is mentioned. Could you maybe provide an excerpt (with redacted domain names)?

It's hard to tell what's going on remotely through the forum posts. Maybe you could open a support ticket with Plesk support? They will for sure be able to assist you directly on the server and they will certainly solve the issue. Sign in here: https://support.plesk.com . In case you bought your...

Did you follow the steps in (Plesk for Linux) Hardening Server Connections Using DANE ?

Is DKIM checked on the mail settings dialog page of the domain?

Has the domain DKIM enabled?

The Plesk backup storage is specified by the DUMP_D variable defined in the /etc/psa/psa. conf configuration file. The default location is /var/lib/psa/dumps. In order to download a backup, it is best to download it from the GUI, because in the /var/lib/psa/dumps directory you won't find a...

Is there any output from # grep -R newrelic /etc/php-fpm.d # grep -R newrelic /opt/plesk/php/*/etc/* ?

Switching the ruleset might not be necessary. For one case, another ruleset might work, but it may create false positives in other cases. Instead, examine the error_log entry where the 403 error is logged. It will mention an [ID .......] field. This is the rule ID that triggered the 403 block...

No, it is not required if your log files have a default format.

I cannot see why it doesn't work for you. You could try to first test it with fail2ban-regex. It might give better clues.

Some data centers block port 25 by default, so it might not be blocked on your server, but in a firewall at your data center. Have you already contacted them on the issue?

This could also be of interest: https://support.plesk.com/hc/en-us/articles/12377967588887-How-to-change-the-location-for-Plesk-backup-files-on-a-Linux-server

/var/lib/psa/dumps stores all local backup files. You can remove local backup sets from Tools & Setttings > Backup Manager or - if they were created by a subscription user - from Subscription > Account > Backup Websites.

I've seen an incredible increase of such robot visites especially from Amazon AWS instances recently. It went up about 12 times of the usual traffic, measured across a dozen machines, so probably it's a general issue as it does not target specific IPs or domains. You can try to block the traffic...

I didn't mean to say it's a permission issue with the .htaccess file, but that it could be an issue with the file permissions of files that are addressed by a request.

You can find an example in the above mentioned blog article.