Recent content by SimonG

The reason for having a different IP for each nameserver is to provide redundancy: so if one is not available the other one may still be. But if both IPs are on the same server, then whatever affects the first one will probably also affect the second one. To get good redundancy you need two...

Note that a second IP will not benefit you unless it is on a different server.

That one routes the output - including any error messages - to /dev/null. So the first thing would be to change that to a suitable log file location, so you can see if it produces any messages.

I've never found the preview function to be satisfactory. (That goes for other panels, not just Plesk). For testing I think it's better to edit the hosts file on my PC.

It sounds like they're in different subscriptions, in which case it's not possible to use an open_basedir exception to allow one site to access a file from another webspace - only from another site within the same webspace. There's no simple way around that, other than using an HTML ref to the...

Are the websites in the same subscription? I think that open_base_dir only enables access within the same subscription.

Have you clicked on the button to "Detect Hardware Changes"?

Also note that an SSL certificate issued for www.domain.tld will not necessarily be valid for other subdomains, e.g. mail.domain.tld. Unless you've got a wildcard certificate - one that covers multiple subdomains - you may need a second certificate for mail.domain.tld.

I don't think that there's any Plesk utility that will just sync emails between the two servers. However, there are a number of tools which might allow you to do that separately after the main migration, and allowing time for the new DNS records to propagate. The one I've used in the past is...

Try... systemctl restart httpd.service

Make sure that you have completed the steps to enable Passive FTP, and that you have permitted access to your chosen passive ports range in the firewall rules. How to configure a passive ports range for ProFTPd on a server behind a firewall?

It doesn't look unusual to me. Most linux servers suffer from large numbers of failed login attempts and Fail2Ban will deal with them. If you haven't already done so you should consider activating the "recidive" jail. That will permanently block any repeat offenders.

From the Plesk panel, you can either remove a specific item from the queue or clear everything. Neither of these will cause the email to be sent. Emails will get re-tried automatically a number of times. You can force the deferred email queue to be processed immediately, but only via SSH...

If your users are using POP, then they'll have all their messages locally, presumably, and may not need messages transferred between the servers. But if you do need to transfer messages between the servers, whether the end users use POP or IMAP isn't really relevant: you can still use that IMAP...

If you're not comfortable with using the command line, you CAN view the files using SFTP, with a normal FTP client such as FileZilla. Care is still needed, though, as you'll be accessing the server as root, presumably, and could cause significant damage if you make changes.