Search results

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.

I see plenty of posts about upgrading/converting from CentOS to AlmaLinux. Does/will Plesk support upgrading AlmaLinux? Or just Debian/Ubuntu? The latter is discussed at https://support.plesk.com/hc/en-us/articles/12377374654231-Does-Plesk-support-dist-upgrade- but that page doesn't mention...

Thanks. Yes my first thought of upgrade-in-place was that sounds like a great way to crash everyone's site at once. But it avoids the migration headaches and DNS changes.

Hi, thanks for the response. So you use VMs now instead of containers? It costs a bit more in Virtuozzo and uses more RAM but if it allows in place upgrades down the road that could save a bunch of time every ~5 years. I hadn't thought of a trial license, or been aware they'd increase it like...

I see the latest update readme mentions a script to upgrade from CentOS 7 to AlmaLinux 8. However it says Virtuozzo and Docker containers are not supported. Is there an alternative way to upgrade a container? If not, has anyone switched to using VMs instead of containers so future upgrades...

This suggestion (time limit hotfixes and/or system updates) can be voted on at Have some setting to limit days and timeframe of any updates

I understand this is an old thread but Plesk support pointed me to it. The configured update schedule is also not used for "system updates" which are always installed daily.

After banging on this a while I eventually found there was an IPv6 routing issue in the data center, outside of our equipment. It was a bit subtle as it only affected some IPv6 connections, both inbound and outbound, so was not easy to pick up in testing...most pinging was fine but the...

Support says a cert for any additional domain aliases is unnecessary and we should only create certs for the primary domain. :eek: I guess the "solution" is to validate only certain domains so it doesn't time out.

Per Change Log for Plesk Obsidian this extension is now part of SSL It, is that correct? Should a separate thread be pinned for that? Does anyone know a way to lengthen the timeout for an LE cert validation beyond the current roughly 10 minutes? See Issue - SSL It! - LE Cert fails: The...