Unknown error after last upgrade about atom-wakatime

[YummyOreo]

@BestSithInEU @OreoDivision if you remove no_ssl_verify = true from ~/.wakatime.cfg then restart Atom to get the latest wakatime-cli v1.18.9, does that also fix the issue for you?

sorry for the late response but that worked thanks

[nhend]

I am also experiencing this error with the same behavior in the dev console regarding 1.7.4 updates. Forcing 1.7.1 in .wakatime.cfg also fixed things for me.

[YummyOreo]

For me, forcing 1.7.1 does not work, in the .wakatime.log it shows {"caller":"/home/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/today/today.go:44","func":"Run","level":"fatal","message":"failed fetching summaries from api: failed to make request to \"https://api.wakatime.com/api/v1/users/current/summaries\": Get \"https://api.wakatime.com/api/v1/users/current/summaries?end=2021-06-13&start=2021-06-13\": x509: certificate signed by unknown authority","now":"2021-06-13T15:03:18-05:00","version":""} {"caller":"/home/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/heartbeat/heartbeat.go:47","func":"Run","level":"fatal","message":"failed to send heartbeat(s): failed to send heartbeats via api client: failed making request to \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": Post \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": x509: certificate signed by unknown authority","now":"2021-06-13T15:03:21-05:00","version":""} {"caller":"/home/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/heartbeat/heartbeat.go:47","func":"Run","level":"fatal","message":"failed to send heartbeat(s): failed to send heartbeats via api client: failed making request to \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": Post \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": x509: certificate signed by unknown authority","now":"2021-06-13T15:03:21-05:00","version":""} {"caller":"/home/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/today/today.go:44","func":"Run","level":"fatal","message":"failed fetching summaries from api: failed to make request to \"https://api.wakatime.com/api/v1/users/current/summaries\": Get \"https://api.wakatime.com/api/v1/users/current/summaries?end=2021-06-13&start=2021-06-13\": x509: certificate signed by unknown authority","now":"2021-06-13T15:05:14-05:00","version":""} {"caller":"/home/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/heartbeat/heartbeat.go:47","func":"Run","level":"fatal","message":"failed to send heartbeat(s): failed to send heartbeats via api client: failed making request to \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": Post \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": x509: certificate signed by unknown authority","now":"2021-06-13T15:05:19-05:00","version":""}

• Fixed using wakatime/wakatime-cli#432

[alanhamlett]

@OreoDivision that's a bug where our new Go version of wakatime-cli isn't working correctly with custom proxy MITM certs. We're working on fixing it with wakatime/wakatime-cli#385, but for now you can get yours working by disabling SSL verification in your ~/.wakatime.cfg file:

no_ssl_verify = true

[BestSithInEU]

@OreoDivision that's a bug where our new Go version of wakatime-cli isn't working correctly with custom proxy MITM certs. We're working on fixing it with wakatime/wakatime-cli#385, but for now you can get yours working by disabling SSL verification in your ~/.wakatime.cfg file:

no_ssl_verify = true

This is not worked for me.

[YummyOreo]

@OreoDivision that's a bug where our new Go version of wakatime-cli isn't working correctly with custom proxy MITM certs. We're working on fixing it with wakatime/wakatime-cli#385, but for now you can get yours working by disabling SSL verification in your ~/.wakatime.cfg file:

no_ssl_verify = true

Okay, that was the fix that I used

[alanhamlett]

@BestSithInEU @OreoDivision if you remove no_ssl_verify = true from ~/.wakatime.cfg then restart Atom to get the latest wakatime-cli v1.18.9, does that also fix the issue for you?