Search results

If you really want to speed things up, use varnish. However that is hard to integrate with plesk.

maybe the version without the extra headers is still cached somewhere?

Then, that default landing page is also what you (or the bots) get with HTTP/1.0.

Part of this looks like double-bounce spam: The spammer sends a mail to an intentionally malformed address The receiving server does not reject the mail outright like it should, but only figures out it is bad / should be discarded after the message was already accepted, therefore that server...

And what site did you set as default? (the site you get when you access the IP)

No, you didn't follow that. You neither created a new partition nor a new swapfile to prepare with mkswap and then use with swapon. Be glad it didn't work, otherwise you would have overwritten your OS partition. But anyway, that there is no swap entry in your fstab means that it is configured...

Do you see an update in the plesk installer logs? Could this maybe be ubuntu auto-installing security updates?

That's strange. I've never seen any of those bots use HTTP/1.0. Do you have a stupid loadbalancer in front of your server? That can't work with modern (v)hosting because HTTP/1.0 is pre-SNI. All such requests would be served by the default server for the IP, same as if you'd directly supply the...

If the load with wordfence is higher than without, then wordfence is a problem, not a solution.

And the next step is to install lm-sensors to check whether the temperatures are normal.

Obligatory XKCD: Password Strength

Does amadeus set a Sender: header? SPF/DMARC can work with that too - that's also the workaround for forwarded mails.

No. SPF only checks the currently connecting host against the allowed list because all earlier Received: lines can be totally made up. (That's also why it doesn't go well with forwarding.)

No, as it is not an LTS version. So the next one would probably be 24.04.

No, that is not a problem as long as the SPF for example.de includes any entry that resolves to the IP you're actually connecting from. SPF only cares about IPs, not names. Where do you run the Mailserver configuration test?

Is there anything in the mysql error log?

That first screenshot seems to give a hint to what happened: There are two accounts named admin (how is that even possible??), and the user ends up as the lesser privileged one.

And maybe on the entry for localhost in /etc/hosts.

Have you checked the timestamps of the backup files to verify they're not in that time range?

Wait, you're still using MyISAM tables?