Uncaught TypeError: a._qs.unescape is not a function

I need help in fixing this issue.

I have implemented ssl to the domain dashboard.boatman.ai

Front end is Angular and Backend is Meteor

I was able to create ssl certificates properly and was able to get Secure Https label on loading the domain, but the page was not rendering because of the error
Uncaught TypeError: a._qs.unescape is not a function
from the build file in the web.browser
Request URL:https://dashboard.boatman.ai/5a0c202b90aa3cc1c9414b703c4e1f343fb0dd4e.js?meteor_js_resource=true

I have not written any code on Meteor to run it to https, I am trying to handle through nginx.
From angular after adding ssl certificates trying to connect to meteor throughwss://localhost/ instead of ws://localhost:3000/

Please find my nginx file below.


events {

}
http {
  server {
     listen 80;
     listen [::]:80 default_server ipv6only=on;
     server_name  dashboard.boatman.ai;
     root   /client;
     index  index.html;


     location / {
        rewrite     ^ https://$server_name$request_uri? permanent;
     }
}

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

 server {
    # Enable HTTP/2
     listen 443 ssl http2;
     listen [::]:443 ssl http2;
     server_name  dashboard.boatman.ai;

     root   /client;
     index  index.html;
   ssl_certificate /etc/letsencrypt/live/dashboard.boatman.ai/fullchain.pem; # managed by Certbot
   ssl_certificate_key /etc/letsencrypt/live/dashboard.boatman.ai/privkey.pem; # managed by Certbot
   ssl_dhparam /etc/ssl/certs/dhparam.pem;


    location / {

                 proxy_pass http://localhost:3000;
                 proxy_http_version 1.1;
                 proxy_set_header Upgrade $http_upgrade; # allow websockets
                 proxy_set_header Connection $connection_upgrade;
		 proxy_set_header X-Forwarded-For $remote_addr;

    }

    location /api {
        proxy_pass http://localhost:3000;
    }

    location /uploadFile {
        proxy_pass http://localhost:3000;
    }

    error_page   500 502 503 504  /50x.html;
    location = /51x.html {
        root   /client;
    }
  }  
}

Any leads would be appreciated.

Have you tried using Passenger?

No, I am not using passenger for deployment. I am just running the build folder using pm2