fix(connectionhandler): Ensure proper termination of TLS connections without SNI by explicitly ending the socket after sending the unrecognized_name alert. This prevents the connection from hanging and avoids potential duplicate handling.

ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@push.rocks/smartproxy',
-  version: '4.2.1',
+  version: '4.2.2',
   description: 'A powerful proxy package that effectively handles high traffic, with features such as SSL/TLS support, port proxying, WebSocket handling, dynamic routing with authentication options, and automatic ACME certificate management.'
 }

ts/classes.pp.connectionhandler.ts

@@ -589,15 +589,15 @@ export class ConnectionHandler {
               socket.cork();
               const writeSuccessful = socket.write(serverNameUnknownAlertData);
               socket.uncork();
+              socket.end();
               
               // Function to handle the clean socket termination - but more gradually
               const finishConnection = () => {
                 // Give Chrome more time to process the alert before closing
                 // We won't call destroy() at all - just end() and let the socket close naturally
-                
+
                 // Log the cleanup but wait for natural closure
                 setTimeout(() => {
-                  socket.end();
                   this.connectionManager.cleanupConnection(record, 'session_ticket_blocked_no_sni');
                 }, 1000); // Longer delay to let socket cleanup happen naturally
               };