[WakaTime] [ERROR] Invalid API Key (104); Make sure your API Key is correct!

[wakatime]

[WakaTime] [ERROR] Invalid API Key (104); Make sure your API Key is correct!

[alanhamlett]

Sorry, this was me. 😭 I broke the api key parsing last night, but it's fixed now. The plugin saves your stats and syncs them up the next time the plugin runs (the next time you're typing) so nothing is lost, but still sorry about the frustration it may have caused.

[will-r-wang]

cc Main Issue is: #143.

[fruitbang]

process.env['USERPROFILE']

what i need to do if 'process.env['USERPROFILE']' returns 'undefined'?

[alanhamlett]

We now force Python to use the same home folder as Vscode in v1.1.8, to better fix this issue.

[Bailey-1]

I'm having the same issue with Xcode, VSCode and Vim all on OSX. They were all working great yesterday. Status hasn't seen anything since 9:00pm yesterday.

But at least I'm not the only one.

[alanhamlett]

Can you manually check to make sure the api_key setting in ~/.wakatime.cfg matches your key at https://wakatime.com/settings?

[theophilenz]

No it didn't. I was able to work that out. Thanks a lot. Probably a problem with my $HOME path and my terminal.

[ClaireBrione]

Same too. It appeared that the api_key disappeared from my ~/.wakatime.cfg and I don't know how this happened, but putting it back didn't solve the problem.

Edit: I'm running SublimeText3. Changed my API key, no effect. In debug mode, wakatime says
{"now": "2020/07/27 13:13:27 +0000", "version": "13.0.7", "plugin": "sublime/3211 sublime-wakatime/9.1.2", "time": 1595848375.887897, "caller": "/home/alienor/.config/sublime-text-3/Packages/WakaTime/packages/wakatime/api.py", "lineno": 330, "file": "/home/alienor/.wakatime.log", "level": "WARNING", "message": "{'response_code': 401, 'response_content': u'{\"error\":\"Unauthorized\"}\\n'}"}

[NicksIdeaEngine]

I have this problem via vim. I'll disable the plugin until this gets fixed. I haven't updated anything recently, but tried an update once this problem started this morning. Updates didn't resolve it.

[Juniorpucket]

I think its a general fault cuz i am experiencing the same issue with VSCode.

[rnapoli]

Issue fixed for me. Thanks for fixing it quickly !!!

[theophilenz]

Yes. I did check both of them. They are the same.

[alanhamlett]

With debug mode on, what is the response code and error message printed in your ~/.wakatime.log file?

I'm not seeing any connection from your IP to our API Servers. A proxy is probably returning a 401 response which is the response code WakaTime uses when the api key is wrong. However, in this case it's probably the proxy needing authentication to connect to the internet.

[theophilenz]

The message:

I couldn't find the log file in $HOME.

[alanhamlett]

From Help -> Toggle Developer Tools, what is printed when your run this in Console:
process.env['USERPROFILE']

Does that match the location of your ~/.wakatime.cfg file?

[KipchirchirIan]

I now have this problem and I can't find any solution online that works. How was this solved @theophilenz ??

[YazanKhatib]

I am facing the same issue, It was working before and suddenly broke when I started working today @alanhamlett

[OlivierJM]

same here, it has been working just fine until today(untouched)

[tongrow]

same. I updated api key, but it had no effect

"version": "13.0.7", "plugin": "vscode/1.47.2 vscode-wakatime/4.0.0"

[adekoyejoakinhanmi]

I'm currently experiencing this and this is the error it's showing:

[WakaTime][ERROR] Error: Command failed: /Users/adekoyejoakinhanmi/.vscode/extensions/wakatime.vscode-wakatime-4.0.0/wakatime-cli/wakatime-cli 
--file /Users/adekoyejoakinhanmi/Documents/dev/Verifi/people-ui/components/Nav/index.js --plugin "vscode/1.47.2 vscode-wakatime/4.0.0" 
--alternate-project people-ui --write

[Destaq]

Yup, this has happened to me as well.

[adelchamas96]

yes it's not working for me too i tried generate new api key /reinstall the extension nothing worked. is this a problem with newer vs code version?

[shxfee]

+1

[will-r-wang]

+1 same here. I'm getting [WakaTime] Error 104: Invalid API Key

[xage93]

+1

[qzmlgfj]

The same here.
It happened for about 6 hours ago, with[WakaTime][ERROR] Invalid Api Key (104);
And I've got Error: Command failed: c:\Users\Ant\.vscode\extensions\wakatime.vscode-wakatime-4.0.0\wakatime-cli\wakatime-cli.exe --file c:\Users\Ant\Desktop\VSCode\Markdown\MarkDownWork\blog.md --plugin "vscode/1.47.2 vscode-wakatime/4.0.0" --alternate-project MarkDownWork --config C:\Users\Ant\.wakatime.cfg --log-file C:\Users\Ant\.wakatime.log

[kaka-ruto]

Me too, on Vim. Looks like a bug invalidated all our keys. But no worries @alanhamlett , it happens 😉

[venancioavila]

Me too, on vs code. @alanhamlett incorrect api key.

[giancarlopro]

+1

[dlinkoln]

+1

[pablohdzvizcarra]

I have the same problem with the api key

[rnapoli]

+1
My Wakatime was working before and now it's broken.
I get the WakaTime Error - "WakaTime: Invalid Api Key (104); make sure your Api Key is correct!"
I've double-checked my API key and it's perfectly fine.

[VivekAlhat]

I am facing the similar problem. I regenerated new key and tried with that but still same problem. It was working fine until yesterday.

[tubin]

I have the same problem with the api key

[OlivierJM]

Sorry, this was me. 😭 I broke the api key parsing last night, but it's fixed now. The plugin saves your stats and syncs them up the next time the plugin runs (the next time you're typing) so nothing is lost, but still sorry about the frustration it may have caused.

I can confirm it is resolved. Thank you