Editing Running a Django Application on IIS (section)

=== Testing and troubleshooting ===

After the configuration, the website should be available through IIS. If this is not the case, you will probably get a `500` Error:

[[File:500_error.png]]

The first thing to do is to check that the website is available outside of IIS by running it with the command:

<syntaxhighlight lang="dos">
python manage.py runserver 0.0.0.0:8000
</syntaxhighlight>

And accessing it on `http://localhost:8000`. If the application works as a standalone Django application, the most common cause of error is a misconfiguration of either the FastCGI application or the root `web.config` file. You need to be sure that the The `scriptProcessor` attribute of the `web.config` matches `Full Path` and the `Arguments` of the FastCGI application.

To troubleshoot further, the `fcgi.py` command provides several settings to be put in the `settings.py` file : `FCGI_LOG` (default `False`), when `True`, instructs the command to create a log file in the path pointed by `FCGI_LOG_PATH`. If `FCGI_LOG_PATH` is not defined, the log file will be created in the project root directory. The file name name pattern of the log file will be `fcgi_AAMMDD_HHMMSS_XXXX.log`, in which `AAMMDD` is the date, `HHMMSS` the time and `XXXX` the FastCGI application process number. If `DEBUG` is set to `True` in the settings, the log file will contain the Django debug logs. The `FCGI_DEBUG` setting (default `False`), when set to `True`, will output in the log file information about the FCGI protocol transfers between IIS and the Django application.