[Answer]-Django south : "No connection could be made because the target machine actively refused it."

The table south_migrationhistory doesn’t seem to exist. You need to run manage.py syncdb once before you can use south migrations.

south_migrationhistory persists, for each app, which migrations are already applied. If you convert an existing app to south, the initial migration should match the current schema state, e.g. you should not do any model changes before creating the initial migration. Then, to make the south_migrationhistory table match the schema state, you can ‘fake-apply’ the initial migration:

manage.py migrate appname 0001 --fake

that will create the record for the initial migration in the south_migrationhistory table without actually attempting to do any schema changes. Now you can apply the rest of your migrations:

manage.py migrate appname