I had run the server locally using ./manage.py runserver and it threw the error on the console:
December 28, 2015 - 08:57:30 Django version 1.8.4, using settings 'jivaana.settings' Starting development server at http://0.0.0.0:8600/ Quit the server with CONTROL-C. HTTPError = 503 *[28/Dec/2015 08:57:31] "GET /catalogue/ HTTP/1.1" 500 2990* HTTPError = 503 *[28/Dec/2015 08:57:37] "GET /accounts/login/ HTTP/1.1" 500 2990* HTTPError = 503 *[28/Dec/2015 09:01:55] "GET /catalogue/ HTTP/1.1" 500 2990* *I do not have any other logs which I could share. If any more info is needed, I could try to gather.* *Thanks.* On Monday, December 28, 2015 at 3:08:01 PM UTC+5:30, monoBOT monoBOT wrote: > > Your server is not working, the first thing to do always is see what is > the error message: > > 503 Service Unavailable > > The server is currently unable to handle the request due to a temporary > overloading or maintenance of the server. The implication is that this is a > temporary condition which will be alleviated after some delay. If known, > the length of the delay MAY be indicated in a Retry-After header. If no > Retry-After is given, the client SHOULD handle the response as it would for > a 500 response. > > Note: The existence of the 503 status code does not imply that a server > must use it when becoming overloaded. Some servers may wish to simply > refuse the connection. > > When you face similar things you should test them locally (with manage.py > runserver) with the exact same configuration for django to show you the > error message. > You have not explained too much so we can not help you more. > > > 2015-12-28 8:46 GMT+00:00 Web Architect <[email protected] <javascript:>>: > >> Hi, >> >> I have set the following in settings.py for our production system: >> >> DEBUG=False >> >> ALLOWED_HOSTS = ['*'] (in fact any value is not working) >> >> The server is throwing "HTTPError = 503". >> >> There are no logs and I am clueless about the reason for the error. I >> tried searching the net and looking into DJango documents but couldn't find >> the possible reason. >> >> Django version is 1.8.3. >> >> Would really appreciate if anyone could help with the above. >> >> Thanks. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > *monoBOT* > Visite mi sitio(Visit my site): monobotsoft.es/blog/ > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/060a429d-06a1-4232-a316-b2fcfaea922f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
