Issues connecting a Trezor One to a regtest BitCore Node

I have BitCore running on http://127.0.0.1:3000 and am using a NGINX HTTPS reverse proxy server listening on port 4000 to forward traffic to it since Trezor doesn’t allow non-HTTPS URLs in their server selection. I’m very new to NGINX/Trezor/BitCore so it’s very possible I’m just mis-configuring/misunderstanding something.

When I attempt to add https://127.0.0.1:4000 as my BitCore server on the Trezor.io site, I see the Trezor request hit my NGINX server:

access.log

127.0.0.1 - - [08/May/2019:10:07:42 -0400] "GET /socket.io/?EIO=3&transport=websocket HTTP/1.1" 101 98 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0" 4000

But then the Trezor website returns a “The bitcore server doesn’t seem to reply” error. When I attempt to visit https://127.0.0.1:4000/socket.io/?EIO=3&transport=websocket in a web browser I get this as a response:

{"code":3,"message":"Bad request"}

And I get the same response if I bypass the NGINX server and access http://127.0.0.1:3000/socket.io/?EIO=3&transport=websocket through a browser.

My NGINX default file:

server {
    listen 4000 ssl;
    server_name 127.0.0.1;
    ssl_certificate /home/username/sslcerts/cert.pem;
    ssl_certificate_key /home/username/sslcerts/private.pem;

  location / {
          proxy_pass http://127.0.0.1:3000;
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection "upgrade";
        }
     }

Is there something I’m doing wrong or are Trezor wallets no longer compatible with BitCore?