The problem was resolved, there was nothing wrong with the 'settings.py', but a database field that conflicted with the previous migrations. Once I filled the field with data, the error stopped and the django site worked fully.