Recent content by SteveITS

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...

I only had to set the server's primary domain name (server.example.net) so it would use it in the outgoing greeting.

ref: converter script by @websavers: Question - Upgrade Virtuozzo container from CentOS 7, haven't tried it yet.

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."...

3 https://support.plesk.com/hc/en-us/articles/12388069544215-How-to-get-Plesk-Web-Host-edition-trial-license-for-migration

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.

Yes thank you but still not my question. :) Or are you saying in the future it will also work for CentOS->CentOS, Alma->Alma, and other RH based distribution version upgrades?

I don't suppose that's in print somewhere? We're thinking of moving from containers to VMs for some servers to allow for OS upgrades but if they end up not supporting OS upgrades then an AlmaLinux VM doesn't gain us anything.

Yep, I'm aware of that. I was asking about, say, AlmaLinux 8 to 9. All I've found so far is Debian/Ubuntu based version upgrades.