BioTime login fails with 403 when using HTTPS behind Nginx reverse proxy

We have a ZKTeco MB10 Attendance Device

I have successfully installed it, and connected to the BioTime 9.5 that we are hosting on a VPS,

I have pointed a subdomain record to the the VPS ip address and I can access the bioTime using checkin.company.com

This works fine on http

And I am using nginx as a reverse proxy

http://checkin.company.com

nginx config file

server {        listen       80;        server_name  checkin.company.com;     location / {        proxy_pass http://127.0.0.1:9040;          proxy_set_header Host $host;        proxy_set_header X-Real-IP $remote_addr;        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;        proxy_set_header X-Forwarded-Proto $scheme; }}

Now the issue is with SSL if I try to get https. I cannot login to BioTime web login anymore

https://checkin.company.com

nginx config file

server {     listen 443 ssl;     server_name checkin.company.com;     ssl_certificate      C:\win-acme\certs\checkin.company.com-chain.pem;     ssl_certificate_key  C:\win-acme\certs\checkin.company.com-key.pem;     ssl_session_cache    shared:SSL:1m;     ssl_session_timeout  5m;     ssl_ciphers  HIGH:!aNULL:!MD5;     ssl_prefer_server_ciphers  on;     location / {         proxy_pass http://127.0.0.1:9040;         proxy_set_header Host $host;         proxy_set_header X-Real-IP $remote_addr;         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;         proxy_set_header X-Forwarded-Proto $scheme;     } }

While using https://

In the Nginx Access Logs I get this

82.xxx.xx.xxx - -  "GET /login/?next=/ HTTP/1.1" 200 11958 82.xxx.xx.xxx - - "PATCH /base/system_verify/ HTTP/1.1" 403 1019 

using https I get 403 for /base/system_verify/

I don't know what's the issue and how can I resolve it any insights or help will be appreciated