Getting SSL Errors since April 6th

[wakatime]

Getting SSL Errors since April 6th

[alanhamlett]

Try adding this to your ~/.wakatime.cfg file:

no_ssl_verify = true

[mobychan]

I finally got it working again.
Looks like the extension is unable to download the wakatime-cli/core correctly and somehow the previously existing one was removed
I downloaded it directly from the github and extracted it into .vscode\extensions\WakaTime.vscode-wakatime-1.2.1\out
Additionally I updated the plugin by using "Extensions: Check for Updates" because the status page told me there was a newer version available(vscode didn't show this) this changed the extensions version from 1.2.0 to 1.2.1

[alanhamlett]

Since your company removed it's proxy, you should remove the proxy setting in your ~/.wakatime.cfg file as it's no longer needed.

You can also edit that proxy config within VS Code with ctrl + shift + p then WakaTime Proxy.

[mobychan]

Thank you for your time.

I removed that setting back when the proxy was removed(and it did work for multiple weeks) and I just checked again, the current content of my ~/.wakatime.cfg file looks like this:

[settings]
api_key = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
debug = true

---

would it be possible to copy the .wakatime.db file to another pc to sync the data for now or would that create problems?

[alanhamlett]

~/.wakatime.db is just an sqlite file, so you can safely copy it to another computer and it will sync. If your first computer gets back online in the future, the duplicate data will be ignored.

[alanhamlett]

Just want to check in, is everything working now?

[mobychan]

Nope still not working, but it might be an issue with my companies firewall, I have been informed that a lot has been changed and as far as I understand it's messing with the https-certificates by deciphering, analysing and then reencoding the requests.

Not sure if this could help but I started using this plugin for unity a while ago, which is working just fine, but uses a direct web-api approach it seems.

But copying the .db file at least lets me upload the data from home, even if it took a while for the data to be uploaded

[mobychan]

Still not working, but it looks wakatime-core doesn't exist anymore and can't be downloaded.
There's nothing new in .wakatime.log(even though it tells me to look there) but the Developer Tools' Console logs this:

[Extension Host] [WakaTime] [DEBUG] Initializing WakaTime v1.2.1
console.ts:136 [Extension Host] [WakaTime] [DEBUG] Looking for python at: C:\Users\sschewe\.vscode\extensions\WakaTime.vscode-wakatime-1.2.1\out\python\pythonw
console.ts:136 [Extension Host] [WakaTime] [DEBUG] Invalid python version: 
console.ts:136 [Extension Host] [WakaTime] [DEBUG] Looking for python at: pythonw
console.ts:136 [Extension Host] [WakaTime] [DEBUG] Valid python version: Python 3.6.5

console.ts:136 [Extension Host] [WakaTime] [DEBUG] Downloading wakatime-core...
log.ts:171   ERR self signed certificate in certificate chain: Error: self signed certificate in certificate chain
	at TLSSocket.<anonymous> (_tls_wrap.js:1088:38)
	at emitNone (events.js:86:13)
	at TLSSocket.emit (events.js:188:7)
	at TLSSocket._finishInit (_tls_wrap.js:610:8)
	at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)
log.ts:171   ERR socket hang up: Error: socket hang up
	at createHangUpError (_http_client.js:302:15)
	at TLSSocket.socketCloseListener (_http_client.js:334:23)
	at emitOne (events.js:101:20)
	at TLSSocket.emit (events.js:191:7)
	at _handle.close (net.js:510:12)
	at TCP.done [as _onclose] (_tls_wrap.js:332:7)

EDIT:
As soon as I do something in a file it logs this to the Developer Tools' Console:

[Extension Host] [WakaTime] [DEBUG] Sending heartbeat: pythonw C:\Users\sschewe\.vscode\extensions\WakaTime.vscode-wakatime-1.2.1\out\wakatime-master\wakatime\cli.py --file d:\Projects\[Folder]\[Folder]\Main\Source\[Folder]\parts\config.ios.xml --plugin "vscode/1.22.2 vscode-wakatime/1.2.1" --alternate-project [Project] --config C:\Users\sschewe\.wakatime.cfg --logfile C:\Users\sschewe\.wakatime.log
console.ts:136 [Extension Host] [WakaTime] [ERROR] pythonw: can't open file 'C:\Users\sschewe\.vscode\extensions\WakaTime.vscode-wakatime-1.2.1\out\wakatime-master\wakatime\cli.py': [Errno 2] No such file or directory

t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:395
(anonymous) @ extensionHost.ts:210
emitTwo @ events.js:106
emit @ events.js:194
process.nextTick @ internal/child_process.js:766
_combinedTickCallback @ internal/process/next_tick.js:73
_tickCallback @ internal/process/next_tick.js:104
console.ts:136 [Extension Host] [WakaTime] [ERROR] Error: Command failed: pythonw C:\Users\sschewe\.vscode\extensions\WakaTime.vscode-wakatime-1.2.1\out\wakatime-master\wakatime\cli.py --file d:\Projects\[Folder]\[Folder]\Main\Source\[Folder]\parts\config.ios.xml --plugin vscode/1.22.2 vscode-wakatime/1.2.1 --alternate-project [Project] --config C:\Users\sschewe\.wakatime.cfg --logfile C:\Users\sschewe\.wakatime.log
pythonw: can't open file 'C:\Users\sschewe\.vscode\extensions\WakaTime.vscode-wakatime-1.2.1\out\wakatime-master\wakatime\cli.py': [Errno 2] No such file or directory

t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:395
(anonymous) @ extensionHost.ts:210
emitTwo @ events.js:106
emit @ events.js:194
process.nextTick @ internal/child_process.js:766
_combinedTickCallback @ internal/process/next_tick.js:73
_tickCallback @ internal/process/next_tick.js:104
console.ts:136 [Extension Host] [WakaTime] [ERROR] Unknown Error (2); Check your C:\Users\sschewe\.wakatime.log file for more details.

[alanhamlett]

That's good! If the VS Code plugin isn't able to download wakatime-cli through the proxy, it might break the next time you upgrade the WakaTime extension for VS Code since wakatime-cli is stored in the plugin's folder and deleted/re-downloaded when a plugin version's folder is removed after upgrading.

Since v1.1.13 released in 2017 the WakaTime VS Code plugin should be using the proxy value from ~/.wakatime.cfg when downloading wakatime-cli. If the plugin is sending heartbeats but not able to download/update wakatime-cli then that's a bug that we should fix.

[alanhamlett]

Looks like this is the same issue as #11. One fix might be to disable verifying ssl certs, if your proxy is injecting it's own cert.

[mobychan]

By disabling verifying ssl certs do you mean using the no_ssl_verify = true setting?
Because that did not work.

[alanhamlett]

Yep, that would only work if we disable verifying certs in vscode based on that wakatime-cli config.

[nicholasinatel]

I finally got it working again.
Looks like the extension is unable to download the wakatime-cli/core correctly and somehow the previously existing one was removed
I downloaded it directly from the github and extracted it into .vscode\extensions\WakaTime.vscode-wakatime-1.2.1\out
Additionally I updated the plugin by using "Extensions: Check for Updates" because the status page told me there was a newer version available(vscode didn't show this) this changed the extensions version from 1.2.0 to 1.2.1

@mobychan could you please elaborate more on how you managed to do it, i tried following your steps and still nothing, i copy the github to the out folder but the visual studio code see's my version as 1.2.4 and the status page see's it as 1.2.3.
Thank you best regards

[cbb330]

I also had this issue and can offer a possible solution.

My employer tweaked some setting that disables any default certificate CA trust. So to re-enable the trust needed for NodeJS to download the CLI from Github:

• export Github's root CA certificate in PEM format
• set your environment variable 'NODE_EXTRA_CA_CERTS' to filepath of that exported cert
• reload VSCode

More info on that environment variable here.