Hamuko / anifunnel

Update your Anilist watching list automatically using Plex webhooks.
Apache License 2.0
22 stars 0 forks source link

Software still maintained? #1

Closed bogdans92 closed 1 year ago

bogdans92 commented 1 year ago

Hello,

Curious if you are sitll maintaining the docker file.

Did a few things:

  1. Tried receiving my token from the link in the description:
    • {"error":{"status":404,"messages":["API route not found."]}} this is the response code, i ended up getting the token (which i think is correct and added it myself to the docker image)
    • altough it gave the above message i also checked and saw that in my settings the anifunnel application has rights
      1. Ran the docker image with the token & configured the webhook.
    • on the plex console i'm getting the following error: Webhook: Error delivering payload to http://127.0.0.1:32400/: 401
    • i tried also without the / at the ending even though it was not in the documentation Unfortunately i don't know how to enable debugging on the docker image itself, no errors on that.

This is the output: 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch] 🔧 Configured for release. 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] address: 0.0.0.0 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] port: 8000 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] workers: 16 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] max blocking threads: 512 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] ident: Rocket 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] IP header: X-Real-IP 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] limits: bytes = 8KiB, data-form = 2MiB, file = 1MiB, form = 32KiB, json = 1MiB, msgpack = 1MiB, string = 8KiB 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] temp dir: /tmp 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] http/2: true 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] keep-alive: 5s 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] tls: disabled 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] shutdown: ctrlc = true, force = true, signals = [SIGTERM], grace = 2s, mercy = 3s 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] log level: critical 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] cli colors: true 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch] 📬 Routes: 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] (scrobble) POST / 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] (managementredirect) GET / 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] (management) GET /admin 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::_] (managementedit) POST /admin/edit/ 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch] 📡 Fairings: 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] Shield (liftoff, response, singleton) 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::launch::] Templating (ignite, liftoff) 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::shield::shield] 🛡️ Shield: 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::shield::shield::] X-Content-Type-Options: nosniff 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::shield::shield::] Permissions-Policy: interest-cohort=() 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket::shield::shield::] X-Frame-Options: SAMEORIGIN 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket_dyn_templates::fairing] 📐 Templating: 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket_dyntemplates::fairing::] directory: tmp/.tmpc5DHa1 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z INFO [rocket_dyntemplates::fairing::] engines: ["tera"] 2023-11-02 21:20:57 2023-11-02T19:20:57.143Z WARN [rocket::launch] 🚀 Rocket has launched from http://0.0.0.0:8000

Hamuko commented 1 year ago

Yeah, the Dockerfile is still maintained since that's how I run anifunnel on my server.

At least that log output appears like anifunnel is launching itself correctly. Trailing slash should definitely work, since I'm currently using http://ip.address:8010/ for my Plex installation. Are you able to reach the management UI at /admin?

bogdans92 commented 1 year ago

yes, the /admin is reachable. It is also finding the list of anime that is on plex.

Hamuko commented 1 year ago

anifunnel doesn't actually look up what anime is on your Plex instance. It fetches what anime you have on Anilist, and then listens to Plex webhooks for any events that match your Anilist watching list. At no point will it actually see what your Plex library has in it.

But if /admin is reachable and it has the list of anime that you have on Anilist, then it sounds like the API token is correct and the server is running fine. My guess would be that the connection between the Plex instance and your anifunnel instance isn't either set up correctly, or just doesn't work. You should see anifunel produce log output if it's receiving webhooks from Plex if you do basically anything in Plex (start watching something, stop watching something, etc).

2023-11-02T19:58:40.615Z INFO  [rocket::server] POST / multipart/form-data:
2023-11-02T19:58:40.615Z INFO  [rocket::server::_] Matched: (scrobble) POST /
2023-11-02T19:58:40.615Z INFO  [anifunnel] Webhook is not actionable
2023-11-02T19:58:40.615Z INFO  [rocket::server::_] Outcome: Success
2023-11-02T19:58:40.615Z INFO  [rocket::server::_] Response succeeded.
bogdans92 commented 1 year ago

Got it. Thank you, currently trying to do that, i think the webhook is also set up correctly, i'll try fixing it and come back (i'll start off by changing the plex webserver port ), hopefully afterwards it should (in theory) work also for the TV.

Thank you for the quick response

Hamuko commented 1 year ago

Note that the connection is between the Plex server and anifunnel. I presume the TV you're referring to is just a Plex client, and that won't actually communicate with anifunnel.

bogdans92 commented 1 year ago

You are right, what i was thinking is that the client when it connects to the server it should also do a request to that therefore triggering the webhook. From my tests so far it seems the error for the webhook is also triggered when i try it from the TV (for the desktop tbh i use Taiga).

bogdans92 commented 1 year ago

Ok, status update. Ofc this is a misconfiguration on my side. The webhook needs to be to anifunnel port not to the plex server.... (long day) Both from TV/PC i now get the expected result: 2023-11-02 22:17:12 2023-11-02T20:17:12.298Z INFO [rocket::server::] Matched: (scrobble) POST / 2023-11-02 22:17:12 2023-11-02T20:17:12.298Z INFO [anifunnel] Webhook is not actionable 2023-11-02 22:17:12 2023-11-02T20:17:12.298Z INFO [rocket::server::] Outcome: Success 2023-11-02 22:17:12 2023-11-02T20:17:12.298Z INFO [rocket::server::_] Response succeeded.

Unfortunately nothing is updated yet in my list of anime. I'll keep on checking and update

Hamuko commented 1 year ago

It'll update once you finish watching an episode (and it meets the update criteria, see the README file for details).

bogdans92 commented 1 year ago

I can confirm it works also from the TV (as one of the anime has updated). i just need to re-read the documentation and understand how to configure it properly. Thank you for all the help.