> On 15. May 2023, at 17.15, Francis Daly wrote:
>
> On Mon, May 15, 2023 at 12:46:14PM -1000, Palvelin Postmaster via nginx wrote:
>>> On 8. May 2023, at 8.49, Palvelin Postmaster via nginx
>>> wrote:
>
> Hi there,
>
>>> I use php-fpm together
Can anyone help me with this?
> On 8. May 2023, at 8.49, Palvelin Postmaster via nginx
> wrote:
>
> Hi all!
>
> I use php-fpm together with nginx.
>
> My PHP app serves files which have hashed filenames and no filename extension
> from a specific subdirect
Hi all!
I use php-fpm together with nginx.
My PHP app serves files which have hashed filenames and no filename extension
from a specific subdirectory url, e.g
/files/hash/31b4ba4a0dc6536201c25e92fe464f85
I would like to be able to set, for example, a separate ’expires’ value to
these files wi
I wonder what can cause these weird error log entries? The log entries indicate
a PID which doesn’t exist. Does nginx launch some temporary process when it
starts?
Nginx 1.21.0 on Ubuntu 20.04.
root@k2:~# systemctl restart nginx
root@k2:~# tail /var/log/nginx/error.log
2021/06/08 21:25:32 [war
I’m trying to learn how to pass specific Magento 1.x URLs such as this to a
PHP-FPM backend.
/js/index.php/x.js?f=prototype/prototype.js,prototype/validation.js,mage/adminhtml/events.js,mage/adminhtml/form.js,scriptaculous/effects.js
All the nginx configs I’ve found (e.g.
https://gist.github.co
> On 4 Sep 2019, at 18.32, j94305 wrote:
>
> On the other hand, why do you need the ALB if you have an NGINX in there,
> anyway? I would rather settle for a simple NLB and handle http/https
> redirections etc. in the NGINX itself.
Is it possible to terminate SSL at NLB with multiple certificat
> On 4 Sep 2019, at 18.32, j94305 wrote:
>
> In order to redirect http to https, you have to define a listener rule in
> the ALB that redirects all traffic on port 80 to port 443 (of the ALB) with
> the original path and query parameters. The status code should be a 301
> (permanent redirectio
> On Wed, Sep 04, 2019 at 03:59:41PM -0700, Palvelin Postmaster wrote:
>
>> This is still a big mystery to me. Upgrading to nginx 1.16.1 didn’t help.
>>
>> As far as I can understand, the nginx master process IS running with root
>> privileges.
>
> The error is f
This is still a big mystery to me. Upgrading to nginx 1.16.1 didn’t help.
As far as I can understand, the nginx master process IS running with root
privileges.
> On 19 Sep 2018, at 2.00, Palvelin Postmaster via nginx
> wrote:
>
> Why am I getting these log warn/emerg? Running
I have AWS ALB in front of an instance running nginx. I want to terminate https
at the load balancer.
I have setup ALB's http listener to redirect http to https and forward https to
the instance’s port 80.
I’m switching from using apache to nginx. My apache currently responds on a
single port
I have AWS ALB in front of an instance running nginx. I want to terminate https
at the load balancer.
I have setup ALB's http listener to redirect http to https and forward https to
the instance’s port 80.
I’m switching from using apache2 to nginx. My apache responds on a single port
80. In my
> On 22 Jul 2019, at 4:54, Maxim Dounin wrote:
>
> Hello!
>
> On Fri, Jul 19, 2019 at 11:35:44AM -0700, Palvelin Postmaster via nginx wrote:
>
>>> On 19 Jul 2019, at 9.59, Maxim Dounin wrote:
>>>
>>> Hello!
>>>
>>> On Thu,
> On 19 Jul 2019, at 9.59, Maxim Dounin wrote:
>
> Hello!
>
> On Thu, Jul 18, 2019 at 10:03:24AM -0700, Palvelin Postmaster via nginx wrote:
>
>> we’re getting random SSL_write() failed errors on seemingly
>> legitimate requests. The common denominator se
Hi,
we’re getting random SSL_write() failed errors on seemingly legitimate
requests. The common denominator seems to be they are all for static files
(images, js, etc.).
Can anyone help me debug the issue?
Here’s a debug log paste for one incident: https://pastebin.com/ZsbLuD5N
Our architect
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I’m running a standard Ubuntu 18.04, not SELinux. I’m under the assumption that
my nginx master process IS being run by root.
> On 25 Jan 2019, at 19:03, Maxim Ozerov wrote:
>
> Hm... it doesn't sound believable, but for example, you can restrict the root
> user with SELinux context ;)
>
>>
> On 25 Jan 2019, at 03:50, Zhang Chao wrote:
>
> Hello!
>
> > Why does this error occur (Ubuntu 18.04/nginx 1.14.0)?
> >
> > nginx.conf:21
> > user www-data;
> >
> > error.log
> > 2019/01/24 19:07:07 [warn] 3526#3526: the "user" directive makes sense only
> > if the master process runs w
Why does this error occur (Ubuntu 18.04/nginx 1.14.0)?
nginx.conf:21
user www-data;
error.log
2019/01/24 19:07:07 [warn] 3526#3526: the "user" directive makes sense
only if the master process runs with super-user privileges, ignored in
/etc/nginx/nginx.conf:21
# ps -axu |grep n
> On 13 Dec 2018, at 16:31, Maxim Dounin wrote:
>
> Hello!
>
> On Thu, Dec 13, 2018 at 11:17:03AM +0200, Palvelin Postmaster via nginx wrote:
>
>> Hi,
>>
>> I run nginx/1.14.0 (Ubuntu 18.04) and PHP-FPM 7.2. I get such occasional
>> (daily
Hi,
I run nginx/1.14.0 (Ubuntu 18.04) and PHP-FPM 7.2. I get such occasional
(daily) errors about too long cache file headers:
2018/12/13 10:39:49 [crit] 1537#1537: *760972 cache file
"/var/lib/nginx/fastcgi/mydomain-fi/d/be/7a11ac32c28dc9f8c3d7da12fe3d6bed" has
too long header, client: XXX.XX
> On 25 Sep 2018, at 16:35, Palvelin Postmaster via nginx
> wrote:
>
> I use Wordpress’ REST API post feed to embed articles on an external site. My
> articles are updated fairly seldom, so there’s probably no need to
> dynamically compile every request response. I’m
I use Wordpress’ REST API post feed to embed articles on an external site. My
articles are updated fairly seldom, so there’s probably no need to dynamically
compile every request response. I’m thinking of using fastcgi cache to cache
the feed.
I’m currently skipping caching for all requests wit
Why am I getting these log warn/emerg? Running Nginx 1.14.0 on Ubuntu 18.04.
root@k2:~# whoami
root
root@k2:~# service nginx restart
root@k2:~# tail /var/log/nginx/error.log
2018/09/19 11:38:47 [warn] 22399#22399: the "user" directive makes sense only
if the master process runs with super-user
I believe my current rexexp match isn’t proper because it’s missing an anchor
from the pattern:
location ~ /\. {
deny all;
}
What would be more appropriate? Would this work?
location ~ /\..*$
--
Palvelin.fi Hostmaster
postmas...@palvelin.fi
> On 10 Sep 2018, at 16:27, Maxim Konovalov wrote:
>
> On 10/09/2018 16:19, Palvelin Postmaster via nginx wrote:
>> What chat icon? Where?
>
> Please see on the screenshort attached.
Facepalm myself :D
--
Palvelin.fi Hostmaster
p
What chat icon? Where?
> On 10 Sep 2018, at 15:45, Maxim Konovalov wrote:
>
> Hi Palvelin,
>
> it makes sense to open a support case -- click on a chat icon in the
> bottom-right corner.
>
> On 10/09/2018 15:06, Palvelin Postmaster via nginx wrote:
>> Hi,
>&
Hi,
my nginx config hierarchy is:
/etc/nginx/nginx.conf (commented out except for a single include directive of
/etc/nginx/conf.d/*.conf)
/etc/nginx/conf.d/default.conf (server-wider config directives and an include
of /etc/nginx/sites-enabled/*.conf)
/etc/nginx/sites-enabled/domainX.conf (mult
27 matches
Mail list logo
