Activation Agent Issues

[liaoqing1999]

I activated typora on a machine that had to use a proxy. I make sure I can access https://www.typora.io/ on my browser, but the error message "Failed to access the license server. Please check your network or try gain later." still appears when I activate. Can Typora use the built-in proxy of the computer or manually set the proxy?

[abnerlee]

Does https://support.typora.io/activation/#error-message-failed-to-access-the-license-server-please-check-your-network-or-try-gain-later help? Which requires you to remove HTTP_PROXY and HTTPS_PROXY from your system environment variables.

For proxy, Typora uses system proxy, and can also be configured independently (on Windows / Linux) (refer https://www.sxj.xyz/set-proxy-for-typora.html)

[levee223]

I have the same issue. Our corporation has no internet access without a proxy. The following has been tried. [1] With/Without --proxy-server flag. [2] With/Without HTTP_PROXY and HTTPS_PROXY. Is there any other help?

[liaoqing1999]

I found my problem, my company's firewall software blocked the typora activation request.

[even0306]

i am the same as them

[happy2h]

the same

[ghost]

I have to use a VPN to visit store.typora.io. I tried all ways you mentioned, but it didn't work. The error message "Failed to access the license server. Please check your network or try gain later." still appears when I activate. Can Typora make the activation more easy and convenient？ Sorry, I know very little about network proxy.

[levee223]

@abnerlee
I'm not a Chinese user, but I cannot activate Typora 1.0.3 due to a proxy issue. In Typora for Windows, the Editor part (Electron renderer process) uses system proxy, but Activator and Updater seems to ignore system proxy.

[abnerlee]

(For Chinese User) 如果你是中国国内用户，请更新或下载 1.0.3，然后打开 偏好设置 → 通用 → Typora 服务使用国内服务器

[mrcbax]

This paid model is hot trash. Requires internet, and has the gall to ask for "Usage Info". This is not the open source way. You will not be getting my money. And you have lost a loyal user.

[vksir]

In my enviroment, I can do like this:

curl https://www.google.com -x http:example.com -k

and I can't do like this:

curl https://www.google.com -x http:example.com

To use my proxy, it's unable to verify certificate.

And, this is also unuseful:

./Typora.exe --proxy-server=http://example.com

It may be necessary to add an option to prevent typora from verifying the certificate

[MarinnaCole]

The activation agent is completely in-appropriate. Not only the activation server won't be accepted by many modern day IT department, but also the license has to be repeatedly verified every time the application is opened. Would the developers really care about piracy that much that they would rather lose a big chuck of potential industrial users? This is Markdown editor for Christ sake...

[kyet]

Same here.

typora.log (I hide timestmap)

INFO ***  [RenderProcess 2][Log] onBecomeActive
INFO ***  [RenderProcess 2][Log] File.activeWindow = true
ERROR ***  unhandledRejection Error: unable to verify the first certificate
    at TLSSocket.onConnectSecure (_tls_wrap.js:1497:34)
    at TLSSocket.emit (events.js:315:20)
    at TLSSocket.EventEmitter.emit (domain.js:467:12)
    at TLSSocket._finishInit (_tls_wrap.js:932:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:706:12)

Should provide one of the below,

• insecure option (like curl -k)
• set path to self-signed certificate
• use system's certificate store

[0xced]

One hour and counting trying to activate my license behind a proxy. I have tried basically every possible combination of options (--proxy-server=address:port, --proxy-server=address, --proxy-pac-url=url, --no-proxy-server) but I still get errors.

Thanks to @kyet I realized I could look at the typora.log file at %AppData%\Typora\typora.log and here's the recurring error I get:

INFO 13.01.2022, 18:28:57  handle addLicense
INFO 13.01.2022, 18:28:57  request https://store.typora.io/api/client/activate
Error: getaddrinfo ENOTFOUND 80
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
ERROR 13.01.2022, 18:28:59  Error: getaddrinfo ENOTFOUND 80
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)

I guess I could read the 79 messages on nodejs/node#5436 to try to understand if there's a way around this error but I'm not sure I want to!

Now I strongly regret having updated from the beta version. ☹

Given there are so many users reporting issues to activate their license you should really consider an offline mechanism (#4903).

@kyet You may try to set the NODE_TLS_REJECT_UNAUTHORIZED environment variable to 0. I got this to work in another node-based app (maybe it was npm) in order to accept untrusted certificate (which is what often happens in enterprise networks that intercept https traffic).

[kyet]

@0xced Many Thanks! NODE_TLS_REJECT_UNAUTHORIZED trick works!
It should be added to FAQ.

[0xced]

What eventually worked for me was to remove all proxy-related environment variables before launching Typora.

set HTTP_PROXY=
set HTTPS_PROXY=
set NO_PROXY=
Typora.exe

Then I was finally able to activate Typora!

[nayabin]

Same on Windows. All ways here didn't work for me. I am a huge fan of Typora but, I now regret buying it.

request https://store.typora.io/api/client/activate
Error: read ECONNRESET
    at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20)
Error: read ECONNRESET
    at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20)

[abnerlee]

Please try 1.1.0-dev (https://typora.io/releases/dev) and check https://support.typora.io/Offline-Activation/

[nayabin]

Please try 1.1.0-dev (https://typora.io/releases/dev) and check https://support.typora.io/Offline-Activation/

Great! Thank you for your quick support.

[kai2nenobu]

In 1.1.0-dev, offline activation has succeeded in my proxy network as below.

However, I cannot see my license in https://store.typora.io/my.

How can I check my offline activations?

[abnerlee]

@kai2nenobu could you send us ([email protected]) the email or license code you use?

[abnerlee]

close since offline activation is now supported