Hi,

Thanks for your response.

I had run the server using runserver and it threw the same error:

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 am sorry I should have mentioned. After all the above debugging, I was 
clueless what was going wrong.*


The DEBUG and ALLOWED_HOSTS was set as per documentation. Not sure if 
anything more was needed.


Thanks.

On Monday, December 28, 2015 at 3:40:24 PM UTC+5:30, esauro wrote:
>
> Hi,
> I assume the development server is working. If that is the case it could 
> be that you have a problem with your production stack. I remember a 
> situation long time ago (like Django 1.1 or so) a project I run with apache 
> + mod_wsgi and we have a problem like this (I don't remember the error 
> code) because there were a "print" in the code.
>
> So please confirm you can use "runserver"
>     * If so, try to put more data on your production stack (web server, 
> wsgi gateway, etc.)
>     * If no you'll probably have much more data to fix the problem.
>
> Regards,
> Esau.
>
>
>
> On Mon, Dec 28, 2015 at 8:46 AM, Web Architect <pina...@gmail.com 
> <javascript:>> wrote:
>
>> 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 django-users...@googlegroups.com <javascript:>.
>> To post to this group, send email to django...@googlegroups.com 
>> <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.
>>
>
>
>
> -- 
> Esaú Rodríguez
> esa...@gmail.com <javascript:>
>

-- 
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 django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/284d41eb-fbba-469c-b9e0-148b65daf38c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to