search

psyko-gh / overcrawlrr

Automated smart movies request for Overseerr/Jellyseerr
https://psyko-gh.github.io/overcrawlrr/latest/
MIT License
56 stars 0 forks source link

404 Error #16

Closed dhrandy closed 1 month ago

dhrandy commented 1 month ago

[ 2024-08-27 22:12:42.801 ] info: Loading settings... [ 2024-08-27 22:12:42.869 ] info: Settings loaded successfully from /config/settings.yaml [ 2024-08-27 22:12:42.870 ] info: Successfully loaded ruleset 'New great movie' with 2 rules [ 2024-08-27 22:12:42.873 ] info: Registered Discover job. Next run: Wed Aug 28 2024 03:30:00 GMT+0000 (Coordinated Universal Time) [ 2024-08-27 22:12:42.874 ] info: Testing overseerr connection... [ 2024-08-27 22:12:42.879 ] info: Server is listening at http://localhost:5056 [ 2024-08-27 22:12:42.896 ] error: Request failed with status code 404

Docker Compose

services: overcrawlrr: image: ghcr.io/psyko-gh/overcrawlrr:latest container_name: overcrawlrr restart: unless-stopped ports:

settings.yaml

config: overseerr: apiUrl: http://redacted:5056/api/v1 user: Overcrawler # required password: redacted # required dryRun: false # Optional - dryRun will not send requests to Overseerr discovery:

Required

cron: '30 3 * * *'
# Required - the overseer streams to search through
# Possible values: upcoming, popular, trending
streams:
  - upcoming
  - popular
  - trending
# Required - the name of the ruleset used to evaluate movies
ruleset: New great movie # References the ruleset below

rulesets: # Indentation was wrong

psyko-gh commented 1 month ago

status code 404 = most likely, your overseerr apiUrl is not correct.

Also not related, but will be an issue after you solve the 404, OVERSEERR_USER=Overcrawler user should be the email associated with the account

neilerua973 commented 1 month ago

Hello Psyko,

I also have the 404 when contacting overseerr. I tried with the local IP and my domain. I can ping & nslookup my domain from the overcrawlrr container.

Maybe it's related to overseerr because I also have 404 from my overseerr API when I call /auth/local with curl from my PC: `<!DOCTYPE html>

Error 
Cannot POST /auth/local
` However, I got 200 when I called `/status`, but it returns the login page in HTML... 😅 Btw, thank you for your work, really useful app that needs to be known !
psyko-gh commented 1 month ago

Btw, thank you for your work, really useful app that needs to be known !

@neilerua973 Thank you. It's not a big project, but I thought it might be useful to others :)

Did you try to curl http://overseerr_ip:5056/auth/local or http://overseerr_ip:5056/api/v1/auth/local ? The first one will give you a 404. The second should work. (I was wrong in https://github.com/psyko-gh/overcrawlrr/issues/11#issuecomment-2316253889)

If you're curl'ing the .../api/v1/auth/local, with a GET method, it should reply a JSON like {"message":"GET method not allowed","errors":[{"path":"/api/v1/auth/local","message":"GET method not allowed"}]}

I'll update the code to log the Overseerr url when testing it. It might help.

dhrandy commented 1 month ago

It’s working now. At least the first search, which didn’t download yet because I had some strict search criteria. I had the wrong port and wasn’t using the full email. I switched mine to searching once a week instead of a day. Once working I’ll probably switch to searching once a months. Thanks for this app!

dhrandy commented 1 month ago

This can close now.

psyko-gh commented 1 month ago

@dhrandy I'm happy to read that it works

there is a fix in preparation. The score predicate is not working properly when using score: above X. I recommend using score: above X/10. I'm not sure how badly it can impact your searches.

Having it run once a month is probably enough indeed, but the current job only analyses the 50 last movies for the trends in upcoming/trending/popular stream. I might add an option to specify the number of movies to evaluate...

neilerua973 commented 1 month ago

@psyko-gh

Did you try to curl http://overseerr_ip:5056/auth/local or http://overseerr_ip:5056/api/v1/auth/local ? The first one will give you a 404. The second should work. (I was wrong in #11 (comment))

Good point, I just frogot to add /api/v1, thank you ! 😁