Hot answers tagged

2

No, this is not possible. Haproxy does not understand the FTP protocol, and therefore can't do things like re-write the FTP commands and responses that include the true IP address of the FTP server. If that's a requirement, then you'll have to find a different proxy solution.


2

So I have found a solution. I remove all newlines in the certificate and send them as a single HTTP Header from the proxy to the back-end, similar as explained here: https://forum.nginx.org/read.php?2,236546,236546 In my back-end I reconstruct the certificate by adding a newline every 64 characters. The updated code for the reverse proxy is the following ...


2

today, nginx Supports ssl pass thru: https://serversforhackers.com/tcp-load-balancing-with-nginx-ssl-pass-thru


1

The following configuration works fine on my server. proxy_buffers 16 16k; proxy_buffer_size 16k;


1

I see 2 solutions here: Enable LUA scripting and reformat the string in a no-end-of-line format. Use the Set Misc plugin and use base64_encode on that variable.


1

Nginx will always create new proxy connection for incoming connection unless it is cached localy. As MJPG is an infinite loop, it doesn't seem as an option here. What I would however try is setup a ffmpeg/vlc on the proxy server to consume mjpg stream from rpi. Nginx then can connect to local ffmpeg/vlc to get stream. You will then have only one connection ...


1

it won't work with https:// extentions no matter in what way I try to set it Your <VirtualHost *:80> is only matching port 80 traffic, so it cannot work with "https:// extentions." Whatever problem there might be with your proxy setup, your first issue is with your virtual host setup. EDIT per OP comment to answer: what I want to do is redirect ...


1

Not sure about your environment, just as a hint: Is the machine in question publicly reachable? If so, implement authentication / authorization, or use a VPN. If this is valid, how can I fix the error "Too many open files"? Probably, because it's listening to that many ports, your nginx, runs against limits, specifically the ones dealing with file ...



Only top voted, non community-wiki answers of a minimum length are eligible