Facebook
Twitter
D
Dragan Marjanovic
Guest
Using the migration manager will reset all ssl certificates for all your IP addresses to the default ssl certificate for the server you are migrating to! I'm using plesk 9.2.1 on centos 4 32bit.
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
We just hit the same issue using the migration manager to move a site from a Plesk 9.2.3 installation on RHEL4 to another Plesk 9.2.3 installation on RHEL4.
The certificate for all sites using a dedicated IP address and a dedicate certificate was reset to the certificate of the default site using the main IP address of the server. We had to manually reassign the correct certificate to all sites!
There is a workaround here:
http://forum.parallels.com/showpost.php?p=395046&postcount=39
I hope the fix will be included in an updated Plesk version asap, since it's not acceptable for this bug to be around this long!
Thanks.
The certificate for all sites using a dedicated IP address and a dedicate certificate was reset to the certificate of the default site using the main IP address of the server. We had to manually reassign the correct certificate to all sites!
There is a workaround here:
http://forum.parallels.com/showpost.php?p=395046&postcount=39
I hope the fix will be included in an updated Plesk version asap, since it's not acceptable for this bug to be around this long!
Thanks.
E
Eric Haskins
Guest
How do I manually reassign the certs? This just happened to me
According Release notes problem described here is fixed in 9.3.0 version:
http://download1.parallels.com/Plesk/PPP9/plesk-9.3.0-for-rpm-based-os.html#5
http://download1.parallels.com/Plesk/PPP9/plesk-9.3.0-for-rpm-based-os.html#5
N
nedry
Guest
While the 9.3 release notes may say that this problem is fixed, it seems to not have been completely fixed.
I just migrated about 40 domains to a new server and about a third of them were still pointing to the old certificate. I changed the first few by hand (edited using a command line editor). Then I discovered that editing anything in the Web Hosting Settings for the domain would also change the certificate.
What a pain! Since "upgrading" from the rock solid Plesk 8.6 to the flakey Plesk 9.3 I've run into one bug after the other. I would rather Parallels would spend some serious time testing and fixing bugs and stop this crazy rush to advance the version numbers.
I just migrated about 40 domains to a new server and about a third of them were still pointing to the old certificate. I changed the first few by hand (edited using a command line editor). Then I discovered that editing anything in the Web Hosting Settings for the domain would also change the certificate.
What a pain! Since "upgrading" from the rock solid Plesk 8.6 to the flakey Plesk 9.3 I've run into one bug after the other. I would rather Parallels would spend some serious time testing and fixing bugs and stop this crazy rush to advance the version numbers.
It's definitely not completely fixed, the current status is that 9.3 will bring the certificate over but screw up the assignment and turn off the use same directory for secure requests check box if you had it on before, so every site you migrate you have to go in and turn that back on and choose the existing certificate all over again, before your web server will restart. So it's easy to tell when a migration has finished for us since the web server will go down and we'll get an alert from our monitoring system. But cut them some slack, it's only been a few months, it took eight months to fix the last issue. LOL 9.x should be stable by December I think, then they'll release 10.
N
nedry
Guest
I'd be happy with Plesk 9.3.x releases for the next year if all they did was fixed bugs. It would also be nice if they brought back the rest of the features they removed when they "upgraded" Plesk 8.6.
I need reliability far more than I need new features!
I need reliability far more than I need new features!
