migration tool - fails to connect as remote user

Discussion in 'Plugins/Modules/Addons' started by Lushy, Jun 27, 2019.

  1. Lushy

    Lushy New Member

    Hi all,
    I'm hoping someone can help. I have a Centos 6 installation and migrating to a new server (Centos 6). I keep getting an error either in dry or migraiton mode. The initial SOAP connection as the remote user fails:

    [ERROR] API call to login failed. See log file for details.
    Could not connect to api. Please check if the data you provided is correct.

    However, I do not see any attempt to access the server in the apache logs. To make things more complicated, I created a php script to test the remote user and this logged in no problems at all - plus I see the logon showing in the apache logs.

    The migration log is showing:
    2019-06-27 14:35:59 - [ERROR] JSON API ERROR in API call (login): NO ACCESS
    2019-06-27 14:35:59 - [INFO] Trying again (login)
    2019-06-27 14:36:01 - [ERROR] JSON API ERROR in API call (login): NO ACCESS
    2019-06-27 14:36:01 - [INFO] Trying again (login)
    2019-06-27 14:36:03 - [ERROR] JSON API ERROR in API call (login): NO ACCESS
    2019-06-27 14:36:03 - [ERROR] API call to login failed.
    2019-06-27 14:36:03 - [ERROR] JSON API ERROR. Arguments sent were: array (
    'username' => '<remote user>',
    'password' => '<password>',
    )
    2019-06-27 14:36:03 - [ERROR] Could not log in to api at https://<target server>:8080/remote/ with user migration.

    I'm running ISPConfig 3.1.13p1 on both servers. I'm running php 5.4 on the source server and php 5.7 on the target.

    I've checked the obvious things like making sure the account has all the grant options selected and I can login via a soap connection to it.

    I'm at a loss as to why the script is failing and I am not seeing a connection attempt in the logs.

    Any one have any thoughts?

    Thanks

    Rich
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Try to start the migration tool like this:

    ./migrate --legacy-tls

    This switches the tool into the legacy tls mode, it helps when the two servers are not able to communicate over tls.
     
  3. Lushy

    Lushy New Member

    Perfect, that was the fix.

    Thanks
     

Share This Page