Provisioner not working (Revo-to-Revo)

I'm trying to connect from one Revo 2.1.3 site to another 2.1.3 site using Provisioner (1.1.0, latest), and I can't get it to work. I am getting "Login to the remote site failed - Access Denied"

I'm sure it isn't a password issue, or a wrong site identifier, or a bad user. I've quadruple-checked all of those things.

I was able to connect successfully to a different site at a different hosting provider. But I can't connect in either direction with these two installations.

Is there anything I could have done to my installations that would screw up a provisioner login? I tried disabling all plugins related to login events, thinking maybe that was the problem, but it didn't help. I'm really not sure what else to look for.

Hi, Provisioner won't connect to sites above and including 2.1.3, this should be documented on download page, you can install it in a 2.1.3 site and connect to a lower revo version or evo version.

Damn. Well, at least that explains my predicament. I had been using it very infrequently on these sites since much earlier MODX versions, so wasn't expecting it & didn't look for a version compatibility issue.

Is there any good way post 2.1.3 to migrate content from one server to another? Any plans for a future-compatible version of provisioner?

A user on Twitter (LarsCWallin, IIRC), mentioned that he was working on updating Provisioner, but I'm not sure how far he's gotten or if he's still at it.


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODX info for everyone: http://bobsguides.com/modx.html

I'm also trying to migrate a 2.1.3 large site to modxcloud and Vapor didn't produced the expected results. I'm aware Provisioner doesn't work with 2.1.3. Has someone solved this?

I don't want to run on risks trying to update a production site.
Any other options?

Thanks in advance.

I think Vapor requires at least 2.2.x, so you'd have to upgrade the site first. If you do end up upgrading the site, I'd suggest disabling all plugins before running the upgrade. It's possible for a plugin to crash setup.

If you look around the forums, there are some methods for upgrading a live site that only have it down for about 10 minutes and you can revert to the previous site immediately if the upgrade goes bad. Susan Otwell (Sottwell) has the best method, IMO. You just rename the MODX directories and files in the MODX root and rename them back if Setup goes bad.



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Thanks Bob, i'll try and research over that way.