HOWTO migrate stuff automatically from WebFaction!
sean Thank you Sean. I think i filled out everything correctly but do get this error:
Traceback (most recent call last):
File "/usr/local/bin/wfmigrate", line 66, in <module>
migrator = __import__(COMPONENTS[args.component]['module']).Migrator(cfg, args)
File "/opt/app_migrators-1.3.1/wf_wordpress/migrator.py", line 27, in __init__
self.wf_cfg = WfCfg(cfg['webfaction'])
File "/opt/app_migrators-1.3.1/lib/config_types/wf_cfg.py", line 12, in __init__
self.update_derived_attrs()
File "/opt/app_migrators-1.3.1/lib/config_types/wf_cfg.py", line 16, in update_derived_attrs
self.wf_session_id, self.wf_account_cfg = self.wf_api.login(self.wf_account, self.wf_password, self.wf_server.capitalize(), 2)
File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request
verbose=self.__verbose
File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib64/python3.6/xmlrpc/client.py", line 1170, in single_request
return self.parse_response(resp)
File "/usr/lib64/python3.6/xmlrpc/client.py", line 1342, in parse_response
return u.close()
File "/usr/lib64/python3.6/xmlrpc/client.py", line 656, in close
raise Fault(**self._stack[0])
xmlrpc.client.Fault: <Fault 1: 'LoginError'>
My password contains various characters which are not alphanummerical, might that be it?
webscience we'll do some testing on our end and fix if necessary.
sean did you have looked into this issue? Thank you Sean for your help.
One thing I wanted to post to help others that might get confused as I did. The config asks for your Opal and WF server names. Do NOT include the full domain name, only the first part. IE Opal4 or web556 and nothing else. If you include the rest it will cause issues. Unfortunately this isn't really stated anywhere that I saw so it hung me up for a while.
On the issue of Wordpress database passwords..The info in the OP says that the password will not be migrated, and so we should update the password to match our original password on WF.. however, the MariaDB won't let me use the same password because it doesn't have a number in it.
I'm waiting for the DNS propagation so I can see if I can figure out how to update the password on the WordPress side, but not 100% familiar with that setup so we'll see.
- Edited
jwvanderbeck Do NOT include the full domain name, only the first part.
The examples in the boilerplate config show that, eg:
server = opal1
...
server = web1Follow the examples as provided and you should be good 
jwvanderbeck The info in the OP says that the password will not be migrated, and so we should update the password to match our original password on WF.. however, the MariaDB won't let me use the same password because it doesn't have a number in it.
In that case you should use the second option in the instructions, ie "update your application settings to use the new DB password".
webscience I don't think the migrator dev has got to this just yet but most likely will within the next day or two
sean Yes the boilerplate shows it that way and maybe that made it obvious to you, but it was not obvious to me. I am simply sharing my experience in case others run into the same misleading errors.
- Edited
The info in the OP says that the password will not be migrated, and so we should update the password to match our original password on WF.. however, the MariaDB won't let me use the same password because it doesn't have a number in it.
In that case you should use the second option in the instructions, ie "update your application settings to use the new DB password".
Yes, I just need to figure out HOW to do this
Ok just a follow up for information on the Database Password thing.. it appears that the Wordpress migrator at least DOES take care of the password for you. I finally found information on how to edit it, it is inside a PHP file, but the proper password was already in there.
So if you are migrating Wordpress it seems that this amazing script does it 100% for you. All I had to do by hand was update my domain's nameservers to point to Opalstack.
jwvanderbeck Yes, I just need to figure out HOW to do this
For Wordpress, that would be changing the DB_PASSWORD option in your app's wp-config.php once the migration is complete.
sean Yep I found it, but it appears the migration script had already changed it for me, so all was good!
- Edited
Just to confirm the obvious, this is a read-only action on the WebFaction side and won't modify anything there. Right?
And second, will this work with the private Maria instances? I'm assuming so, just set the right target info.
leehinde Just to confirm the obvious, this is a read-only action on the WebFaction side and won't modify anything there. Right?
yes
leehinde And second, will this work with the private Maria instances? I'm assuming so, just set the right target info.
probably not 
I don't believe our MariaDB setup has drop-in binary compatibility with the DB store used by a private MySQL instance at WF. If you do migrate it over and it doesn't seem to work, then build a new private MariaDB instance on Opalstack and import your data into that manually.
- Edited
Two files were created at same place config.ini is: "dbname.opalmigration.sql" and " and "dbname.opalmigration-local.passwd" Can I get rid of them? (I noticed my new password in there).
Just some feedback from my side.
I had no issue with wfmigrate wordpress, it worked perfectly and quickly, around 1-2 minute.
After migration I found out that some plugins (crayon-syntax-highlighter, web4pro-about-me) are making WordPress crash. To be clear this is not problem with OpalStack, but because PHP was not updated on WebFaction (it was running depreciated version), these outdated plugins still worked, if WebFaction did update I would have same problem there.
This Wordpress site is my personal development/coder blog and I have no plans to publish more content via WordPress, WordPress is just not good option for developer/coder blog. I have a plan(but not time) to switch to static site generator. Duo to these errors I decide to switch is to static site. I have used this tool https://www.youtube.com/watch?v=UKFCWMCNWLM&ab_channel=RedServerHost. Process is done and all is working fine.
I posted this because maybe somebody is in similar situation, have WordPress that will not be updated anymore, one option is to convert it to static site.
P.S. I did kept original WordPress on OpalStack, just in case I change my mind, but it is not available via site routes.
webscience dmeehan we have not been able to reproduce the password issue that you've reported.
If you're still hitting this problem then please email support with to let us know the location of the config that you're trying to use. We'll also need your permission to actually run the migrator with that config.