Search results

Maybe you could start with # package-cleanup --problems

I'm afraid I won't be able to edit this. The article is meant to jump start you and others on the topic. I am using similar settings on my servers here, but meanwhile already with a lot of changes as attacks constantly evolve. But what you could do is to add the suggested modification as a...

This has one ".so" too many. Could you maybe edit the .ini file where it is located and remove the one .so?

I think there is something wrong with the SQLite database where the WP Toolkit extension stores some values, but it's hard to say what. If there are not too many websites on the server, maybe removing WP Toolkit and reinstalling it can help. Otherwise or if you have doubts about taking that...

You may need @pleskpanel 's solution shown in Issue - Default plesk-apache-badbot fail2ban doesn't work

Existing files managed by Plesk may be changed, but additional custom files that you create will not be touched. There is no such hook, but why can you not let Plesk manage the certificate for you?

This means that the file is good. It's just the online file viewer who doesn't like the ".ini" ending I guess.

I must admit that I've been ignoring this and put my own config into the files anyway. The only situation where this ever needed a manual intervention was on the centos2alma upgrade when Dovecot was completely reinstalled. But many years before the configs were never changed.

If the pages really exist, you can only manually ban the IP, e.g. # fail2ban-client set recidive banip <ip address goes here> But if you find a file that responds with a code 200 but is actually not a valid page of the site, you could use that to detect the bot and ban it automatically.

@cloudadmin If possible, do you still know the time of the migration and the website? We'd like to check it in the server logs here. You can send the information in a private message to me.

@cloudadmin Could you please tell me the Migrator version on the source server that you have used for migration? Current versions should migrate the Sitejet key, too. Maybe it was an outdated version? You can find the version in the "Extension" on the Migrator icon.

That is strange as the files in /etc/dovecot/conf.d should not be overwritten on updates.

And what exactly had to be edited?

Can you read the file on the console, like # cat /var/www/vhosts/<your subscription domain>/httpdocs/config.ini ? What permissions and ownership does it have?

As I understand it, your bot does not have a signature (no name) and it only crawls existing pages, correct? Are you sure that all the 200 responses are truly existing pages or might a rewrite rule in your .htaccess file respond to everything with code 200?

Please contact Plesk support on this topic. It will need to be checked on your server. To sign-in to support please go to https://support.plesk.com If you experience login issues, please see this KB article...

You could make a Plesk extension out of it. https://docs.plesk.com/en-US/current/extensions-guide/create-your-first-extension.76333/

The problem lies in what's an "established" connection. Once the same source IP, target IP and port have successfully connected (and passed the iptables rule that can rate-limite connections), they are considered "established" so that all consecutive requests will also pass. So rate-limiting...

There are two feature requests for oAuth with Plesk that you could vote on: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/45597829-secure-plesk-mail-servers-with-modern-authenticati...

This does not seem to be a Plesk issue, but rather a PHP issue that should be reported to PHP developers.