Hi folks,
I wonder if I missed an announcement for a change in nginx behaviour
or if some local issue is causing me problems. The configuration
server {
listen *:443 ssl default_server;
}
used to bind to both 0.0.0.0:443 and [::]:443, but since I updated to
nginx 1.15.0 it only binds to
Hello!
On Wed, Jun 13, 2018 at 11:01:09AM +0200, Ralph Seichter wrote:
> I wonder if I missed an announcement for a change in nginx behaviour
> or if some local issue is causing me problems. The configuration
>
> server {
> listen *:443 ssl default_server;
> }
>
> used to bind to both 0
Hello!
On Mon, Jun 11, 2018 at 08:53:49AM -0400, ayman wrote:
> When enabling the cache on image filter; nginx workers crash and keep
> getting 500.
>
> I'm using Nginx 1.14.0
>
> error log:
> 2018/06/11 12:30:49 [alert] 46105#0: worker process 46705 exited on signal
> 11 (core dumped)
>
> pro
Hi
On 6/12/18 12:03 AM, Andrei wrote:
- The sheer amount of added context switches (proxying was done local on
a cPanel box, seeing 20-30k reqs/sec during peak hours)
Not clear what you mean here
- Having to manage two software versions, configs, auto config builders
used by internal tools,
On 13.06.18 14:19, Maxim Dounin wrote:
> The "listen *:443" snippet always created only IPv4 listening socket.
That's interesting. Maybe Gentoo Linux did indeed add a custom patch to
previous nginx versions.
What is the shortest officially recommended way to bind nginx to port
443 for both IPv4
Hello!
On Wed, Jun 13, 2018 at 05:10:51PM +0200, Ralph Seichter wrote:
> On 13.06.18 14:19, Maxim Dounin wrote:
>
> > The "listen *:443" snippet always created only IPv4 listening socket.
>
> That's interesting. Maybe Gentoo Linux did indeed add a custom patch to
> previous nginx versions.
>
>
