Search results

I would agree with many of your points on the progress of the 12.5 version as far as new functionality and features, that is why I was trying to move to it. But if you can't migrate your clients from your current production server to this new version, then those new features and improvements...

First off, let me summarize what is and isn't happening. What IS happening: The domain, IP assignment (no matter if shared or dedicated) and DNS records are all migrated successfully. The DNS is correctly reformatted to the target server's DNS Template, it even revises the SPF record...

Thanks again for your help.

I tried that and even re-imaged the entire server and it still doesn't work. I have tried it with many domains that are on my current production server (source) and it is always the same. I looked at the XML for the webspace and there are a few. Strangely, the ones for the domain have error...

Next half:

Thanks for your help. Here is everything from the first stack trace I could find (I have to post 2 replies, it won't allow so much in one post):

I want to mention that the target is a clean install brand new server - Plesk 12.5.30 on Centos 7 Here is the entire last section of the debug.log file. I don't see any additional E codes in there: Duplicate emails come from target server as if everything is OK. The domain is created on...

Another odd and maybe irrelevant item is that I get 2 notification emails for each domain that is migrated (or sort of migrated).

Just noticed another component update for the Migration Manager. I updated and... still doesn't work. Don't know what they are fixing with all these daily updates but it isn't this problem.

Thanks for your suggestion. Both source and destination were completely unlimited to begin with but I created new unlimited plans on both and it still failed with exactly the same errors.

I have searched everywhere for an answer to this and finally have to resort to posting a new thread. Using Migration Manager to move individual sites from source server: CentOS 6.7 (Final) Plesk version 12.0.18 Update #70 To a new destination server: CentOS Linux 7.1.1503 (Core)‬ Plesk...

OK, got it. The MU 48 evidently wiped the OS user credentials for installing software. I had to put in my su credentials and now it shows me the updates and upgrades page with the v12 panel upgrade available (although the link and upgrade notification still isn't in the home page of the panel...

New question - Did MU 48 change the way the plesk updater works? I finally got through to the update page and it is asking for the login credentials. (see screenshot) I have never seen this before and this server has never allowed root login. As I said, I haven't changed a thing and it showed...

--2014-10-24 02:20:42-- http://autoinstall.plesk.com/plesk.inf3 Resolving autoinstall.plesk.com... 72.21.81.253 Connecting to autoinstall.plesk.com|72.21.81.253|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 284525 (278K) [text/xml] Saving to: “plesk.inf3”...

No, it is not blocked.

I am beginning to think the MU broke the connection of the panel to Parallels servers. The Tools & Settings > Updates and Upgrades link just opens a blank window that never loads. I would guess that is also why the link on the home page is gone. There is no connection to Parallels so it...

After last night's auto-update to MU 48, I no longer have the link on the panel home page to upgrade the panel to V12 and going to the update / add components area doesn't give me the option either. All traces of being able to upgrade the panel to v 12 have disappeared. Anyone know what is...

I have it too on one of my two Plesk servers. Plesk version 11.5.30 patch #15. CentOS 6.4. It has been happening since update #13 or 14. Parallels dev team... Hellloooooo.... This is all over the plesk forums.

Thanks for the explanation. I'm not much of a Linux guy and have never had a problem with Atomic updates in many years of using them for my servers, especially for php and mysql. I did notice it appeared that the php module was not loading but didn't have the overall knowledge to figure out...

If you do a yum update for php and use the atomic repository, BE CAREFUL! The latest version 5.3.26 from ART repository created a big problem with apache for me with my Plesk 11.0.9 / Centos 5.9 box. After the update, Apache will fail to start with this error: # service httpd restart...