All files from this thread

File Name	File Size		Posted by	Date
image001.jpg	4.7 KB	open | download	Shashi Kant Sharma	09/01/2023	Read message
image002.png	45.5 KB	open | download	Shashi Kant Sharma	09/01/2023	Read message
image001.jpg	4.7 KB	open | download	Shashi Kant Sharma	09/04/2023	Read message
image002.png	45.5 KB	open | download	Shashi Kant Sharma	09/04/2023	Read message

Is there any paid support that would help me fix this problem:
This works:
https://www.ntn24.com/noticias-actualidad/crecen-las-hipotesis-alrededor-de-la-muerte-del-exjefe-del-grupo-wagner-yevgueni-prigozhin-439911
but in the link below, the video from videomotion, fails to play:
https://ntn24.1eye.us/noticias-actualidad/crecen-las-hipotesis-alrededor-de-la-muerte-del-exjefe-del-grupo-wagner-yevgueni-prigozhin-439911

The proxy should work, this is my definition

server {
default_type application/octet-stream;
set $template_root /usr/local/openresty/nginx/html/templates;
listen 38.95.11.236:443 ssl;
error_log logs/error.log warn;
access_log logs/access.log;
server_name ntn24.1eye.us;
ssl_certificate /etc/letsencrypt/live/ntn24.1eye.us/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/ntn24.1eye.us/privkey.pem;
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by
Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

location / {
include /etc/proxy_include.txt;
proxy_cookie_domain https://ntn24.com https://ntn24.1eye.us;
proxy_set_header Host "www.ntn24.com";
proxy_pass https://www.ntn24.com;
proxy_redirect https://www.ntn24.com https://ntn24.1eye.us;

subs_filter_types text/css text/javascript application/javascript;
subs_filter "ntn24.com" "ntn24.1eye.us" gi;
subs_filter "https://(.*).ntn24.com/(.*)" "https://ntn24.1eye.us/$1/$2" gi;
subs_filter "https://ntn24.com" "https://ntn24.1eye.us" gi;
subs_filter "https://www.ntn24.com" "https://ntn24.1eye.us" gi;
subs_filter "www.ntn24.com" "ntn24.1eye.us" gi;

}


}


the proxy_include.txt file:
proxy_buffering on;
resolver 127.0.0.1 ipv6=off;
proxy_http_version 1.1;
proxy_buffer_size 128k;
proxy_busy_buffers_size 256k;
proxy_buffers 4 256k;
proxy_pass_header *;
proxy_set_header Connection "Keep-Alive";
proxy_set_header Proxy-Connection "Keep-Alive";
#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";
#proxy_set_header User-Agent $http_user_agent;

proxy_set_header X-Frame-Options sameorigin; # read here
proxy_set_header X-Content-Type-Options nosniff; # read here
proxy_set_header X-Xss-Protection "1; mode=block"; #read here
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_set_header Accept-Encoding "";
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_ssl_server_name on;
proxy_ssl_name $proxy_host;







On Sat, Sep 2, 2023 at 7:16 AM Francis Daly <francis@daoine.org> wrote:

> On Sat, Sep 02, 2023 at 08:01:42AM +0000, Shashi Kant Sharma wrote:
>
> Hi there,
>
> > I am looking forward response on this. Can you please response or
> suggest any time for discussion today.
>
> For the nginx@nginx.org public list for "community" support of the open
> source application: if you can show what you are doing, and what you
> are seeing, and what you want to see instead; then there's a better
> chance that someone will be able to to either recognise the problem,
> or re-create the problem.
>
> You seem to be reporting that an upload of something bigger than 20 MB
> leads to some problem.
>
> It sounds like you might want to use the client_max_body_size directive
> (http://nginx.org/r/client_max_body_size) if you get a 413 response from
> nginx when you send a big file and not when you send a small file.
>
> But if your nginx accepts the current big upload, and whatever nginx
> sends the request to for further processing rejects it as too big,
> then that other thing is the thing that would need to be reconfigured
> to allow it.
>
> Maybe that's enough to allow you to resolve the issue? If not, if you
> can provide more specific details about what your system is doing,
> someone might be able to make an alternate suggestion.
>
> Good luck with it,
>
> f
> --
> Francis Daly francis@daoine.org
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx