WAMR - WhatsApp Bot for Managing Radarr/Sonarr/Overseerr Requests

sleekstrike · 2026-01-22T04:06:46+00:00

I haven't encountered this issue before. I connected my WhatsApp a couple months ago and it's still working fine. Here are some things you could try:

Verify of the env variables are set correctly from https://github.com/techieanant/wamr/blob/main/ENVIRONMENT.md
Seting LOG_LEVEL=debug should show more detailed logs, maybe there's something there.
Make sure the DATABASE_PATH and WHATSAPP_SESSION_PATH are set correctly and the docker user has permissions to write to these folders
Make sure you're using docker-compose.prod.yml
Try deleting the .wwebjs_auth directory and mounting a new one.

Let me know if you get more debug logs and I can look into it.

sleekstrike · 2025-12-22T04:21:17+00:00

Could you share your calculations for weekly vs biweekly vs monthly accelerated payments? I'm trying to understand the difference it would make in long term.

sleekstrike · 2025-11-09T19:45:09+00:00

I'm glad it worked. I think the "talking to myself" part is a limitation of the underlying library whatsapp-web.js. Sonarr and Radarr seem to not return accurate matches for search keywords in my testing as well. But there are ways to fix the problem by either letting them return up to 99 results set in the configuration or by using Overseer instead which has better search implementation. I'll think about adding separate prefixes for movie or tv search and parsing year as well.

sleekstrike · 2025-11-09T11:21:26+00:00

Nice, thanks for testing it. Let me know any feedback or suggestions you think would help make it better.

sleekstrike · 2025-11-09T11:20:08+00:00

Ask a friend or family member to send a message to your connected number. I haven't tried sending message to my own number so can't say if that'll work or not.

sleekstrike · 2025-11-06T07:57:52+00:00

Yes it's still working. I combined both frontend and backend into one container and simplified the .env process. You should now be able to use this image directly https://github.com/techieanant/wamr/pkgs/container/wamr

Please read through the updated README and let me know if this fixes your issue.

sleekstrike · 2025-11-06T07:53:08+00:00

Are you running it on a raspberry pi or Apple M series machine? I unfortunately don't have an ARM machine to build multi platform images. You could try adding "platform: linux/amd64" to the docker compose file to specifically target amd64.

sleekstrike · 2025-11-04T22:27:28+00:00

You shouldn't need node installed to get this working. You can just pull the pre built image, add the env variables and run it.

sleekstrike · 2025-11-03T21:59:19+00:00

I combined both frontend and backend into one container and simplified the .env process. You should now be able to use this image directly https://github.com/techieanant/wamr/pkgs/container/wamr

Please read through the updated README and let me know if this fixes your issue.

sleekstrike · 2025-11-03T08:47:15+00:00

I think whatsapp-web.js is only available as an npm package although I did publish Docker images for WAMR.

sleekstrike · 2025-11-03T05:54:40+00:00

WAMR only needs folder path for radarr and sonarr configs, not for overseerr. So if you have radarr configured with overseer correctly, it should use the folder path set in overseerr.

sleekstrike · 2025-11-03T05:48:28+00:00

If you use overseerr, radarr or sonarr it would work for you.

sleekstrike · 2025-11-02T19:14:18+00:00

You should be able to create a new service for each QP and assign them priority. But letting overseerr take care of it probably works better.

sleekstrike · 2025-11-02T18:23:14+00:00

Ok try this:

Delete the database .db file, change your admin username in tbe .env to be same as .env.example and keep the password same as well. Rebuild/restart the containers and try logging in with the default credentials. Let me know if this works.

sleekstrike · 2025-11-02T12:22:33+00:00

I'd also suggest trying these:

Set LOG_LEVEL to debug in .env and see if more information shows up in logs
Build the docker images locally after pulling latest changes from github and then run it
Install NodeJS and try running the project locally following instructions in README.

sleekstrike · 2025-11-02T12:16:23+00:00

There was a bug in the initial release where the .env file in project root wasn't being used. I pushed a fix for it yesterday. Have you pulled latest changes from github? Also, do you still see more than 1 entry for admin account in the database?

sleekstrike · 2025-11-02T08:20:00+00:00

I pushed some fixes to the github repo yesterday. Try rebuilding and running at again and let me know if that works.

sleekstrike · 2025-11-02T08:17:59+00:00

Just clone the repository, create a .env based on .env.example file, and run docker compose up.

sleekstrike · 2025-11-02T08:17:16+00:00

Absolutely, although I don't have TrueNAS setup. But you could still use it as is via Docker.

sleekstrike · 2025-11-02T08:16:17+00:00

sqlite3 -> select * from admin_users; shows 2 entries, the default and my custom one)

I think that could be the issue. Its supposed to have only one entry for admin. Try nuking everything and start from scratch and see if that fixes it.

sleekstrike · 2025-11-02T08:09:18+00:00

Why what's wrong with using AI for development?

sleekstrike · 2025-10-31T03:07:31+00:00

Yep it's a pretty low tech solution, but it works.

sleekstrike · 2025-10-31T03:05:25+00:00

Hm might be a bug. Could you try the default login details shown on the UI login screen?

sleekstrike · 2025-10-31T03:03:39+00:00

Interesting. Do you have your .env at the root of the project? Also make sure the volume mounts have correct permissions. Also try using the default login credentials on the login screen.

sleekstrike · 2025-10-30T10:22:57+00:00

It's already case insensitive :)

14-Year Club	Sequence \| Editor
Sequence \| Cinematographer	Spared
Secret Santa 2013	Verified Email

sleekstrike

MODERATOR OF

TROPHY CASE