ETIMEOUT when deploying leancloud_counter_security_sync

[catbro666]

The log is as follows:

INFO  Deploy done: git
INFO  Deploying: leancloud_counter_security_sync
Enter your username: root
Enter your password: *************

ERROR Error: connect ETIMEDOUT xxx.xxx.xxx.xxx:443 [N/A POST https://xxxx.api.lncldglobal.com/1.1/login]
    at /Users/xxxx/workspace/blog/node_modules/leancloud-storage/dist/node/request.js:169:17
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at async Hexo.sync (/Users/xxxx/workspace/blog/node_modules/hexo-leancloud-counter-security/index.js:102:9) {
  code: 'ETIMEDOUT',
  rawMessage: 'connect ETIMEDOUT xxx.xxx.xxx.xxx:443'
}

INFO  Now syncing your posts list to leancloud counter...
INFO  Dealing with record of xxxx
INFO  Deploy done: leancloud_counter_security_sync
INFO  Deploying: baidu_url_submitter
INFO  Submitting urls
https://catbro666.github.io/posts/68dbb05c/
https://catbro666.github.io/posts/83951100/
https://catbro666.github.io/posts/615fc0b5/
https://catbro666.github.io/posts/2dc32e47/
https://catbro666.github.io/posts/657c24ad/
{"remain":2975,"success":5}
INFO  Deploy done: baidu_url_submitter

ERROR Error: connect ETIMEDOUT xxx.xxx.xxx.xxx:443 [N/A GET https://xxxx.api.lncldglobal.com/1.1/classes/Counter]
    at /Users/xxxx/workspace/blog/node_modules/leancloud-storage/dist/node/request.js:169:17
    at processTicksAndRejections (internal/process/task_queues.js:94:5) {
  code: 'ETIMEDOUT',
  rawMessage: 'connect ETIMEDOUT xxx.xxx.xxx.xxx:443'
}
INFO  leancloud.memo successfully updated.

Is that because the http requests in js didn't go through the proxy.

But I already set export all_proxy=socks5://127.0.0.1:7890, and I can access the urls above successfully by using curl like this:

$ curl https://xxxx.api.lncldglobal.com/1.1/login
{"code":401,"error":"Unauthorized."}