diff --git a/nginx/nginx.conf b/nginx/nginx.conf
index d6f71d9..f6a5451 100644
--- a/nginx/nginx.conf
+++ b/nginx/nginx.conf
@@ -1,9 +1,9 @@
 worker_processes 8;
-worker_rlimit_nofile 65536;
+worker_rlimit_nofile 155536;
 worker_shutdown_timeout 10;
 
 events {
-	worker_connections 432768; # Default: 1024
+	worker_connections 32768; # Default: 1024
 }
 
 http {
@@ -33,12 +33,15 @@ http {
 		#server		localhost:4447;
 		#server		localhost:4448;
 
-		server		10.0.0.3:4441;
+		#server		10.0.0.3:4441;
 		server		10.0.0.3:4442;
 
 		server		10.0.0.5:4441;
 		server		10.0.0.5:4442;
 
+		server		10.0.0.6:4441;
+		server		10.0.0.6:4442;
+
 		#server		134.209.69.251:80	backup;
 
 		#server		116.203.32.253:80	backup;
@@ -121,6 +124,8 @@ http {
 
 		location /api/getTotalStats {
 			proxy_pass http://backend_GET;
+                        proxy_cache CACHEZONE;
+			proxy_cache_valid 20m;
 			#return 200 "";
 		}
 
@@ -167,15 +172,24 @@ http {
 			root	/home/sbadmin/SponsorBlockSite/public-prod;
 		}
 		
+		listen [::]:443 default_server ssl http2 ipv6only=on;
 		listen 443 default_server ssl http2; # managed by Certbot
 		#listen 443 http3 reuseport;
 		#ssl_protocols TLSv1.2 TLSv1.3;
 		#listen 80;
-		ssl_certificate		/etc/letsencrypt/live/sponsor.ajay.app-0003/fullchain.pem; # managed by Certbot
-		ssl_certificate_key	/etc/letsencrypt/live/sponsor.ajay.app-0003/privkey.pem; # managed by Certbot
+    ssl_certificate /etc/letsencrypt/live/sponsor.ajay.app-0001/fullchain.pem; # managed by Certbot
+    ssl_certificate_key /etc/letsencrypt/live/sponsor.ajay.app-0001/privkey.pem; # managed by Certbot
 		include				/etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
 		ssl_dhparam			/etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
-	}
+	
+
+
+
+
+
+
+
+}
 
 	server {
 		server_name cdnsponsor.ajay.app;
@@ -195,11 +209,15 @@ http {
 
 
 		listen 443 ssl; # managed by Certbot
-		ssl_certificate /etc/letsencrypt/live/sponsor.ajay.app-0001/fullchain.pem; # managed by Certbot
-		ssl_certificate_key /etc/letsencrypt/live/sponsor.ajay.app-0001/privkey.pem; # managed by Certbot
+    ssl_certificate /etc/letsencrypt/live/sponsor.ajay.app-0001/fullchain.pem; # managed by Certbot
+    ssl_certificate_key /etc/letsencrypt/live/sponsor.ajay.app-0001/privkey.pem; # managed by Certbot
 		include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
 		ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
-	}
+	
+
+
+
+}
 
 	server {
 		access_log off;
@@ -212,6 +230,7 @@ http {
 			return 301 https://$host$request_uri;
 		} # managed by Certbot
 
+		listen [::]:80 ipv6only=on;
 		listen 80;
 		server_name sponsor.ajay.app api.sponsor.ajay.app;
 		return 404; # managed by Certbot
@@ -238,13 +257,18 @@ http {
 			proxy_pass http://10.0.0.3:8080;
 		}
 
+		#listen [::]:443 ssl http2 ipv6only=on;
 		listen 443  ssl http2; # managed by Certbot
 		#listen 443 http3 reuseport;
 		#ssl_protocols TLSv1.2 TLSv1.3;
 		#listen 80;
-		ssl_certificate /etc/letsencrypt/live/sponsor.ajay.app-0003/fullchain.pem; # managed by Certbot
-		ssl_certificate_key /etc/letsencrypt/live/sponsor.ajay.app-0003/privkey.pem; # managed by Certbot
+    ssl_certificate /etc/letsencrypt/live/sponsor.ajay.app-0001/fullchain.pem; # managed by Certbot
+    ssl_certificate_key /etc/letsencrypt/live/sponsor.ajay.app-0001/privkey.pem; # managed by Certbot
 		include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
 		ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
-	}
+	
+
+
+
+}
 }