Re: SSL_write() failed (55: No buffer space available) while proxying upgraded connection

2021-11-03 Thread johan.belin
Hi Sergey, Thanks for your reply! Unfortunately that is exactly the type of knowledge we lack! Any idea where we can find someone that can help us with that? MacMini M1 macOS BigSur 11.6 Posted at Nginx Forum: https://forum.nginx.org/read.php?2,292750,292753#msg-292753 ___

Re: SSL_write() failed (55: No buffer space available) while proxying upgraded connection

2021-11-03 Thread Sergey A. Osokin
Hi Johan, hope you're doing well thse days. On Wed, Nov 03, 2021 at 02:59:15PM -0400, johan.belin wrote: > I am a beginner so I am sorry for lacking info or stupid questions! > Building a WebRTC streaming media system based on mediasoup, the server runs > on a MacMini M1 in node, nginx port forwa

Re: Help with static content

2021-11-03 Thread deeztek
So after some more trial and error, I was able to display static content by including the following: location ~* \.(?:ico|css|js|gif|jpe?g|png|woff2|map)$ { # Some basic cache-control for static files to be sent to the browser expires max; add_header Pragma public; add_head

SSL_write() failed (55: No buffer space available) while proxying upgraded connection

2021-11-03 Thread johan.belin
I am a beginner so I am sorry for lacking info or stupid questions! Building a WebRTC streaming media system based on mediasoup, the server runs on a MacMini M1 in node, nginx port forwards to 8400. We are doing load tests and at 120 connected clients nginx gives the following error message: 2021/1

Re: Help with static content

2021-11-03 Thread deeztek
I ran it and there were no problems found. I think there is a misunderstanding. There are no errors in Nginx. Nginx starts with no problem and I'm able to access the application. The only problem is that static content is not being served when I configure and use a FQDN to access the application.

Re: Help with static content

2021-11-03 Thread basti
Check your config with 'nginx -T | less' for 'server_name _'. This is a catch_all as described in the docs. On 02.11.21 22:50, deeztek wrote: > I already tried that with same results. > > Posted at Nginx Forum: > https://forum.nginx.org/read.php?2,292742,292744#msg-292744 > > __