Django ImproperlyConfigured The SECRET KEY setting must not be empty

Question

I am trying to set up multiple setting files  development  production      that include some base settings  Cannot succeed though  When I try to run   manage py runserver I am getting the following error    cb clime den  srv www cb     manage py runserver ImproperlyConfigured  The SECRET KEY setting must not be empty    Here is my settings module    cb clime den  srv www cb cb settings   ll total 24 -rw-rw-r--  1 clime clime 8230 Oct  2 02 56 base py -rw-rw-r--  1 clime clime  489 Oct  2 03 09 development py -rw-rw-r--  1 clime clime   24 Oct  2 02 34   init   py -rw-rw-r--  1 clime clime  471 Oct  2 02 51 production py   Base settings  contain SECRET KEY     cb clime den  srv www cb cb settings   cat base py    Django base settings for cb project   import django conf global settings as defaults  DEBUG   False TEMPLATE DEBUG   False  INTERNAL IPS     127 0 0 1     ADMINS           clime    clime7 gmail com       MANAGERS   ADMINS  DATABASES          default               ENGINE    django db backends postgresql psycopg2     Add  postgresql psycopg2    mysql    sqlite3  or  oracle            ENGINE    django db backends postgresql psycopg2            NAME    cwu                       Or path to database file if using sqlite3           USER    clime                     Not used with sqlite3           PASSWORD                          Not used with sqlite3           HOST                              Set to empty string for localhost  Not used with sqlite3           PORT                              Set to empty string for default  Not used with sqlite3             Local time zone for this installation  Choices can be found here    http   en wikipedia org wiki List of tz zones by name   although not all choices may be available on all operating systems    In a Windows environment this must be set to your system time zone  TIME ZONE    Europe Prague     Language code for this installation  All choices can be found here    http   www i18nguy com unicode language-identifiers html LANGUAGE CODE    en-us   SITE ID   1    If you set this to False  Django will make some optimizations so as not   to load the internationalization machinery  USE I18N   False    If you set this to False  Django will not format dates  numbers and   calendars according to the current locale  USE L10N   False   TODO  make this true and accustom date time input  DATE INPUT FORMATS   defaults DATE INPUT FORMATS      d  b  y     d  b   y         25 Oct 13    25 Oct  13      If you set this to False  Django will not use timezone-aware datetimes  USE TZ   True    Absolute filesystem path to the directory that will hold user-uploaded files    Example    home media media lawrence com media   MEDIA ROOT     srv www cb media     URL that handles the media served from MEDIA ROOT  Make sure to use a   trailing slash    Examples   http   media lawrence com media     http   example com media   MEDIA URL     media      Absolute path to the directory static files should be collected to    Don t put anything in this directory yourself  store your static files   in apps   static   subdirectories and in STATICFILES DIRS    Example    home media media lawrence com static   STATIC ROOT     srv www cb static     URL prefix for static files    Example   http   media lawrence com static   STATIC URL     static      Additional locations of static files STATICFILES DIRS           Put strings here  like   home html static  or  C  www django static         Always use forward slashes  even on Windows        Don t forget to use absolute paths  not relative paths       List of finder classes that know how to find static files in   various locations  STATICFILES FINDERS          django contrib staticfiles finders FileSystemFinder        django contrib staticfiles finders AppDirectoriesFinder         django contrib staticfiles finders DefaultStorageFinder        Make this unique  and don t share it with anybody  SECRET KEY    8lu 6g0lg 9z ba a ehk xt x rxgb i1 amp amp 022shmi1jcgihb      List of callables that know how to import templates from various sources  TEMPLATE LOADERS          django template loaders filesystem Loader        django template loaders app directories Loader          django template loaders eggs Loader      TEMPLATE CONTEXT PROCESSORS          django contrib auth context processors auth        django core context processors request        django core context processors debug        django core context processors i18n        django core context processors media        django core context processors static        django core context processors tz        django contrib messages context processors messages        web context inbox        web context base        web context main search        web context enums      MIDDLEWARE CLASSES          django middleware common CommonMiddleware        django contrib sessions middleware SessionMiddleware        django middleware csrf CsrfViewMiddleware        django contrib auth middleware AuthenticationMiddleware        django contrib messages middleware MessageMiddleware        watson middleware SearchContextMiddleware        debug toolbar middleware DebugToolbarMiddleware        middleware UserMemberMiddleware        middleware ProfilerMiddleware        middleware VaryOnAcceptMiddleware         Uncomment the next line for simple clickjacking protection         django middleware clickjacking XFrameOptionsMiddleware      ROOT URLCONF    cb urls     Python dotted path to the WSGI application used by Django s runserver  WSGI APPLICATION    cb wsgi application   TEMPLATE DIRS           Put strings here  like   home html django templates  or  C  www django templates         Always use forward slashes  even on Windows        Don t forget to use absolute paths  not relative paths        srv www cb web templates         srv www cb templates      INSTALLED APPS          django contrib auth        django contrib contenttypes        django contrib sessions        django contrib sites        django contrib messages        django contrib staticfiles        south        grappelli     must be before admin      django contrib admin        django contrib admindocs        endless pagination        debug toolbar        djangoratings        watson        web      AUTH USER MODEL    web User     A sample logging configuration  The only tangible logging   performed by this configuration is to send an email to   the site admins on every HTTP 500 error when DEBUG False    See http   docs djangoproject com en dev topics logging for   more details on how to customize your logging configuration  LOGGING          version   1       disable existing loggers   False       filters              require debug false                        django utils log RequireDebugFalse                        formatters              standard                  format        asctime s    levelname s    name s   lineno s    message s                datefmt      d  b  Y  H  M  S                         handlers              mail admins                  level    ERROR                filters     require debug false                 class    django utils log AdminEmailHandler                      null                  level   DEBUG                class   django utils log NullHandler                       logfile                  level   DEBUG                class   logging handlers RotatingFileHandler                filename     srv www cb logs application log                maxBytes   50000               backupCount   2               formatter    standard                       console                 level   INFO                class   logging StreamHandler                formatter    standard                         loggers              django request                  handlers     mail admins                 level    ERROR                propagate   True                      django                  handlers    console                 propagate   True               level   WARN                       django db backends                  handlers     console                 level    DEBUG                propagate   False                      web                  handlers     console    logfile                 level    DEBUG                        LOGIN URL    login  LOGOUT URL    logout    ENDLESS PAGINATION LOADING             lt img src   static web img preloader gif  alt  loading  style  margin auto   gt       ENDLESS PAGINATION LOADING            lt div class  spinner small  style  margin auto  gt           lt div class  block 1 spinner block small  gt  lt  div gt           lt div class  block 2 spinner block small  gt  lt  div gt           lt div class  block 3 spinner block small  gt  lt  div gt       lt  div gt       DEBUG TOOLBAR CONFIG          INTERCEPT REDIRECTS   False     import django template loader django template loader add to builtins  web templatetags cb tags   django template loader add to builtins  web templatetags tag library    WATSON POSTGRESQL SEARCH CONFIG    public english nostop    One of the setting files    cb clime den  srv www cb cb settings   cat development py  from base import    DEBUG   True TEMPLATE DEBUG   True  ALLOWED HOSTS     127 0 0 1    31 31 78 149    DATABASES          default              ENGINE    django db backends postgresql psycopg2            NAME    cwu            USER    clime            PASSWORD                HOST                PORT                MEDIA ROOT     srv www cb media    STATIC ROOT     srv www cb static    TEMPLATE DIRS           srv www cb web templates         srv www cb templates       Code in manage py    cb clime den  srv www cb   cat manage py     usr bin env python import os import sys  if   name         main         os environ setdefault  DJANGO SETTINGS MODULE    cb settings development        from django core management import execute from command line      execute from command line sys argv    If I add from base import   into  srv www cb cb settings   init   py  which is otherwise empty   it magically starts to work but I don t understand why  Anyone could explain to me what s going on here  It must be some python module magic   EDIT  Everything also starts to work if I remove this line from base py  django template loader add to builtins  web templatetags cb tags     If I remove this line from web templatetags cb tags  it also starts to work   from endless pagination templatetags import endless   I guess it is because  in the end  it leads to   from django conf import settings PER PAGE   getattr settings   ENDLESS PAGINATION PER PAGE   10    So it creates some weird circular stuff and game over

User · Answer

I had the same problem with Celery  My setting py before   SECRET KEY   os environ get  DJANGO SECRET KEY     after   SECRET KEY   os environ get  DJANGO SECRET KEY    lt YOUR developing key gt     If the environment variables are not defined then  SECRET KEY   YOUR developing key

User · Answer

I think that it is the Environment error you should try setting   DJANGO SETTINGS MODULE  correctly settings

User · Answer

I had the same error and it turned out to be a circular dependency between a module or class loaded by the settings and the settings module itself  In my case it was a middleware class which was named in the settings which itself tried to load the settings

User · Answer

The issue for me was calling get text noop in the LANGUAGES iterable   Changing  LANGUAGES           en-gb   get text noop  British English           fr   get text noop  French         to  from django utils translation import gettext lazy as    LANGUAGES           en-gb      British English           fr      French         in the base settings file resolved the ImproperlyConfigured  The SECRET KEY setting must not be empty exception

User · Answer

try import django then run django setup   after the secret key definition  like so  SECRET KEY    it5bs  q6toz-1gwf  j f9 rd8  -0nx p-2 egr y1o51 45XXCV  django setup

User · Answer

In the init py of the settings directory write the correct import  like   from Project settings base import     No need to change wsgi py or manage py

User · Answer

My Mac OS didn t like that it didn t find the env variable set in the settings file     SECURITY WARNING  keep the secret key used in production secret  SECRET KEY   os environ get  MY SERVER ENV VAR NAME     but after adding the env var to my local Mac OS dev environment  the error disappeared   export MY SERVER ENV VAR NAME   fake dev security key that is longer than 50 characters     In my case  I also needed to add the --settings param   python3 manage py check --deploy --settings myappname settings production   where production py is a file containing production specific settings inside a settings folder

User · Answer

To throw another potential solution into the mix  I had a settings folder as well as a settings py in my project dir   I was switching back from environment-based settings files to one file  I have since reconsidered    Python was getting confused about whether I wanted to import project settings py or project settings   init   py  I removed the settings dir and everything now works fine

User · Answer

It starts working because on the base py you have all information needed in a basic settings file  You need the line   SECRET KEY    8lu 6g0lg 9z ba a ehk xt x rxgb i1 amp amp 022shmi1jcgihb     So it works and when you do from base import    it imports SECRET KEY into your development py   You should always import basic settings before doing any custom settings     EDIT  Also  when django imports development from your package  it initializes all variables inside base since you defined from base import   inside   init   py

User · Answer

In my case  while setting up a Github action I just forgot to add the env variables to the yml file   jobs    build      env       VAR1  1      VAR2  5

User · Answer

Remove  pyc files  Ubuntu terminal command for deleting  pyc   find   -name    pyc  -exec rm -rf        I have got same error when I did python manage py runserver  It was because  pyc file  I deleted  pyc file from project directory then it was working

User · Answer

I just wanted to add that I got this error when my database name was spelled wrong in my settings py file so the DB couldn t be created

User · Answer

I hadn t specified the settings file   python manage py runserver --settings my project settings develop

User · Answer

For anyone using Wing IDE  set the DJANGO SETTINGS MODULE in your project properties to DJANGO SETTINGS MODULE   DJANGO SITENAME  config settings development You will find the settings under  Project -- gt  Project Properties and set the value in the field Environment

User · Answer

I solved the above problem by commenting the line in my settings py  SECRET KEY os environ get  SECRET KEY     SECRET KEY declared in my    bashrc file for linux Ubuntu users   For development purpose on my localmachine I did not use evironmnet variable  SECRET KEY     i9b4aes h1 m3h 8jh duxrdh 4pu8-q5vkba2yf ptd1lev     above line didn t give the error

User · Answer

I solved this problem occurring on OS X with Django both 1 5 and 1 6 by deactivating all active sessions to virtualenv and starting it again

User · Answer

I had the same error with python manage py runserver   For me  it turned out that it was because of a stale compiled binary   pyc  file  After deleting all such files in my project  server started running again      So if you get this error  out of nowhere  i e without making any change seemingly-related to django-settings  this could be a good first measure

User · Answer

In my case the problem was - I had my app folder and settings py in it  Then I decided to make Settings folder inside app folder - and that made a collision with settings py  Just renamed that Settings folder - and everything worked

User · Answer

Let me share m interesting solution  I put the SECRET KEY    quot     amp      quot  in settings packages init py file and the error disappeared  it s actually a loading problem  Hope this quick workaround is useful for some of you

User · Answer

I solved this problem on 1 8 4 by fixing the TEMPLATES settings which had a typo  removing TEMPLATES  debug   solved it   Go over the settings that you have changed recently  make sure all keys are by-the-book

User · Answer

For anyone using PyCharm  the green  Run selected configuration  button would produce this error  yet running the following works   py manage py runserver 127 0 0 1 8000 --settings app name settings development  To fix this you need to edit the configuration s environment variables  To do this click the  Select run debug configuration  drop-down menu to the left of the green run button and then click on  edit configuration   Under the  environment  tab change the environment variable DJANGO SETTINGS MODULE to app name settings development

User · Answer

I ran into the same problem after restructuring the settings as per the instructions from Daniel Greenfield s book Two scoops of Django   I resolved the issue by setting   os environ setdefault  DJANGO SETTINGS MODULE    project name settings local     in manage py and wsgi py   Update   In the above solution  local is the file name  settings local py  inside my settings folder  which holds the settings for my local environment   Another way to resolve this issue is to keep all your common settings inside settings base py and then create 3 separate settings files for your production  staging and dev environments   Your settings folder will look like   settings        init   py     base py     local py     prod py     stage py   and keep the following code in your settings   init   py  from  base import    env name   os getenv  ENV NAME    local    if env name     prod       from  prod import   elif env name     stage       from  stage import   else      from  local import

User · Answer

I came here looking for answer as I was facing the same issues  none of the answers here worked for me  Then after searching in other websites i stumbled upon this simple fix  It worked for me wsgi py os environ setdefault  DJANGO SETTINGS MODULE    yourProject settings    to os environ setdefault  DJANGO SETTINGS MODULE    yourProject settings dev

User · Answer

I solved this problem by removing the spaces around equal signs     in my  env file

User · Answer

In my case  it was because I was trying to setup django-environ and I missed an important step   Note  In the instructions below  env example and  env should be saved in the same folder as settings py  I incorrectly assumed that  env belonged in the root of my project  Moving it to the same folder as settings py fixed the problem  This error message in the Python console was the clue that set me on the right path  Warning   Users allen PycharmProjects myapp myapp  env doesn t exist - if you re not configuring your environment separately  create one

User · Answer

In my case  after a long search I found that PyCharm in your Django settings  Settings   Languages  amp  Frameworks   Django  had the configuration file field undefined  You should make this field point to your project s settings file  Then  you must open the Run   Debug settings and remove the environment variable DJANGO SETTINGS MODULE   existing path   This happens because the Django plugin in PyCharm forces the configuration of the framework  So there is no point in configuring any os environ setdefault  DJANGO SETTINGS MODULE    myapp settings

User · Answer

Import base py in   init   py  alone  make sure you won t repeat the same configuration again   set environment variable SET DJANGO DEVELOPMENT  dev  settings      init   py   base py   local py   production py   In    init   py  from  base import   if os environ get  DJANGO DEVELOPMENT     prod      from  production import   else     from  local import     In base py configured the global configurations  except for Database  like  SECRET KEY  ALLOWED HOSTS INSTALLED APPS MIDDLEWARE    etc       In local py  DATABASES      default          ENGINE    django db backends postgresql psycopg2        NAME    database        USER    postgres        PASSWORD    password        HOST    localhost        PORT    5432

User · Answer

The reason why there are so many different answers is because the exception probably doesn t have anything to do with the SECRET KEY  It is probably an earlier exception that is being swallowed   Turn on debugging using DEBUG True to see the real exception

[python] Django: ImproperlyConfigured: The SECRET_KEY setting must not be empty

Examples related to python

Examples related to django

Examples related to settings