HOWTO migrate stuff automatically from WebFaction!

sean

gundlach sounds like you have pre-existing app in the way and it's not being deleted automatically.

I'll report the bug but in the meantime please delete your existing nl_nathanmlong_com symlink app and try it again.

Be sure to completely delete the app: https://help.opalstack.com/article/47/managing-applications#deleting-an-application

gundlach

sean FYI, that error appeared the first time I ran the wfmigrate script with an empty /home/nathan/apps folder.

I hadn't noticed the delete-now trash icon; thanks! Maybe when the user types "I confirm" it could bring up a flash helping us discover that option.

gundlach

sean Here's logs repro'ing the error. [snipped for brevity] Let me know if you'd like DEBUG level.

sean

gundlach ok, I wasn't correct earlier.

What's happening is that you're trying to make a new symlink app pointing to a nonexistent directory while also using the --rsync option.

If you're going to use the rsync option, then the symlink target needs to exist so that rsync can copy the files there.

kurt

sean Thanks for adding all of the new migrators. I will be trying a number of the new ones out.

Unfortunately, domain, the first I tried, is not working yet for me.

At the beginning of the logs, I see a ton of DEBUG lines and 200 status codes - no warnings, errors or anything that looks problematic.

Then I see:

DEBUG : performing POST domain/add/ with [JSON array with ~153 domain name objects]
DEBUG : Starting new HTTPS connection (1): my.opalstack.com:443
DEBUG : https://my.opalstack.com:443 "POST /api/v0/domain/add/ HTTP/1.1" 400 553
DEBUG : [array with ~150 empty objects, interspersed by 3 of this object: {"name":["Invalid domain name."]}]

I'm reasonably sure all of my wf domain names are valid, so it's unclear what's up here.

sean

kurt please email support to let us know the domain name and we'll look into it.

ericxob

WordPress in subdirectory... not working.

I managed to get the wfmigrate app working and it appears the apps, sites, databases, domains have been copied and installed at Opalstack. Totally fabulous! Thanks a bunch!! But a small problem...

Using a subdomain and after flushing DNS caches, I am able to use a web browser to connect to the top level of the site. (I put a simple text file there so I could confirm I was looking at the site as being served from Opalstack.)

My WordPress installation is in a subdirectory and does not load when I enter that URL (like "myspiffydomain.com/wp"). A test file in the subdirectory (like "myspiffydomain.com/wp/hellomars.txt") will display in a web browser.

My guess is that the problem is some sort of configuration error with WordPress. I have looked in wp-config.php and did not immediately see anything that might help.

Ideas?

sean

ericxob Did you migrate as Nginx+FPM or Apache? At the moment I don't think the Nginx version can serve a WP app from a subdirectory.

ericxob

sean Umm... I can't tell any longer what served this site, but another at WebFaction is being served by nginx. At Opalstack, the site I moved is being served by Nginx. (By the way, I don't know what "+FPM" means."

At WebFaction, app info for the site says "This application is served by a shared Apache web server instance." But for a different, working, site at WP, the app says the same, but the HTTP headers say "server: nginx." Maybe WP changed server engines and didn't update the text in the app info.

Not sure what piece of things you may be talking about when you write "I don't think the Nginx version can serve a WP app from a subdirectory." A limitation in the wfmigrate script? A limitation with the current configuration of Nginx at Opalstack? ...?

This is not a critical site, so I have time to fuss with things at Opalstack.

Can I fix things here "by hand" using the existing db and files? Can I somehow "switch" to have Apache serve this app?

I notice that app info has "Let our control panel manage WordPress Site URL and Home URL?" as activated.

Can I migrate again but somehow specify moving to a Apache server instead?

Thanks!

wil

odhiambo Hello, im facing a problem, it says .../Maildir doesnt exist but i have double check the path to the Maildir and it exists in webfactions account. What you think it could be?

sean

wil email support with the details please.

odhiambo

wil Sorry just seeing this today. However for those still moving out of webfaction...what I did is to copy the 'wf_archive_delivery' folder that they place in your root (at WF) to your root in opalstack. You then run the rest of the 'email-data' migrator as provided in the instructions here.

sean

ericxob Umm... I can't tell any longer what served this site, but another at WebFaction is being served by nginx. At Opalstack, the site I moved is being served by Nginx. (By the way, I don't know what "+FPM" means."

You might be seeing Nginx in your headers because all apps are proxied behind our front end Nginx.

"FPM" refers to the PHP fast process manager, it's a way of serving PHP from a persistent pool of processes instead of an individual process for every request.

ericxob Not sure what piece of things you may be talking about when you write "I don't think the Nginx version can serve a WP app from a subdirectory." A limitation in the wfmigrate script? A limitation with the current configuration of Nginx at Opalstack? ...?

That's a limitation of the Nginx+FPM config at Opalstack right now.

ericxob Can I fix things here "by hand" using the existing db and files? Can I somehow "switch" to have Apache serve this app?

Yes, email support with the app details and we can change the app type for you.

ericxob Can I migrate again but somehow specify moving to a Apache server instead?

Sure, just set deploy_type = Apache-CGI in your migration config.

ericxob

sean Ah! "Fast Process Manager!" Of course. 😉

OK, I missed the existence of "deploy_type." Maybe, against your advice, I was using an older version of the WordPress config.ini. So I edited mine to add "deploy_type = Apache-CGI" in the [php] section and ran wfmigrate against the wordpress config file again. Simulate warned me that the App, MariaDB and Site would be deleted.

I have not done anything with them, so that is OK. I then actually ran the migration and...

I have the same behavior: a text file in the /wp directory will display in a browser, but the WordPress site does not. Just an empty page.

I thought perhaps the MariaDB password might not be matching, but the one shown in Notifications matches the one I see in the wp-config.php file.

I had commands in a .htaccess file that specified to use a old version of php. I realized this when my expected site displayed the test of index.php rather than my WordPress site. I renamed the .htaccess file and now I just get a blank page, which is interesting.

Do you have an ideas for things I can do at my end?

Thanks as always!

sean

ericxob please email support so that we can look into it.

ericxob

sean OK, I'll send an email... I'm getting pretty verbose here. 😉

Thank you!

For others looking for clues... After I remembered there was such thing, I activated php error display by editing .htaccess. After doing that and reloading my site I got no PHP error but I did get a visible message! Eureka! I saw "500 Internal Server Error" And "The server encountered an internal error or misconfiguration and was unable to complete your request." ...

Ah Hah! Reminds me there are things such as log files. I found log files at <sshusername>/logs/). Inspecting them I saw numerous "connection refused" errors. Progress!

orchardandy

I was able to migrate 4 data-rich Wordpress installations and four domains very smoothly. Thank you for providing a great tool and a great avenue to jump ship!

I do really hope that Opalstack is able to stay solvent and independent for decades to come, as Webfaction/GoDaddy isn't even the first host that's screwed me over...

In case this helps anyone, I will note that my first Wordpress migration actually returned a 500 error on Opalstack servers, somewhat disheartening. Looking at the server logs, this was due to a function call in a plugin that was deprecated in PHP7. I changed the application's PHP version to 5 through the Opalstack panel, and everything ran smoothly, easy peasy.

You can check what platform your apps were previously running on in the Webfaction applications panel, if you have compatibility problems like this. I have since noted that there is also an option in the Opalstack migrator configuration to set versions from the outset.

wil

odhiambo thank you, i try this yesterday and it works! That was my error.

will13

I'm getting a db error when running the simulation...
"mysqldump: Got error: 2005: Unknown MySQL server host 'localhost:3306' (2) when trying to connect"

sean

will13 I think if you change localhost:3306 to localhost in your WP config at WF prior to running the migration you should be OK.

« Previous Page Next Page »