Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Overseerr support #189

Open
19wolf opened this issue Dec 14, 2020 · 19 comments
Open

[Feature Request] Overseerr support #189

19wolf opened this issue Dec 14, 2020 · 19 comments
Labels
approved Enhancement or request that was approved to be worked on enhancement New feature or request in-next-release In the next release

Comments

@19wolf
Copy link

19wolf commented Dec 14, 2020

Overseerr is a new alternative to Ombi, and should be supported by Varken.

@samwiseg0
Copy link
Member

samwiseg0 commented Dec 14, 2020

I agree. I would like to see where the project goes. I will see if I can work on it in the near future. The developer has been inundated with new folks.

@samwiseg0 samwiseg0 added approved Enhancement or request that was approved to be worked on enhancement New feature or request labels Dec 14, 2020
@Maxtoid
Copy link

Maxtoid commented Mar 5, 2021

I too would very much love Overseerr support for this if possible at some point. After years on Ombi, I have cutover my production requests system to Overseerr as it is so stable and SO much better all around than Ombi.

@redredbeard
Copy link

redredbeard commented Aug 4, 2021

Added support in a pull request - #210

@samwiseg0 samwiseg0 added the in-next-release In the next release label Jan 15, 2022
@samwiseg0
Copy link
Member

Overseer support has been added in develop. Please test and let us know if there are any issues.

@modem7
Copy link

modem7 commented Mar 29, 2022

I just installed the development version yesterday and added an Overseerr configuration. I don't see any errors about Overseerr in the logs, and plenty of "WARNING : overseerr : No data to send to influx for overseerr-latest-requests instance, discarding." Most likely due to no new requests, but there was a couple new requests yesterday and some requests completed yesterday.

So far I don't see an "Overseerr" table in the database. Just Ombi and the other configured services.

I've just done the same, but got it working.

Here's my compose file snippet:

  # Varken - Application to aggregate data from the Plex ecosystem
  varken:
    hostname: varken
    container_name: Varken
    image: boerderij/varken:develop
    networks:
      - isonet
      - isolated
    volumes:
      - $USERDIR/TIGVStack/Varken:/config
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - TZ=$TZ
      - VRKN_GLOBAL_SONARR_SERVER_IDS=$VRKN_GLOBAL_SONARR_SERVER_IDS
      - VRKN_GLOBAL_RADARR_SERVER_IDS=$VRKN_GLOBAL_RADARR_SERVER_IDS
      - VRKN_GLOBAL_LIDARR_SERVER_IDS=$VRKN_GLOBAL_LIDARR_SERVER_IDS
      - VRKN_GLOBAL_TAUTULLI_SERVER_IDS=$VRKN_GLOBAL_TAUTULLI_SERVER_IDS
      - VRKN_GLOBAL_OMBI_SERVER_IDS=$VRKN_GLOBAL_OMBI_SERVER_IDS
      - VRKN_GLOBAL_SICKCHILL_SERVER_IDS=$VRKN_GLOBAL_SICKCHILL_SERVER_IDS
      - VRKN_GLOBAL_MAXMIND_LICENSE_KEY=$VRKN_GLOBAL_MAXMIND_LICENSE_KEY
      - VRKN_INFLUXDB_URL=$VRKN_INFLUXDB_URL
      - VRKN_INFLUXDB_PORT=$VRKN_INFLUXDB_PORT
      - VRKN_INFLUXDB_SSL=$VRKN_INFLUXDB_SSL
      - VRKN_INFLUXDB_VERIFY_SSL=VRKN_INFLUXDB_VERIFY_SSL
      - VRKN_INFLUXDB_USERNAME=$VRKN_INFLUXDB_USERNAME
      - VRKN_INFLUXDB_PASSWORD=VRKN_INFLUXDB_PASSWORD
      ~~Other variables not relevant to Overseer~~
      - VRKN_OVERSEERR_1_URL=$VRKN_OVERSEERR_1_URL
      - VRKN_OVERSEERR_1_APIKEY=$VRKN_OVERSEERR_1_APIKEY
      - VRKN_OVERSEERR_1_SSL=$VRKN_OVERSEERR_1_SSL
      - VRKN_OVERSEERR_1_VERIFY_SSL=$VRKN_OVERSEERR_1_VERIFY_SSL
      - VRKN_OVERSEERR_1_GET_REQUEST_TOTAL_COUNTS=$VRKN_OVERSEERR_1_GET_REQUEST_TOTAL_COUNTS
      - VRKN_OVERSEERR_1_REQUEST_TOTAL_RUN_SECONDS=$VRKN_OVERSEERR_1_REQUEST_TOTAL_RUN_SECONDS
      - VRKN_OVERSEERR_1_GET_LATEST_REQUESTS_TO_FETCH=$VRKN_OVERSEERR_1_GET_LATEST_REQUESTS_TO_FETCH
      - VRKN_OVERSEERR_1_NUM_LATEST_REQUESTS_SECONDS=$VRKN_OVERSEERR_1_NUM_LATEST_REQUESTS_SECONDS
    logging:
      driver: "json-file"
      options:
        max-size: 10m
        max-file: "3"
    # labels:
    #   - backup
    depends_on:
      - influxdb
    restart: always

And you'll need to change values in Grafana as well. I just modified the Ombi ones.

image

Be aware that there seems to be a typo here which may cause issues. It seems that it should be SECONDS not SECONDSS. Might be one for @samwiseg0 to address.

(Also this probably needs renaming to overseer.domain.ltd)

@modem7
Copy link

modem7 commented Mar 29, 2022

Actually, my log reading skill must've sucked the first time around.

2022-03-29 14:51:14 : DEBUG : connectionpool : Resetting dropped connection: .1.20 2022-03-29 14:51:14 : DEBUG : connectionpool : http://.1.20:5055 "GET /api/v1/request/count HTTP/1.1" 403 75 2022-03-29 14:51:14 : DEBUG : connectionpool : http://********.1.20:5055 "GET /api/v1/request?take=10&filter=all&sort=added HTTP/1.1" 403 75 2022-03-29 14:51:14 : WARNING : overseerr : No data to send to influx for overseerr-latest-requests instance, discarding.

I've tried with address:port, fqdn:port, https fqdn via HA Proxy with SSL and no verify. Triple checked the API key ... When I try the configured api address + "/api/v1/request?take=10&filter=all&sort=added" in a browser I get a full JSON response, strangely without even providing an API key.

I've got this as my env vars (just in case it helps):

VRKN_OVERSEERR_1_URL="192.168.0.254:5055"
VRKN_OVERSEERR_1_APIKEY="hcxt2lvI2HmPtas9kit5haB6R8mzaQSEMJBsZQumsSGytQ6ue5xAMBxCKiUeviPU4X34"
VRKN_OVERSEERR_1_SSL="false"
VRKN_OVERSEERR_1_VERIFY_SSL="false"
VRKN_OVERSEERR_1_GET_REQUEST_TOTAL_COUNTS="true"
VRKN_OVERSEERR_1_REQUEST_TOTAL_RUN_SECONDS="30"
VRKN_OVERSEERR_1_GET_LATEST_REQUESTS_TO_FETCH="10"
VRKN_OVERSEERR_1_NUM_LATEST_REQUESTS_SECONDS="300"

(APIKEY value was generated randomly with pwgen for the above paste)

@samwiseg0

This comment was marked as off-topic.

@samwiseg0

This comment was marked as off-topic.

@a351must2
Copy link

a351must2 commented Mar 31, 2022

I cleaned up my "off-topic" comments. I'd like to confirm this is working perfectly for me with Overseer now ... (my issue was caused by an "=" at the end of the API key getting dropped when pasting into the config)

@samwiseg0
Copy link
Member

@modem7 Both typos should be fixed. Thanks for the report.

@djsly

This comment was marked as off-topic.

@samwiseg0

This comment was marked as off-topic.

@alphatwins
Copy link

Issues are not working(as I can see, they are not implemented yet)
Would it be possible to copy the issues class from ombi, and change them to overseerr?
I have no experience with API, so no clue if it would actually work. Tried to have a look in the python files, but I hope some of you can fix it :p

@Jarsky
Copy link

Jarsky commented Apr 23, 2022

Overseer support has been added in develop. Please test and let us know if there are any issues.

Working good here mostly.

I'm having 2 issues.

  • It doesnt appear that it's scraping "Issues" ? I cant see anything in the Debug log
  • Also I'm seeing this. The "Pending" movies have a Status: 3, while this "Available" movie has a Status: 5. It seems to be showing the Status number rather than what is translates too. Seems theres a translation missing somewhere?

image

EDIT: Nevermind, shouldnt be there so I just excluded it

image

@BRTPOB

This comment was marked as off-topic.

@samwiseg0

This comment was marked as off-topic.

@rock7632

This comment was marked as off-topic.

@samwiseg0

This comment was marked as off-topic.

@wranglatang
Copy link

Morning will the overseer feature be pulled into the main branch of Varken - From reading above it appears that it is working?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Enhancement or request that was approved to be worked on enhancement New feature or request in-next-release In the next release
Projects
None yet
Development

No branches or pull requests