Gadgetroid

Recheck that you did not delete your config file during the upgrade.
Clear your browser – retry,
Check if you have any caching plugins enabled, disable them and retry.
Disable all plugins enabled and retry.
With plugins disabled switch to default wordpress theme then retry.

Just recheck your config again paying attention to the password. That should match the one you choose for the wordpress database. Then check the usual – file permissions – make a dummy connection file and see if you can connect to the database using the details you are using.

Can see that you are up and running ??

Its a parser error

“Basically this error arises if there is a whitespace before an XML declaration”

The blank line error means that the code has blank lines in it,,,,,

If you can access your database you will find that maybe your ip address is in the list of blocked ip addresses in your security plugin database tables example “wp_sp-locks”. Use “whois.com” to find your home ip address – then look for the ip address in your database and remove it. Some security plugins add the ip address to the .htaccess as well depending on the permissions they’ve been granted.

WordPress provides no rollback for plugin updates. If you cannot access the backend try deactivating all plugins then reactivating them one by till find the conflict, then move on to the theme and do the same.

You can reset your password through sql if you have access to that.

From experience it looks like some security feature of a plugin doing its thing and renaming the database tables. I had to rebuild the site when that happened. What you want to find out is if there is a difference in those tables. If its well written you will find that the original wp- tables or the one with the latest date wp_users_20121214_020503 -….wp_users_20141109_014715 will have the most upto date data. Then its easy coz you can delete everything else and go with the latest data. If there is differences you may need to spend some time in the backend merging that data into one again. After all these is done check how whatever that is causing it is configured. That kind of setting looks like for a very large organisation who have people in the backend full time. Have fun ??

Delete the plugin from the backend and reinstall the plugin. Check out this post

Have a look at your config file although you have wordpress files on that server. By going to https://chscourier.com/readme.html we know there is an instal there. If your config file check you have the std wordpress htaccess in your root. Have a read of that readme file on your server and make sure everything is ok.

Rename your plugins folder to something else like example “plugins.old” then try to see if you can access your wordpress. If you can access the site reactivate the plugins one by one.
Better still if they are generic plugins with no effect on the site create a new plugins folder with necessary permissions and delete the delete the old plugins folder. Re-download all plugins a fresh if you didn’t get any errors. Especially if you have have an old site and have powerful plugins like jetpack, yoast seo, total cache, any security or redirection.

Most of these plugins have or are developing at a very high pace so sometimes even a few months without updating wordpress and you end more than 4 versions behind. I say this because, I have seen some leftover files from an old instal in a newly updated plugin probably caused by permissions problems. They are usually security risks. Be quick before hackers put through enough content about viagra in your sql like they did to me.

Use phpmyadmin for easier interface with your database – then look at your “siteurl” and “home” option values in the table “wp_options”. The last time it happened to me I remember that although I had these two values correct, the “upload_url_path” in “options” and also all my “guid” in the “wp-posts” values were all incorrect.

If all these are ok recheck your config file and .htaccess file then how you have declared this subdomain to your server.

If this is localhost, depending on your server set-up you may have to enable the sites and configure them in your LAMP/MAMP/XAMP setup.

@ ict 2conserve – I can see you solved it ?? – happy blogging

Remove or edit your ip address and replace it with xxx.xxx.xxx.xx. At the moment you are revealing your real ip and the configuration profile of your wordpress installation. Try and give the bad guys more questions to answer.

As for “The database I created is at; xxx.xxx.xxx.xx How do I change that?” – you will need to access your wordpress files and look for a file called wp-config.php and make changes there. Do you have one click installation on hosting account?.

It maybe a server instal problem that error “another native apache is running on my machine.” does not sound good. You need get to get over that before you get to wordpress. What operating system are you using?.