<div dir="ltr"><div class="gmail_default" style="font-size:small">Is there any paid support that would help me fix this problem:</div><div class="gmail_default" style="font-size:small">This works:</div><div class="gmail_default" style="font-size:small"><a href="https://www.ntn24.com/noticias-actualidad/crecen-las-hipotesis-alrededor-de-la-muerte-del-exjefe-del-grupo-wagner-yevgueni-prigozhin-439911">https://www.ntn24.com/noticias-actualidad/crecen-las-hipotesis-alrededor-de-la-muerte-del-exjefe-del-grupo-wagner-yevgueni-prigozhin-439911</a><br></div><div class="gmail_default" style="font-size:small">but in the link below, the video from videomotion, fails to play:</div><div class="gmail_default" style="font-size:small"><a href="https://ntn24.1eye.us/noticias-actualidad/crecen-las-hipotesis-alrededor-de-la-muerte-del-exjefe-del-grupo-wagner-yevgueni-prigozhin-439911">https://ntn24.1eye.us/noticias-actualidad/crecen-las-hipotesis-alrededor-de-la-muerte-del-exjefe-del-grupo-wagner-yevgueni-prigozhin-439911</a><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">The proxy should work, this is my definition</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"> server {<br> default_type application/octet-stream;<br> set $template_root /usr/local/openresty/nginx/html/templates;<br> listen <a href="http://38.95.11.236:443">38.95.11.236:443</a> ssl;<br> error_log logs/error.log warn;<br> access_log logs/access.log;<br> server_name <a href="http://ntn24.1eye.us">ntn24.1eye.us</a>;<br> ssl_certificate /etc/letsencrypt/live/<a href="http://ntn24.1eye.us/fullchain.pem">ntn24.1eye.us/fullchain.pem</a>;<br> ssl_certificate_key /etc/letsencrypt/live/<a href="http://ntn24.1eye.us/privkey.pem">ntn24.1eye.us/privkey.pem</a>;<br> include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot<br> ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot<br><br> location / {<br>include /etc/proxy_include.txt;<br>proxy_cookie_domain <a href="https://ntn24.com">https://ntn24.com</a> <a href="https://ntn24.1eye.us">https://ntn24.1eye.us</a>;<br>proxy_set_header Host "<a href="http://www.ntn24.com">www.ntn24.com</a>";<br>proxy_pass <a href="https://www.ntn24.com">https://www.ntn24.com</a>;<br>proxy_redirect <a href="https://www.ntn24.com">https://www.ntn24.com</a> <a href="https://ntn24.1eye.us">https://ntn24.1eye.us</a>;<br><br>subs_filter_types text/css text/javascript application/javascript;<br>subs_filter "<a href="http://ntn24.com">ntn24.com</a>" "<a href="http://ntn24.1eye.us">ntn24.1eye.us</a>" gi;<br>subs_filter "https://(.*).<a href="http://ntn24.com/(.*)">ntn24.com/(.*)</a>" "<a href="https://ntn24.1eye.us/$1/$2">https://ntn24.1eye.us/$1/$2</a>" gi;<br>subs_filter "<a href="https://ntn24.com">https://ntn24.com</a>" "<a href="https://ntn24.1eye.us">https://ntn24.1eye.us</a>" gi;<br>subs_filter "<a href="https://www.ntn24.com">https://www.ntn24.com</a>" "<a href="https://ntn24.1eye.us">https://ntn24.1eye.us</a>" gi;<br>subs_filter "<a href="http://www.ntn24.com">www.ntn24.com</a>" "<a href="http://ntn24.1eye.us">ntn24.1eye.us</a>" gi;<br><br> }<br><br><br> }<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">the proxy_include.txt file:</div><div class="gmail_default" style="font-size:small">proxy_buffering on;<br>resolver 127.0.0.1 ipv6=off;<br>proxy_http_version 1.1;<br>proxy_buffer_size 128k;<br>proxy_busy_buffers_size 256k;<br>proxy_buffers 4 256k;<br>proxy_pass_header *;<br>proxy_set_header Connection "Keep-Alive";<br>proxy_set_header Proxy-Connection "Keep-Alive";<br>#proxy_set_header User-Agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.82 Safari/537.36";<br>#proxy_set_header User-Agent $http_user_agent;<br><br>proxy_set_header X-Frame-Options sameorigin; # read here<br>proxy_set_header X-Content-Type-Options nosniff; # read here<br>proxy_set_header X-Xss-Protection "1; mode=block"; #read here<br>proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br>proxy_set_header X-Forwarded-Proto $scheme;<br>proxy_set_header Upgrade $http_upgrade;<br>proxy_set_header Connection $http_connection;<br>proxy_set_header Accept-Encoding "";<br>proxy_set_header X-Real-IP $remote_addr;<br>proxy_set_header X-Scheme $scheme;<br>proxy_ssl_server_name on;<br>proxy_ssl_name $proxy_host;<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Sep 2, 2023 at 7:16 AM Francis Daly <<a href="mailto:francis@daoine.org">francis@daoine.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, Sep 02, 2023 at 08:01:42AM +0000, Shashi Kant Sharma wrote:<br>
<br>
Hi there,<br>
<br>
> I am looking forward response on this. Can you please response or suggest any time for discussion today.<br>
<br>
For the <a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a> public list for "community" support of the open<br>
source application: if you can show what you are doing, and what you<br>
are seeing, and what you want to see instead; then there's a better<br>
chance that someone will be able to to either recognise the problem,<br>
or re-create the problem.<br>
<br>
You seem to be reporting that an upload of something bigger than 20 MB<br>
leads to some problem.<br>
<br>
It sounds like you might want to use the client_max_body_size directive<br>
(<a href="http://nginx.org/r/client_max_body_size" rel="noreferrer" target="_blank">http://nginx.org/r/client_max_body_size</a>) if you get a 413 response from<br>
nginx when you send a big file and not when you send a small file.<br>
<br>
But if your nginx accepts the current big upload, and whatever nginx<br>
sends the request to for further processing rejects it as too big,<br>
then that other thing is the thing that would need to be reconfigured<br>
to allow it.<br>
<br>
Maybe that's enough to allow you to resolve the issue? If not, if you<br>
can provide more specific details about what your system is doing,<br>
someone might be able to make an alternate suggestion.<br>
<br>
Good luck with it,<br>
<br>
f<br>
-- <br>
Francis Daly <a href="mailto:francis@daoine.org" target="_blank">francis@daoine.org</a><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="https://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">https://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</blockquote></div>