Thank you very much for this solution. but I have 3 mp3 servers. How can I
share requests equally? With 301, I can only send a request to a single ip
address.
Best.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,289072,289104#msg-289104
Hi,
I'm always happy to announce a new release of NGINX Unit, but this one's BIG.
Besides the varied features and bugfixes, some breakthrough improvements were
made under the hood.
As you may know, Unit uses an advanced architecture that relies on dedicated
processes to serve different roles in
Hi,
I'm always happy to announce a new release of NGINX Unit, but this one's BIG.
Besides the varied features and bugfixes, some breakthrough improvements were
made under the hood.
As you may know, Unit uses an advanced architecture that relies on dedicated
processes to serve different roles in
Thanks for the reply, Thomas.
> You said this is "shared hosting" - when you say "shared hosting" do you
> mean this is *not* a dedicated machine but one machine out of many in a
> shared environment?
Sorry, I meant virtual hosting.
> Have you tested briefly by disabling your firewall just to
You said this is "shared hosting" - when you say "shared hosting" do you
mean this is *not* a dedicated machine but one machine out of many in a
shared environment?
Have you tested briefly by disabling your firewall just to see if that
fixes the issue?
What is the backend? You're passing
Hi All,
Newbie question. I posted this on Stack Overflow but haven't gotten any
replies yet.
https://stackoverflow.com/questions/63391424/why-do-i-get-connection-timeout-on-ssl-even-though-nginx-is-listening-and-firewa
Most/many visitors to my site https://example.org get a connection timeout.
Maxim Dounin Wrote:
---
> Hello!
>
> On Thu, Aug 13, 2020 at 12:11:54PM -0400, vergil wrote:
>
> > Maxim Dounin Wrote:
> > ---
> > > Hello!
> > >
> > > On Thu, Aug 13, 2020 at 11:39:36AM
Hello!
On Thu, Aug 13, 2020 at 12:11:54PM -0400, vergil wrote:
> Maxim Dounin Wrote:
> ---
> > Hello!
> >
> > On Thu, Aug 13, 2020 at 11:39:36AM -0400, vergil wrote:
> >
> > > This one was hard to catch.
> > >
> > > I've captured one error
Maxim Dounin Wrote:
---
> Hello!
>
> On Thu, Aug 13, 2020 at 11:39:36AM -0400, vergil wrote:
>
> > This one was hard to catch.
> >
> > I've captured one error with 30 seconds delta before and after the
> event.
> > Where can i attach log file
Hello!
On Thu, Aug 13, 2020 at 11:39:36AM -0400, vergil wrote:
> This one was hard to catch.
>
> I've captured one error with 30 seconds delta before and after the event.
> Where can i attach log file for you? There's 400K messages, so i cannot
> simple put it here.
Attaching the log to the
Hello!
On Thu, Aug 13, 2020 at 10:01:38AM -0400, vergil wrote:
> Of course!
>
> nginx version: nginx/1.19.2
> built by gcc 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
> built with OpenSSL 1.0.2g 1 Mar 2016
> TLS SNI support enabled
> configure arguments: --prefix=/etc/nginx
This one was hard to catch.
I've captured one error with 30 seconds delta before and after the event.
Where can i attach log file for you? There's 400K messages, so i cannot
simple put it here.
Regards,
Alexander.
Posted at Nginx Forum:
Of course!
nginx version: nginx/1.19.2
built by gcc 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
built with OpenSSL 1.0.2g 1 Mar 2016
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx
--modules-path=/usr/lib/nginx/modules
Hello!
On Thu, Aug 13, 2020 at 06:57:59AM -0400, Mark Lybarger wrote:
> I'm using rewrite to change some tokens in the url path, and am using ssl
> proxy to send traffic to a downstream server.
>
> if i post to https://myhost/start/foo/213/hello, the request gets to
>
details: https://hg.nginx.org/njs/rev/5a80b43b7098
branches:
changeset: 1492:5a80b43b7098
user: Dmitry Volyntsev
date: Thu Aug 13 13:40:36 2020 +
description:
Improved error handling in njs_file_tree_walk().
This also fixes Coverity CID 1465877.
diffstat:
src/njs_fs.c | 75
Hello!
On Thu, Aug 13, 2020 at 09:10:22AM -0400, vergil wrote:
> Good day.
>
> Todays morning we've updated one of our nginx servers to the latest version
> (1.19.2 from 1.19.1).
>
> Since then our log contains "SSL_shutdown() failed (SSL: ... bad write
> retry)" messages which i think you'd
Hello!
On Wed, Aug 12, 2020 at 11:00:20AM -0400, mageside wrote:
> Здавствуйте. Помогите настроить нгинк для корректной работы фронта (написан
> на реакте) и бекента (маджента).
> Фронт обращается на мадженту по определенным урлам (домен/graphql? и тд) что
> бы получить данные.
> Маджента по
Good day.
Todays morning we've updated one of our nginx servers to the latest version
(1.19.2 from 1.19.1).
Since then our log contains "SSL_shutdown() failed (SSL: ... bad write
retry)" messages which i think you'd fixed in this version (i didn't seen
this messages before as far as i remember).
Hello!
On Thu, Aug 13, 2020 at 01:32:18AM -0400, RekGRpth wrote:
> Core was generated by `nginx:'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x555c3ace3b7e in ngx_rbtree_min (node=0x0, sentinel=0x555c3ae2f720
> ) at src/core/ngx_rbtree.h:76
> 76 while (node->left !=
I'm using rewrite to change some tokens in the url path, and am using ssl
proxy to send traffic to a downstream server.
if i post to https://myhost/start/foo/213/hello, the request gets to
https://client-service-host/client/service/hello/213 using the needed
certificate. great.
my question is,
On Wed, Aug 12, 2020 at 02:16:50AM -0400, Dr_tux wrote:
Hi there,
> I have a Nginx reverse proxy. How can I redirect it to the real server URL
> when I download mp3 files in the reverse proxy.
Make a location{} that handles mp3-file requests, and "return 301"
(or otherwise redirect) there.
>
21 matches
Mail list logo
