Can confirm. On version 1.33.1 authentication using Plex works as intended.

@rs5050 Were you ever able to figure out what was causing your container size to be so large? I seem to be running into a similar issue, my container is using up 3.44GB, which seems large.

On 10/15/2023 at 4:33 PM, shaihulud said:

@rs5050 Were you ever able to figure out what was causing your container size to be so large? I seem to be running into a similar issue, my container is using up 3.44GB, which seems large.

I am having the same issue, but not sure what is using so much space. My container is showing almost exactly the same as yours:

 

Name                                              Container                Writable                 Log

binhex-overseerr                                  3.48 GB                  1.22 GB                  340 MB

On 11/16/2023 at 5:10 PM, BudgetAudiophile said:

I am having the same issue, but not sure what is using so much space. My container is showing almost exactly the same as yours:

 

Name                                              Container                Writable                 Log

binhex-overseerr                                  3.48 GB                  1.22 GB                  340 MB

Yeah, seeing the exact same numbers for container/writable size, it's 2x as big as any other docker I have running.  Seems way too big for a docker that shouldn't be storing any large data (media or large files).

 

You might want to check your log settings, 340MB worth of logs is a TON of logs, lol.  Mine is <30MB

Edited January 5, 20242 yr by worldspawn

@binhex

 

same here. but i also think the other are pretty big. 

 

for example i just installed krusader a few hours ago and it is pretty big. i am wondering if these should be that big?

 

31 minutes ago, derjp said:

i am wondering if these should be that big?

 

On 1/5/2024 at 6:41 PM, worldspawn said:

Seems way too big for a docker that shouldn't be storing any large data (media or large files).

The base OS i use is not optimised for docker usage (rolling distro for a start) thus the images are larger than other base OS's such as Alpine, but there are advantages too. In short there is nothing i can do to optimise the image over what it currently is, do keep in mind though that the size shown in the screenshot is not the size you download on update (or size on disk), firstly its compressed and secondly and more importantly there is sharing of layers, its typically more around the 450MB range.

If it really annoys you then the only option is to switch to another image, LSIO use Alpine so the container size will be smaller.

Setup - binhex-radarr, binhex-sonarr, binhex-overseerr and requestrr w/discord.
- I can request tv shows from requestrr/discord and sonarr downloads fine.
- I cant request movies from requestrr/discord to radarr but can from overseer directly. 

Anyone else run into this?

I have had some issues with my Unraid not related to Overseerr, but have gotten them straightened out. Now, when setting up Nginx Proxy Manager to point to Overseerr, I get the default page using the URL I have set up. Did a cURL from that container to the Overseerr one and I get a 307 temporary redirect response. Opening the Overseerr container using IP:Port works fine, and NPM shows the server as online. Here is the output from cURL:

HTTP/1.1 307 Temporary Redirect
X-Powered-By: Express
Location: /login
Date: Sun, 09 Jun 2024 17:00:35 GMT
Connection: keep-alive
Keep-Alive: timeout=5
Transfer-Encoding: chunked

 

Both NPM and Overseerr were working correctly previously, for about a month, and now this is the only response I get between the two. I thought I had the same settings that I had before for both containers but I must have missed something to cause this redirect.

I haven't found any quick solutions for this, but I don't think it's an issue with NPM as other proxies are working fine (Plexpass, Tautulli, and others) and I don't know if it's just the binhex-overseerr container with a problem because my Homarr container is doing the same thing.

If anyone has any suggestions, I'd really appreciate them!

1 hour ago, calabriel said:

I have had some issues with my Unraid not related to Overseerr, but have gotten them straightened out. Now, when setting up Nginx Proxy Manager to point to Overseerr, I get the default page using the URL I have set up. Did a cURL from that container to the Overseerr one and I get a 307 temporary redirect response. Opening the Overseerr container using IP:Port works fine, and NPM shows the server as online. Here is the output from cURL:

HTTP/1.1 307 Temporary Redirect
X-Powered-By: Express
Location: /login
Date: Sun, 09 Jun 2024 17:00:35 GMT
Connection: keep-alive
Keep-Alive: timeout=5
Transfer-Encoding: chunked

 

Both NPM and Overseerr were working correctly previously, for about a month, and now this is the only response I get between the two. I thought I had the same settings that I had before for both containers but I must have missed something to cause this redirect.

I haven't found any quick solutions for this, but I don't think it's an issue with NPM as other proxies are working fine (Plexpass, Tautulli, and others) and I don't know if it's just the binhex-overseerr container with a problem because my Homarr container is doing the same thing.

If anyone has any suggestions, I'd really appreciate them!

TBH you are better asking about this in the Nginx Proxy Manager support thread you will get more replies as the issue is around NPM and not the Overseerr Docker image.

Hello, Im trying to set up overseerr in a docker environment. The first time I tried it, the container was set up ok and I was able to enter the UI. However, I had to re-install and update the host PC, and now any time I try to create the container, it gets stuck at [info] Deleting files in /tmp (non recursive)... step. I am not able to even get into the UI (but can get into the container console). I'm running this with the deluge vpn container, and have overseerr port added to the deluge port and vpn ports. I also created a new user specifically for this container on the host. I tried running it as a "stand alone" container outside of the vpn virtual network, tried running it as root UID 0, clearing the containers using docker system purge -a command. Even tried installing older versions, to no avail. Any recommendations on what I should try first?

3 hours ago, minihq said:

Hello, Im trying to set up overseerr in a docker environment. The first time I tried it, the container was set up ok and I was able to enter the UI. However, I had to re-install and update the host PC, and now any time I try to create the container, it gets stuck at [info] Deleting files in /tmp (non recursive)... step. I am not able to even get into the UI (but can get into the container console). I'm running this with the deluge vpn container, and have overseerr port added to the deluge port and vpn ports. I also created a new user specifically for this container on the host. I tried running it as a "stand alone" container outside of the vpn virtual network, tried running it as root UID 0, clearing the containers using docker system purge -a command. Even tried installing older versions, to no avail. Any recommendations on what I should try first?

if you have switched user then you will need to reset permissions for the container, delete the file /config/perms.txt then restart/start the container.

Yes, anytime I was switching users I was doing this. So after about 50 minutes of "deleting /tmp" it loaded in. This step: [info] Deleting files in /tmp (non recursive)...

Edited July 23, 20241 yr by minihq

Any idea on how to customize Overseerr like the logo? I've read some posts about it but nothing seems to help. Or at least how to get into the Overseerr file structure to customize certain things?

Any chance for a binhex-jellyseerr?

I am getting an error when trying to pull the docker image not only for overseerr but also readarr

 

Unable to find image 'ghcr.io/binhex/arch-overseerr:latest' locally
docker: Error response from daemon: Head "https://ghcr.io/v2/binhex/arch-overseerr/manifests/latest": unauthorized.

 

14 hours ago, seriuzbuzinez said:

I am getting an error when trying to pull the docker image not only for overseerr but also readarr

 

Unable to find image 'ghcr.io/binhex/arch-overseerr:latest' locally
docker: Error response from daemon: Head "https://ghcr.io/v2/binhex/arch-overseerr/manifests/latest": unauthorized.

 

this should now be fixed, please try again.

Hey! Overseerr just got an update after like two years lol, would love if it could get updated <3

2 hours ago, JoshuaH15 said:

Hey! Overseerr just got an update after like two years lol, would love if it could get updated <3

Tis done, click 'check for updates' or do a 'force update'.

Thanks for that binhex!

Tried the new update, I'm guessing I'm just doing something wrong/inexperienced, but the container stops a few seconds after starting with:

Exited (143)

 

And this is the only thing I see in the log: 

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2025-03-31 17:33:51.950122 [info] Host is running unRAID
2025-03-31 17:33:52.040918 [info] System information: Linux ea5c2141a22c 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux
2025-03-31 17:33:52.129194 [info] Image tags: BASE_RELEASE_TAG=2025022801,IMAGE_RELEASE_TAG=1.34.0-1-01
2025-03-31 17:33:52.238200 [info] PUID defined as '99'
2025-03-31 17:33:54.226123 [info] PGID defined as '100'
2025-03-31 17:33:55.839642 [info] UMASK defined as '000'
2025-03-31 17:33:55.930396 [info] Permissions already set for '/config'
2025-03-31 17:33:56.055143 [info] Deleting files in /tmp (non recursive)...
[WARN] 2025-03-31 17:33:58 :: '/config/overseerr' path already exists, skipping copy
[WARN] 2025-03-31 17:33:58 :: Creating '-s' from '/config/overseerr' to '/usr/lib/overseerr/config'...
2025-03-31 17:33:58.762931 [info] SHARED_NETWORK defined as 'yes'

 

Obviously not a big deal since I just downgraded and your previous version still works great, but I figured I'd ask in case there's something easy I'm just missing. (or just that I'm on an older version of UNRAID - 6.10.3)

Edited April 1, 20251 yr by ti1212
Added UNRAID version

7 hours ago, ti1212 said:

SHARED_NETWORK defined as 'yes'

Is this container using a network of another container? if not then set this to no (the default).

Thank you! That's definitely part of the problem, it starts up fine with it set to no.

It's setup to share a network with a few of the arr containers, also sabnzbdvpn, and delugevpn which I just tried restarting and it correctly shows a different IP from my public IP and has provoxy enabled. I also tried with sabnzbdvpn with privoxy enabled and it still stops immediately.

Looks like Plex broke Overseerr's watchlist sync. Word is the Overseerr dev build has it fixed. Is there a way to get that build for this container?

Thanks for all you do! (Please excuse any dumbass verbage by this filthy casual)

6 hours ago, troglodytis said:

Looks like Plex broke Overseerr's watchlist sync. Word is the Overseerr dev build has it fixed. Is there a way to get that build for this container?

Thanks for all you do! (Please excuse any dumbass verbage by this filthy casual)

I try and not build from non releases to keep the support maintenance down to a minimum, for now i would recommend switching to the previous release of plex to keep you working until there is a new release from Overseer to address this (i would assume this will happen quite quickly!).

If there is still no release in a week's time then i will re-evalute this and possibly slip in a temporary build from branch.

If you want instruction on how to roll back o a previous version then please see Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Finally dug into figuring out why watchlist syncs weren't working today and found this thread. Hoping for a fix soon without rolling back Plex. Thanks for your help!