The programmers currently use a file to specify the IP of the remote SQL server. As a work around for the time being I have added a 2nd interface to the front end server and the remote SQL server. These are the errors we get when we hit the 65k limit. mysqli_connect(): Can't connect to MySQL server on '192.168.98.19' (99) Front end 192.168.99.8 192.169.98.9 Remote SQL 192.168.99.19 192.by CCS - Nginx Mailing List - English
That is what I was thinking, I am having an issue with the listen directive, what should I use since the local port is "random" also for split_clients "$remote_addr$remote_port" $split_ip I cant use remote address since its a local address ?? same with port ? This is what I have been trying and have not had any luck upstream backend { server 192.168.99.19:3306; } serby CCS - Nginx Mailing List - English
This is a very busy server and tried to push our programming department to move to persistent connections, they feel that it could be a security issue if dealing with sensitive information since that connection could be hijacked. We do not have an issue on the mysql server side with Port Exhaustion, just on the "Frontend webserver". We have made a lot of changes, and are currently managiby CCS - Nginx Mailing List - English
Yes all of those changes you have mentioned have been made. Thanks Brandon Best Regards, Brandon Mallory Network & Systems Engineer MEDENT EMR/EHR 15 Hulbert Street Auburn, NY 13021 Phone: [ callto:(315)-255-0900 | (315)-255-0900 ] Fax: [ callto:(315)-255-3539 | (315)-255-3539 ] Web: [ http://www.medent.com/ | www.medent.com ] This message and any attachments may contain infoby CCS - Nginx Mailing List - English
I have recently moved our sql server off of our webserver and now we are experiencing Port Exhaustion. We have made all the changed we could in the kernel to help with this but still hitting limits. I have added a 2nd virtual network adapter, I am now trying to "load balance" the lan connection between our web server and mysql server port 3306. Webserver 192.168.99.17 192.168.99.21by CCS - Nginx Mailing List - English
This worked for me without and issue. Try and copy. log_format proxy '$remote_addr [$time_local]' 'with SSL Server name "$ssl_server_name" ' 'proxying to "$selected_upstream" ' '$protocol $status $bytes_sent $bytes_received ' '$session_time'; access_log /var/log/nginxby CCS - Nginx Mailing List - English
Good Advice, After doing some further research. Can you give me your opinion in regards to using the ssl_preread_server_name. So as long as I can get a SNI and then filter TCP connection to the proper server with that information. Does this sound doable ? My plan was to use TLS SNI to to identify and route TCP traffic based in SNI map $ssl_preread_server_name $name { X.X.X.X:11001/12345 1234by CCS - Nginx Mailing List - English
I can try. Basically we have an application that uses TCP to communicate between the client on a windows PC and a linux server. I would like a public facing IP that redirects traffic from the window PC to the correct linux server. I was thinking I could have the windows client point to a public ip and then a location maybe account number. So it would look like Client 1 public ip/12345 forward toby CCS - Nginx Mailing List - English
I am new to NGINX and looking for advice on how to configure NGINX. Here is what I am trying to accomplish for my cloud infrastructure. Have NGINX configured with a public IP (65.x.x.x.) . I need to use TCP for my application ( not http ). I would like to have a client hit the public IP with a location ( 65.x.x.x.x\12345) and have that connection forwarded to a LAN IP. Example: Client1 - aby CCS - Nginx Mailing List - English