[GH-ISSUE #283] Server Error (500) #213

New issue

Closed

opened 2026-02-25 23:41:37 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:41:37 +03:00

Owner

Originally created by @mzch on GitHub (Sep 3, 2019).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/283

Hi,

in local_settings.py when set DEBUG = False, healthchecks works well, but when DEBUG = True, only the error message shows 'Server Error (500). How can I fix this issue?

HealthCheck: 1.9.0
Python: 3.7.4
MariaDB: 10.3.15-MariaDB
OS: Debian GNU/Linux 10 (Buster)

Originally created by @mzch on GitHub (Sep 3, 2019). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/283 Hi, in local_settings.py when set DEBUG = False, healthchecks works well, but when DEBUG = True, only the error message shows 'Server Error (500). How can I fix this issue? HealthCheck: 1.9.0 Python: 3.7.4 MariaDB: 10.3.15-MariaDB OS: Debian GNU/Linux 10 (Buster)

kerem closed this issue

2026-02-25 23:41:37 +03:00

kerem commented

2026-02-25 23:41:38 +03:00

Author

Owner

@cuu508 commented on GitHub (Sep 3, 2019):

To diagnose this, we need to know the error details. When DEBUG is False, Django sends tracebacks to email addresses listed in the ADMINS setting. Try putting your name and address there and see if you get an email with more details. You may also need to fix the SERVER_EMAIL setting.

Alternatively, you can tweak Django's logging to print error details to console even with DEBUG=False. Details here: https://www.agiliq.com/blog/2017/12/configure-django-log-exceptions-production/

@cuu508 commented on GitHub (Sep 3, 2019): To diagnose this, we need to know the error details. When DEBUG is False, Django sends tracebacks to email addresses listed in the [ADMINS](https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-ADMINS) setting. Try putting your name and address there and see if you get an email with more details. You may also need to fix the [SERVER_EMAIL](https://docs.djangoproject.com/en/2.2/ref/settings/#server-email) setting. Alternatively, you can tweak Django's logging to print error details to console even with DEBUG=False. Details here: https://www.agiliq.com/blog/2017/12/configure-django-log-exceptions-production/

kerem commented

2026-02-25 23:41:38 +03:00

Author

Owner

@mzch commented on GitHub (Sep 4, 2019):

Thanks for your reply. I added ADMIN to local_settings and the error report said 'You may need python manage.py compress'. When I did it, everything went well. :) Please add the step to README.md.

@mzch commented on GitHub (Sep 4, 2019): Thanks for your reply. I added ADMIN to local_settings and the error report said 'You may need python manage.py compress'. When I did it, everything went well. :) Please add the step to README.md.

kerem commented

2026-02-25 23:41:38 +03:00

Author

Owner

@cuu508 commented on GitHub (Sep 4, 2019):

Thanks, good idea – I've updated README with a "Running in Production" section. Some parts of it probably need to be expanded, but it's a start.

@cuu508 commented on GitHub (Sep 4, 2019): Thanks, good idea – I've updated README with a "Running in Production" section. Some parts of it probably need to be expanded, but it's a start.

kerem commented

2026-02-25 23:41:38 +03:00

Author

Owner

@mzch commented on GitHub (Sep 4, 2019):

Great! Thanks, @cuu508 !

@mzch commented on GitHub (Sep 4, 2019): Great! Thanks, @cuu508 !