Cache only one specific query string pattern

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

Re: Cache only one specific query string pattern

> 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

FastCGI cache file has too long header

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

Re: FastCGI cache file has too long header

> 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

User directive error

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

Re: User directive error

> 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

Re: User directive error

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 ;) > >>

SSL_write() failed errors

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

Re: SSL_write() failed errors

> 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

Re: SSL_write() failed errors

> 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,

Config problems with Amplify

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

Re: Config problems with Amplify

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, >&

Re: Config problems with Amplify

> 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

Deny access to hidden files and directories (and their content)

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

Errors suggesting nginx isn't started as root

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

Separate location for files served by php-fpm

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

Re: Separate location for files served by php-fpm

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

Re: Separate location for files served by php-fpm

> 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