is it possible that my heartache over the last 14 hours is not my fault?
I migrated a server from Google Cloud Compute to Vultr, used the backup/restore virtual server option from inside virtualmin to make the migration. I was unable to perform one single migration and had to resort to individual virtual servers (1 at a time).
i thought all was going well and i completed the move of a couple of virtual servers until i migrated what was originally, the first virtual server in the list on my old system. As soon as this one was restored onto my new server, the entire server shit itself. I spent the next 2 hours tearing my hair out trying to get Webmin functioning again…eventually succeeding. Then once this was sorted, i was unable to browse any websites except the very first one i migrated on my new server.
I decided to delete and then attempted to create new virtual servers…forwarded the Registrar A records to these virtual servers one at a time…absolutely no one home.
It was as if apache had no idea how to resolve the websites internally from the vhosts file. I checked this file and all of the .com’s i had setup were there in said file.
Now i deleted the entire Vultr instance and started over.
I setup a debian sudo user who is part of the sudoer group (should i have used the unix root instead?)
I setup the virtual servers (this time not migrating) and ran the install script for fresh Wordpress on each.
As soon as i attempt to follow the virtualmin instructions saying to navigate to http://mydomain.com/wordpress/wp-admin/install.php i get a database connection error.
I checked my wp-config.php file and it is obvious that the script is not updating the wordpress /wp.config file with the virtual server details at all WTF? The user, password, and database information is blank (ie wordpress.org default ones “database_name_here”, “username_here”, password_here"). The script is supposed to update these to match my newly created virtual server! It seems that the virtual server user doesnt have the required permissions to edit the wp-config file and or write to the database itself for that matter?
I have checked the permissions on my virtual server…all files are virtual server : virtual server, and permissions set to 750 and 644
I dont know if my problem is similar?
Are these problems all related?
I am about to blow away another 3 hours worth the work and start over again. I will create another new instance from which i can compare in order to try to figure out what is going wrong. i am going to not change a damned thing (leaving absolutelly all defaults in place and see what happens).
I will report back in a few hours…it will either be a positive post here…or a “blood curdling war cry”!