We are all trying to help you with by providing some small changes (remove a semicolon) and some bigger changes (try installing a fresh copy of moodle).
Thanks for posting your config.php. A small suggestion would be remove the ending "/" in line 20. I doubt this will help, but in my installs I my config.php does not have this ending "/", even though I think that it is technically fine.
On the bigger side, you never got your new install of moodle to work. So I wonder how you are really installing moodle, and if your server is fully ready to run moodle. Could be a number of things, and others here might be able to more quickly guide you.
When I install moodle from scratch, I do it in the following way. Maybe you will see something here.
1) First, I make moodle be in a folder off of my may url, such as www.mydomain.com/moodle. You appear to be making moodle be your main URL, which is no problem, but you could try an experimental install of moodle in its own folder.
2) Then, I create the database. I do this with the cPanel tools on my VPS, but one can do this at the command line. Then I use phpMyAdmin to change the collation to utf8_unicode_ci . How have you created your database, and have you changed its collation?
3) Then, I manually create my moodledata folder one level down from my "public_html" folder. If this is an experimental install, I name it something like moodledata04, just so that I don't disturb my production copy. I change its rights which a chmod 777 moodledat04 command issued via an ssh session. There are other ways of doing this. How are you doing this?
4) I prefer the tar versions of the moodle program. But the zip is find. I download the moodle program into a temporary area (a moodletmp folder), then I un-tar it with the command tar xvzf moodledata.tgz, issued from a ssh session. Then I move this to my "public_html" area with the following command "mv -i moodle ../public_html/moodle04".
5) Then I start moodle (moodle04) in my browser, the install proceeds, then you have to make sure to use the correct database and moodledata in the dialog boxes.
6) This is really step 0, I check that my server meets all of the requirements for moodle with the following a webpage called info.php that contains the line "<? phpinfo(); ?>". I check for the presence of zip, xmlrpc, soap, mysql improved, mbstring, intl, and gd. I also check my versions of php and mysql.
Well, maybe some of this will help you. But if you cannot get a fresh copy of moodle working, you will not likely get your "moved" copy of moodle working either.
Oh, here is one more step. When you do get your fresh copy of moodle working, then try moving your previous moodledata into your new copy, and your database into your new copy.