Search results

Just to verify that the manual intervention via SQL command worked.

That's the incoming direction. Those of interest are with :25 below "Foreign address".

Also check netstat -tpn for any connections to foreign port 25 or 465 from programs other than postfix.

I actually did try before posting and couldn't reproduce. plesk just wouldn't proceed with adding another server. It looks like this: Note that there is the same message you have, but for the postgreSQL connector, which we do not use. Does the account you use for plesk have full admin rights...

Why does this look like the question was run through and remixed by ChatGPT or similar generative AI? BTT: I'd guess @schauhan11 just didn't notice the server at first. Or the internal server only shows up since a later update. If you enter invalid authentication data, you can't finish adding a...

That's still an improvement because now the websites won't be on that highly fragmented disk anymore. First, you should not store backups on the same server anyway, especially not on the same disk. Second, if you think incremental backup is wasteful, you're doing something wrong. Daily full...

Yes.

I recommend using a more narrow pattern like "*.smtp-out.amazonses.com", though.

Doesn't that allow every host to connect? (And what happened to using the socket /var/run/mysqld/mysqld.sock only, not using TCP/IP connections at all?)

Because it's not necessary when it's the same name. In the maillog I find the mentioned complaint about SNI, so that means SNI was used, right? Have you looked into the maillog? Should there be no message like above, I guess plesk only configures SNI for domains that differ from the default...

By the way, the SNI configuration is broken, resulting in postfix/smtpd[1611847]: TLS SNI server.com from client.de not matched, using default chain every time SNI is used. It still works because the default chain is the one for server.com, verified with openssl s_client -connect server.com:465...

Then your user has a shell that is not bash. You could change that with chsh or by editing /etc/passwd directly, but running another shell might break scripts or cronjobs that rely on the shell being whatever it is now, so be sure to test.

You should contact IONOS and ask if there's anything in the logs of the host your VPS runs on.

Not much, save for bugs. But for a container, the host should have same or newer kernel version than the guest, otherwise there could be required features missing. So with an up-to-date host, you have a better chance of a guest upgrade succeeding.

Because MUAs default to using subdomains for well-known services.

That's the system-wide log. You obviously have /var/log/apache2/error.log. However, this will only show errors that aren't associated with a vhost. Those logs are in /var/www/vhosts/system/<domain>/logs.

That means you set rDNS wrong. Change to vps.i-web.nl.

How did you set that up? You do have two separate wordpress installations, right? I don't think multisite is supported by plesk yet.

Use smartctl -a /dev/nvme1 or nvme smart-log /dev/nvme1 etc. on the devices and compare the power_on_hours, that should tell you which ones were recently installed :) (if neither is installed, install smartmontools or nvme-cli) When you know the new ones, you can build the new raid. Well, there...

Are your queries really using the nameserver, or do you have leftover entries in /etc/hosts?