20
The Previous Update Broke Our Bot And I Don't Know Why
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Mar 2024
20 points (100.0% liked)
Lemmy.world Support
3212 readers
2 users here now
Lemmy.world Support
Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.
This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.
This community is subject to the rules defined here for lemmy.world.
To open a support ticket
You can also DM https://lemmy.world/u/lwreport or email report@lemmy.world (PGP Supported) if you need to reach our directly to the admin team.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world
founded 1 year ago
MODERATORS
Just a shot in the dark but I've seen some people say something about one of the updates logging out accounts as a security measure. Assuming the recent updates didn't change auth stuff, maybe it's possible that it just needs to refresh the token? A glance at the code looks like it will keep trying to use the same JWT as long as it's still valid, and fall back to getting a new JWT using username/password. So deleting the JWT would make it get a new one. (Iirc JWTs have an embedded expiration, but the server can invalidate it so the bot code could in theory not know that the server can invalidate it)
Assuming you're getting the incorrect login error from Lemmy. Idk maybe I'm way off base with my guess.
Thank you for responding.
[ERROR] [LEMMY] Error while trying to login, host might be down
[ERROR] [SCHEDULER] An error occurred: Error: incorrect_login
Is the error.
I have attempted to add a different username and password and it didn't work. Would that get a new JWT?
If not how do I delete it?
Hmm maybe it's not that simple then. It doesn't look like the JWT is stored so it's probably trying to get a new one when started. The other possible culprit would be if you need to use lemmy-js-library with a major version matching the Lemmy server version.
Assuming the server updated to 0.19.0, the version used by the bot is 0.18.0. You would just need to edit package.json so that the lemmy-js-client line reads:
"lemmy-js-client": "^0.19.0",
Then running npm install or yarn install (or whatever command you used to install dependencies previously)
After suggested change:
PS C:\Users***********\Botlt> npm install
npm ERR! code EJSONPARSE
npm ERR! path C:\Users********\Botlt/package.json
npm ERR! JSON.parse Unexpected token "โ" (0x201C) in JSON at position 976 while parsing near "... "lemmy-js-client": โ^0.19.0โ,\r\n "lin..."
npm ERR! JSON.parse Failed to parse JSON data.
npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.
I went back in and changed it to:
It will now run again, but same incorrect_login error.
I think that's part of the solution, I skimmed some of the forks and found one that updated the lemmy-js-client to 0.19.2-alpha.3 but they made some code changes too to the authentication code. So maybe trying that fork is worth a shot: https://github.com/thepaperpilot/BotIt
Last changes were last month on that fork
Thanks so much for your help.
I am not programmer, and I didn't even realize there was a fork. Let me root around in there and see what I can find out tomorrow.
Thanks again.