Did you ever get this to work? I've realized we have some Debian 12 servers that show the page and some that don't. The ones that show the Plesk 404 page (the astronaut) do not have an entry in /var/log/apache2/other_vhosts_access.log.
I ran into this once a while back. That implies there's an IPv6 connection or configuration problem. LE will try to connect from multiple source IPs and if it fails to connect it won't renew the cert.
Plesk accepted the idea and is looking for votes. Since Windows is already a small share of the Plesk install base it would be helpful to have as many votes as possible.
Came back to this again...I didn't see an open feature request so I created one, if you would please vote for it:
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/48447479-set-helo-ehlo-name-in-mailenable-on-windows-at-ple
FWIW it works on a slave name server container, I upgraded two. I just had to re-save the existing firewall config in Virtual Administrator afterwards, to get it to allow DNS. Have not tried a Plesk container yet.
(I also upgraded a non-VZ VM under Hyper-V by upgrading in two steps to CentOS 8...
Thanks for the pointer, found our new Plesk install had it defaulting to "home" as in servername.home and that was causing problems. The other fields had been left blank. Seems like Plesk should set this at install.
I had to add a "mail.servernamehere" domain/site to Plesk in order to save the...
If you know their IP you can add it to the Trusted IP Addresses list. We have one client who doesn't want to track down the phone that's been failing POP logins since last summer, and yet is surprised when their office changes IPs and it gets blocked again.
Just to call it out, we have run into a few scattered cases where the Plesk migrator ends up with a duplicate SPF record (which causes it to eval as failure, so Gmail now refuses mail for a nonexistent SPF) or other duplicate records such as mail.domain.
Thanks for the update. I got sidetracked on projects so didn't get back to it yet. I see Virtuozzo added the "yum install vzdeploy8" bit to the docs, I did get far enough to figure that out.
Maybe it'll work on the Plesk slave DNS if Plesk isn't installed.
I did try to convert a small...
Since this is my thread I'm going to resurrect it...
Virtuozzo 7.5 update 5 hotfix 1 added "The ability to convert the CentOS 7.x, CentOS 8.x, VzLinux 7.x, and VzLinux 8.x operating systems running on a container to AlmaLinux 8.x."...
For the record I just tried this on a domain on 18.0.52. The Plesk migrator extension does migrate DNS. It does create an AAAA record for ipv4.domain and an A record for ipv6.domain. It tries to "addzone" the domain and doesn't say it fails but then immediately rejects the transfer:
May 19...
Agree, we may just do that and hope it works down the road. The goal here was actually whether to set up new servers using Alma or Debian, with Debian 11 having only 3 years of support left.