Problems while migrating drupal website from localhost to server I am trying to migrate my Drupal website from localhost to server, but I am having some problems. I tried many guides from Google, but with no luck.

What I did:

First I did a fresh drupal installation on server

Once installation was complete I edited the .htaccess file as 

RewriteBase /site-name


Then I used mysqldump to dump my database from localhost to server I found that I had total 126 tables in localhost while in server I had 128 tables

Then I copied my complete "sites" directory from localhost to server

My problem:

Now when I enter www.mysite.com/site-name I get proper home page of my website but if I go to any other link such as www.mysite.com/site-name/user it is not able to open the page but if I enter www.mysite.com/?q=user then it works perfectly and this happens for all pages such as /content, /config etc.

What should I do to solve this issue? I think it is a problem of clean-urls So I went to configuration but it said clean URL enabled but test failed!

I need to make website live by tomorrow so need your help!

Note: I am using ubuntu on localhost as well as server 

Thanks!
To avoid requiring ?q=user or ?q=some/page/path you should assure ModRewrite is enabled on your Apache webserver. If you're on shared hosting you made need to ask your host provider to enable this module of Apache.
Moving a Drupal site is essentially moving all the PHP + MySQL data from 1 computer to another. Pick you're tools: mysqldump + zip, rsync, scp, ftp ... Drush whatever ... but the procedure is essentially the same -- move everything in it's entirety.


Why you have 2 less tables between your Drupal installs is unfortunately simply bad project management on your behalf -- good luck tracking down the differences.

Comparing drush pm-list between the 2 Drupal installs should help to find any modules on 1 system and not on the other. I like using drush archive-dump and drush archive-restore to move Drupal sites around -- but under your time constraint I recommend using SQL migration tools and code migration tools your comfortable and most familiar with.