Recent content by mow

cloudflare's challenge will also block legitimate users who don't have the most recent browser version installed or who block third-party scripts. Also, randomly API requests are blocked. And that's not counting the cases where cloudflare itself fails massively.

This is configured in the systemd unit file.

Are those all from different networks or just a few rogue providers? E.g. when I run grep "SASL LOGIN authentication failed" /var/log/mail.info |cut -f 5 -d ":"|sort|uniq -c, I get ... 8580 unknown[158.94.210.39] 177 unknown[158.94.210.86] ... for which I block the whole net...

@King555 Because POST parsing is where the vulnerabilities usually are.

... while explicitly stating that you are invoicing the undisputed part of the current price, but still uphold claim to the rest. If the client already does continue to pay the old price, just send a payment reminder instead.

Add to .htaccess: <Limit POST> Order Deny,Allow Deny from all Allow from <your IP addresses> </Limit>

But you accessed the nginx port (80 or 443), not the port apache runs on, so the deny/allow settings don't even apply to your connection.

Since a while, apache binds to localhost by default. This is not automatically updated, but a new install will do that, and a restore won't change back to the old setting.

Yes, but there also is a limit to the amount of enshittification we will tolerate.

okay, that's even more bugs then. The additional restart was enough to fix our Taubenkot.

I'd guess that's what saved you: another restart after all the changes were really done. Relevant part of autoinstaller3.log: Setting up plesk-dovecot (2.4.1-4-v.debian.11+p18.0.73.3+t251009.1752) ... Installing new version of config file /etc/dovecot/conf.d/10-plesk-security.conf ...

I have no other idea how the error message could reference file contents that don't exist anymore, though. The file timestamp 03:18:20 exactly matches the error message.

It seems that during the upgrade, Plesk restarts dovecot before updating all the config files, which is bound to fail. Rookie mistake. Makes one wonder whether there are any experienced developers left at Plesk.

YOU GET PAID FOR DOING THAT. Today I got woken up by a phone call, while sick at home, that email doesn't work. Logged in and found: Nov 03 03:18:20 sourcetronic.com systemd[1]: Starting Dovecot IMAP/POP3 email server... Nov 03 03:18:20 sourcetronic.com dovecot[1780787]: doveconf: Fatal: Error...

And maybe change the time, or that poor server will be DDoSed by all the plesk installations ...