On Thu, Feb 1, 2024 at 2:03 PM J Carter wrote:
>
> Hello,
>
> On Thu, 1 Feb 2024 12:28:40 -0500
> Larry Martell wrote:
>
> > On Thu, Feb 1, 2024 at 11:57 AM Sergey A. Osokin
> > wrote:
> > >
> > > Hi Larry,
> > >
> > > On Thu,
On Fri, Feb 2, 2024 at 8:43 PM Maxim Dounin wrote:
>
> Hello!
>
> On Fri, Feb 02, 2024 at 01:07:40PM -0500, Larry Martell wrote:
>
> > I built nginx from source and it fails to start with:
> >
> > 2024/02/02 13:00:59 [emerg] 1961284#1961284: dlopen()
> > &
I built nginx from source and it fails to start with:
2024/02/02 13:00:59 [emerg] 1961284#1961284: dlopen()
"/usr/modules/ndk_http_module.so" failed
(/usr/modules/ndk_http_module.so: cannot open shared object file: No
such file or directory) in
/etc/nginx/modules-enabled/10-mod-http-ndk.conf:1
-V
On Thu, Feb 1, 2024 at 1:28 PM Sergey A. Osokin wrote:
>
> On Thu, Feb 01, 2024 at 01:10:35PM -0500, Larry Martell wrote:
> >
> > I had already done all that. (Those instructors are the same as the
> > page I initially referenced,
> > https://docs.nginx.com/ngin
On Thu, Feb 1, 2024 at 12:48 PM Sergey A. Osokin wrote:
>
> Hi Larry,
>
> On Thu, Feb 01, 2024 at 12:28:40PM -0500, Larry Martell wrote:
> >
> > I was able to install nginx-module-image-filter with apt, but
> > http-xslt-filter, mail, stream all fail with the s
On Thu, Feb 1, 2024 at 11:57 AM Sergey A. Osokin wrote:
>
> Hi Larry,
>
> On Thu, Feb 01, 2024 at 11:34:08AM -0500, Larry Martell wrote:
> > We run Ubuntu 20.04, which has nginx 1.18. I was asked to upgrade it
> > to 1.25.3, which I did following the instructions here:
&g
We run Ubuntu 20.04, which has nginx 1.18. I was asked to upgrade it
to 1.25.3, which I did following the instructions here:
https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/.
We had 6 modules installed (http-ndk, http-image-filter, http-lua,
http-xslt-filter,
Is there a way to have nginx log the response body?
___
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
On Tue, May 12, 2020 at 12:55 PM Norman Gray wrote:
>
>
> Larry, hello.
>
> On 12 May 2020, at 16:33, Larry Martell wrote:
>
> > There can be cases when a
> > request from a user does not come back from the db for 15-20 minutes.
> > This is expected as it
On Tue, May 12, 2020 at 11:33 AM Larry Martell wrote:
>
> I have a django app using nginx and uwsgi. There can be cases when a
> request from a user does not come back from the db for 15-20 minutes.
> This is expected as it's calling a stored proc that does a lot and
> thi
I have a django app using nginx and uwsgi. There can be cases when a
request from a user does not come back from the db for 15-20 minutes.
This is expected as it's calling a stored proc that does a lot and
this is an internal app. Issue is that after some amount of time I get
a 504 timeout error -
On Wed, Feb 26, 2020 at 6:39 PM Francis Daly wrote:
>
> On Wed, Feb 26, 2020 at 05:55:02PM -0500, Larry Martell wrote:
>
> Hi there,
>
> > upstream django {
> > server unix:/run/daphne/devAppReporting.sock;
> > }
> >
> > server {
&g
I've posted this to the django mailing list and to stack overflow,
with no replies so trying here.
I am trying to deploy a django app that uses channels and websockets,
with nginx and daphne.
When I was using uwsgi, here was my nginx file:
upstream django {
server unix:/run/uwsgi/devAppR
t
> have different configuration?
>
>
> > On Jan 5, 2019, at 13:01, Larry Martell wrote:
> >
> > I am having an odd interment django problem. I have an app which is
> > deployed at 30 different sites, some with apache and wsgi and some
> > with nginx a
I am having an odd interment django problem. I have an app which is
deployed at 30 different sites, some with apache and wsgi and some
with nginx and uwsgi. At only the nginx/uwsgi sites and only
intermittently, users will get the error No module named
context_processors.
I am only posting it here
I found that copying the static files to /var/run (and changing the
nginx config) fixed this.
On Sun, Aug 20, 2017 at 9:52 AM, Larry Martell wrote:
> I changed the socket to be in /var/run and that fixed the issue. But
> now I am getting a 403 on all the static files, e.g:
>
> 2017
, request: "GET
/static/scripts/bootstrap.min.js HTTP/1.1", host: "localhost:9003",
referrer: "http://localhost:9003/";
Any ideas on that?
On Sat, Aug 19, 2017 at 7:33 PM, Larry Martell wrote:
> Inside the docker container the dir is /opt/django/CAPgraph/.
>
>
t type of file.
>
> Place the socket somewhere else (like /var/run/aoo.sock).
>
> Cheers,
>
> Guilherme Capilé
>
> On Sat, Aug 19, 2017 at 4:59 PM, Larry Martell
> wrote:
>> Don't ask why, but on my mac I am running Windows Server 2016 in
>> VMware.
Don't ask why, but on my mac I am running Windows Server 2016 in
VMware. In there I am running Ubuntu in vagrant/Virtual Box. In there
I am trying to run a django app in a docker container with
nginx/uwsgi.
The socket is being created, but then when I try and connect to the
site it fails with this
On Fri, Apr 7, 2017 at 2:53 PM, Larry Martell wrote:
> I have a django app that I serve with nginx. Some requests that the
> app receives start python threads that are not complete when the
> request returns a response to the client. When I run with the django
> devel server the thre
I have a django app that I serve with nginx. Some requests that the
app receives start python threads that are not complete when the
request returns a response to the client. When I run with the django
devel server the threads continue to run to completion. But when I run
with nginx it seems that t
right? But I get the 504 response before 10 minutes
have passed since the request is sent. Why is that?
>
> On Tue, Aug 9, 2016 at 11:09 PM, Larry Martell
> wrote:
>>
>> I just set up a django site with nginx and uWSGI. Some pages I go to
>> work fine, but other fail with a
I just set up a django site with nginx and uWSGI. Some pages I go to
work fine, but other fail with a 504 Gateway Time-out. I used to
serve this site with apache and wsgi and these same pages worked fine.
This is what I see in the nginx error log:
2016/08/09 16:40:19 [error] 17345#0: *1 upstream
On Fri, Jul 29, 2016 at 3:58 AM, Francis Daly wrote:
> On Thu, Jul 28, 2016 at 10:13:30PM -0400, Larry Martell wrote:
> Does "iptables -L -v -n" show anything interesting? You said that you
> disabled the firewall, so it probably is empty.
I am on Centos7 which uses firewal
On Thu, Jul 28, 2016 at 3:52 PM, Francis Daly wrote:
> On Thu, Jul 28, 2016 at 03:01:17PM -0400, Larry Martell wrote:
>
> Hi there,
>
>> netstat shows that nginx is listening on port 80:
>>
>> tcp0 0 0.0.0.0:80 0.0.0.0:*
>> LISTEN
On Thursday, July 28, 2016, Pratyush Kumar wrote:
> Can you please share the address which you are using in browser.
>
> According to the config which you shared, you will get a response only if
> you use localhost as URL in browser
>
I am connecting from the outside to the public IP of the mach
Trying to set up nginx and uwsgi for django. Following the directions here:
https://www.digitalocean.com/community/tutorials/how-to-serve-django-applications-with-uwsgi-and-nginx-on-centos-7
netstat shows that nginx is listening on port 80:
tcp0 0 0.0.0.0:80 0.0.0.0:*
L
On Tue, May 31, 2016 at 7:06 PM, Francis Daly wrote:
> On Tue, May 31, 2016 at 04:48:19PM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 4:19 PM, Francis Daly wrote:
>> > On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
>
> Hi there,
>
>>
On Tue, May 31, 2016 at 4:19 PM, Francis Daly wrote:
> On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
>> > On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
>
> Hi there,
>
>>
On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
> On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
>
> Hi there,
>
>> > Possibly one of them covers what you want?
>>
>> There are
On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
> On Tue, May 31, 2016 at 09:23:36AM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 7:55 AM, Larry Martell
>> wrote:
>> >>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
>> >>> wrote:
On Tue, May 31, 2016 at 7:55 AM, Larry Martell wrote:
> On Tue, May 31, 2016 at 7:41 AM, Larry Martell
> wrote:
>> On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
>> wrote:
>>>
>>>
>>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
>>> w
On Tue, May 31, 2016 at 7:41 AM, Larry Martell wrote:
> On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
> wrote:
>>
>>
>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
>> wrote:
>>>
>>> Is there any way with nginx to check a request's h
On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
wrote:
>
>
> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
> wrote:
>>
>> Is there any way with nginx to check a request's headers and send back
>> a 401 if the headers are not proper?
>
>
>
>
Is there any way with nginx to check a request's headers and send back
a 401 if the headers are not proper?
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Sun, May 3, 2015 at 8:18 AM, Maxim Dounin wrote:
> Hello!
>
> On Fri, May 01, 2015 at 12:04:51PM -0400, Larry Martell wrote:
>
>> Prior to now, all the django projects I've worked on have used apache
>> and WSGI. With those, when an error occurred I went to
&g
Prior to now, all the django projects I've worked on have used apache
and WSGI. With those, when an error occurred I went to
/var/log/httpd/error_log and details of the error were clearly there.
Now for the first time I am working on a project using nginx and
uWSGI. Here, the /var/log/nginx/error_
37 matches
Mail list logo
