We're going to need to see the full traceback again to help you out.
However, a 502 sounds like an error happening before the request reaches
Django. Can you check the nginx logs? They should be in
/home/%(user)s/logs/%(proj_name)s_error_nginx.log (taken from the fabfile).
--
You received
I think, problem is related to *rsync, *it's not sync any static file from
development environment to
/home/user_name/mezzanine/prooject_name/static
Ok... Fine, But then after I was checked fabfile.py and removed "/static"
from *excludeList *and this internal server error solved ! And
Yes, That was my mistake. I will take care this thing next time.
Your Replay very help full. That error is something like...
Internal Server Error: /
UncompressableFileError at /
'css/socialbutton_style.css' could not be found in the COMPRESS_ROOT
'/home/pi/mezzanine/trekmunk/static' or with
Please don't double post. Some people are subscribed to this list and will
get every email.
Have you configured email reporting for your site? That should get you a
full traceback delivered to your email, which you can then post here. This
thread describes how to configure it:
On Monday, September 26, 2016 at 12:41:35 PM UTC+5:30, shivang patel wrote:
>
> Hello
>
> I got rapidly "*Internal Server Error*" after deployed site on production
> environment.
>
> I checked everything...
>
> 1) development environment wring fine- good
> 2) no errors while *fab all - Debug
Simplifying the local_settings.py seems to have resolved this problem; I'm
using the defaults for STATIC_ROOT and STATIC_URL that are already in
settings.py, with the configuration for nginx as listed above.
Of course, now I'm getting a different error, but the problem with the
permission
I made some progress on understanding this, but haven't quite gotten past
the problem. One thing I learned was that I mixed up the use of the
STATIC_ROOT and STATIC_URL, but fixing it didn't seem to do much.
Here are what appear to be the relevant configs.
local_settings.py:
STATIC_URL =
I wonder if STATIC_ROOT is the source of your problem. Have you tried
different settings for that, including STATIC_ROOT = /static/ ? I don't
use nginx (I use Apache), but looking at your config, I wonder if the
webserver is looking for static files in a folder that Django appends with
another
I think you're probably right, Ross. I noticed that when we did some
updates to the theme locally and some static files were accidentally
missing, internally the dev server produced a 404 error as evidenced by the
server output. However, on the browser it showed up as a 500 error. I
suspect
Good thought, I had been running collectstatic as part of the fabric
deploy. This time I ran the command by itself.
It correctly copied everything into the location specified by the static
root, so it's putting them where I expected. I'm still not seeing any new
error messages in the ngnix
What happens when you run collectstatic?
If I recall correctly, one of the differences between DEBUG = False and
DEBUG = True is that the former will use static files from Mezzanine's
codebase and the latter will search for static files in your project
folders. The collectstatic command will
11 matches
Mail list logo
