diamkil Posted December 15, 2020 Share Posted December 15, 2020 (edited) Overview: Support for the docker template and container for Overseerr App: Overseerr - https://github.com/sct/overseerr Docker Hub: https://registry.hub.docker.com/r/sctx/overseerr Edited December 18, 2020 by diamkil 1 Quote Link to comment
chrispcrust Posted December 17, 2020 Share Posted December 17, 2020 Got it working, love the UI. Reverse proxied it, tested with a friend, everything working great! Quote Link to comment
Anthwerp Posted December 17, 2020 Share Posted December 17, 2020 This is awesome! I've tried Ombi before but I like this better even in the ALPHA state. Looking forward to the updates! 1 Quote Link to comment
Cpt. Chaz Posted December 18, 2020 Share Posted December 18, 2020 (edited) has anyone gotten the proxy conf working for this? i can't seem to get it working per this example from the github page. i've added the cname into cloudfare and running SWAG from lsio. my reverse proxy is working fine for all my other proxy confs, so i don't think this is a SWAG issue. edit: duh, forgot to put the container network type on the proxynet! 🤦♂️ Edited December 18, 2020 by Cpt. Chaz solved 1 Quote Link to comment
diamkil Posted December 18, 2020 Author Share Posted December 18, 2020 12 hours ago, Cpt. Chaz said: has anyone gotten the proxy conf working for this? i can't seem to get it working per this example from the github page. i've added the cname into cloudfare and running SWAG from lsio. my reverse proxy is working fine for all my other proxy confs, so i don't think this is a SWAG issue. edit: duh, forgot to put the container network type on the proxynet! 🤦♂️ I personally use it a different way just pointing to my local server ip and the host port, if it works that way for you I'm happy! Quote Link to comment
diamkil Posted December 18, 2020 Author Share Posted December 18, 2020 New Overseer update changes internal port, template has been updated for new install but you can simply remove the port binding and add it back with internal port 5055 (instead of 3000) Quote Link to comment
progrockusa Posted December 18, 2020 Share Posted December 18, 2020 Having trouble getting the gui to launch, even reinstalled from scratch. Tried both ports 300 and 5050 192.168.1.144 refused to connect. Search the web for 192 168 1 144 ERR_CONNECTION_REFUSED Quote Link to comment
drpeppershaker Posted December 18, 2020 Share Posted December 18, 2020 Switching to sctx/overseerr:devolop broke the webUI for me. I switched back to sctx/overseerr and it's working again. Not sure if this is an unraid/docker issue or a overseer issue. I have no errors showing in the logs. Quote Link to comment
progrockusa Posted December 18, 2020 Share Posted December 18, 2020 22 minutes ago, drpeppershaker said: Switching to sctx/overseerr:devolop broke the webUI for me. I switched back to sctx/overseerr and it's working again. Not sure if this is an unraid/docker issue or a overseer issue. I have no errors showing in the logs. I never messed with any of that still on sctx/overseerr just stopped working after the update this morning Quote Link to comment
JohnnyGrey Posted December 18, 2020 Share Posted December 18, 2020 (edited) The internal port was changed to match the external port, so it's now 5055:5055. If using the develop tag, you have to manually edit the container to reflect this. InternalIP:5055 will be the WebUI instead of InternalIP:3000. (This applies to develop tag, as well as master tag with version 1.9.1) Edited December 18, 2020 by JohnnyGrey Quote Link to comment
progrockusa Posted December 18, 2020 Share Posted December 18, 2020 1 minute ago, JohnnyGrey said: The internal port was changed to match the external port, so it's now 5055:5055. If using the develop tag, you have to manually edit the container to reflect this. InternalIP:5055 will be the WebUI instead of InternalIP:3000. Funny thing is it is set to 5055 in the container, but when I launch the app still tries to go to 3000, changed manually and I got into the gui. Quote Link to comment
Fiala06 Posted December 18, 2020 Share Posted December 18, 2020 (edited) 3 minutes ago, progrockusa said: Funny thing is it is set to 5055 in the container, but when I launch the app still tries to go to 3000, changed manually and I got into the gui. Click advanced view and edit the WEBUI Edited December 18, 2020 by Fiala06 Quote Link to comment
progrockusa Posted December 18, 2020 Share Posted December 18, 2020 2 minutes ago, Fiala06 said: Click advanced view and edit the WEBUI has this http://[IP]:[PORT:5055]/ Quote Link to comment
progrockusa Posted December 18, 2020 Share Posted December 18, 2020 1 minute ago, progrockusa said: has this http://[IP]:[PORT:5055]/ 3 minutes ago, Fiala06 said: Click advanced view and edit the WEBUI still tries to launch to port 3000, even cleared cookies on my browser Quote Link to comment
JohnnyGrey Posted December 18, 2020 Share Posted December 18, 2020 Mine worked immediately following this change. I also had to remove the Host Port 1 and then recreate it: I also had to modify the port from 3000 to 5055 in my reverse proxy config. More info about that here. 1 Quote Link to comment
progrockusa Posted December 18, 2020 Share Posted December 18, 2020 1 minute ago, JohnnyGrey said: Mine worked immediately following this change. I also had to remove the Host Port 1 and then recreate it: I also had to modify the port from 3000 to 5055 in my reverse proxy config. More info about that here. Ok i'll give that a shot, currently it's rescanning my library Quote Link to comment
Fiala06 Posted December 18, 2020 Share Posted December 18, 2020 (edited) Also @diamkil Overseerr is spelled wrong. Should be "Overseerr" not "Overseer" Just missing another "r" on the end. Edited December 18, 2020 by Fiala06 Quote Link to comment
diamkil Posted December 18, 2020 Author Share Posted December 18, 2020 1 minute ago, Fiala06 said: Also @diamkil Overseerr is spelled wrong. Should be "Overseerr" not "Overseer" Just missing another "r" on the end. It's on two 'r's my guess is it didn't update the template for you yet as it show Overseerr for me 1 Quote Link to comment
diamkil Posted December 18, 2020 Author Share Posted December 18, 2020 If some of you are still having problems I recommend removing it, restarting your unraid and installing the app from CA again Quote Link to comment
JohnnyGrey Posted December 18, 2020 Share Posted December 18, 2020 48 minutes ago, diamkil said: It's on two 'r's my guess is it didn't update the template for you yet as it show Overseerr for me I think Fiala means on this thread It's spelled correctly in Unraid, bot not on this thread. Quote Link to comment
diamkil Posted December 18, 2020 Author Share Posted December 18, 2020 3 minutes ago, JohnnyGrey said: I think Fiala means on this thread It's spelled correctly in Unraid, bot not on this thread. oh true will fix asap 1 Quote Link to comment
progrockusa Posted December 18, 2020 Share Posted December 18, 2020 double checked all my settings, still opening to port 3000 from the docker app section in unraid. all settings show port 5055 Quote Link to comment
pepbill Posted December 18, 2020 Share Posted December 18, 2020 Deleted Docker and re-installed over the old app data and working now. Quote Link to comment
Cpt. Chaz Posted December 18, 2020 Share Posted December 18, 2020 (edited) 3 hours ago, diamkil said: I personally use it a different way just pointing to my local server ip and the host port, if it works that way for you I'm happy! i use it your way for internal network access, but the other method is needed for reverse proxy, which provides external network access for other users to make requests. edit: thanks for this container btw, very cool! Edited December 18, 2020 by Cpt. Chaz gratitude Quote Link to comment
progrockusa Posted December 19, 2020 Share Posted December 19, 2020 Anyone know why the app still tries to go to port 3000? Already reinstalled this from scratch, including erasing the app data folder container settings click wrong port Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.