Search results

Only in so far that you should only be root when necessary and do other tasks with an unprivileged account. However we're talking about Plesk servers where usually the only reason you need to log in at all is to do things you can't do from or repair the web interface, for which you need...

Does it get faster if you lower the MTU to 1492 or less? If yes, then MTU Path Discovery is broken.

Did you check whether you're connecting to the website by ipv4? What's your MTU? These are suspicious:

No, it isn't. You should, however, use PasswordAuthentication no or at least PermitRootLogin prohibit-password. Make sure your key works before restarting sshd.

Do you have chroot active? Might be better to use relative links ../../../httpdocs/wp-content/uploads

On debian/ubuntu I would use update-alternatives to select which php `php` points to, no idea how that works in centos, worst case you'd have to manually overwrite /usr/bin/php with a symlink to your desired php binary.

With that setup, nobody would be able to send email to support@longdomainname.com unless that account is configured at google too. The MX with the higher number will only be tried if google's server can't be reached or responds with a temporary failure code. But an account that isn't recognized...

fail2ban maybe?

Doesn't aptitude give you any options to resolve those dependencies?

I do not support spammers.

As long as the A/AAAA records for serveur001.domain.com do not point to cloudflare, that is not a problem. You can use the same certificate on different servers. You can also use different certificates as long as the issuer is not forbidden via CAA record in DNS. You can even use different...

I think I'm seeing something similar here ... this morning at 6:26, Plesk updated itself to 18.0.63mu3. Just a minute later, I got a Package Update Manager notification for 108 packages, some of them skipping several versions (e.g. "libc-bin 2.31-13+deb11u10 from Debian-Security for...

You haven't? What did you try, then?

I would guess it is this problem again: Issue - apache2 proxy target - wrong ip-address

Isn't that by design? I think you'd need to use separate redis instances if you want to avoid this.

or you could just use webmail.domain.com for imap and smtp ...

${} does not do what you think it does. Lose the {}. And it's 'exit', but you don't actually need that because the script ends anyway.

Oh, and you should restrict the mariadb users to that IP. See mysqltuner for how.

No, it's just that you're listing the worker status. SHOW GLOBAL STATUS LIKE 'created_%'; has a very different result.

Did you recently restart the mysql server? Also, you should have a look at mysqltuner. Don't blindly follow the recommendations, though.