• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Issue [PMT-2980] Migration error 10054

Staf999

New Pleskian
Hi specialists,

I'm trying to do a full migration from one server to another but get this error:

[2016-08-02 09:20:20][ERROR] Failed to perform action: Fetch information from target servers
Cause: <urlopen error [Errno 10054] An existing connection was forcibly closed by the remote host>
That is a critical error, migration was stopped.

source server: 2008 R2 with plask 12.5
target server : 2012 R2 with plesk 12.5

Firewalls are off on both sides.

I also tried the CLI method:
https://kb.plesk.com/en/127304

i can generate the domain transfer list but when i start the transfer is get the error.
All DNS settings were automatically copied though.

Anybody an idea?
 
Thx, i found that article also but didn't help me.
I can access plesk config on both servers with : https://localhost:8443/
Or am i misunderstanding the information and need to add localhost somewhere else?
 
Hello!

I have no ideas about root cause, but Plesk Migrator has a workaround for cases if Plesk API not accessible via HTTPS. You need to configure migration via CLI and specify following option in [plesk] section of migration configuration file:

plesk-protocol = "http"
plesk-port = "8880"

Also you need to allow access to Plesk API via HTTP by adding following lines into panel.ini:

[api]
allowPlainHttpAccess = true

But be aware: such configuration is insecure and very undesirable, so it could be used only as a workaround.

And unfortunately, because a bug PMT-2980 at Plesk Migrator side, you can not change protocol via option plesk-protocol in migration configuration file. Plesk Migrator still will use HTTPS. But fix will be availalbe in future Plesk Migrator release - at the middle of September.
 
Back
Top