dstanley

Members
  • Posts

    78
  • Joined

  • Last visited

About dstanley

  • Birthday 05/31/1956

Converted

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dstanley's Achievements

Rookie

Rookie (2/14)

8

Reputation

  1. Weird issue I am running into ... I have had Radarr setup and running in Unraid, Swag and Organizr using my custom network for a long time - no problems. I recently setup another container for Radarr - called it 'radarr4k' - set the urlbase to 'radarr4k' - the port redirection to 17878:7878 Modified a copy of the radarr.subfolder.conf for Swag and called it radarr4k.subfolder.conf - edited it to change radarr to radarr4k within the conf file. Everything is working now with Organizr using reverse proxy to access both radarr and radarr4k. I have linked the radarrs using 'lists' so requests for 4k movies in the regular radarr gets picked up by radarr4k - thus giving me 1080P and 4k copies for Plex - COOL!! But here is my problem: In advanced view of the radarr4k template I edited the webui template as follows: http://[IP]:[PORT:17878]/radarr4k/ So what happens now (in the Unraid UI) if I try to launch the webui of the radarr4k docker it navigates to: http://192.168.1.5:17878/radarr4k/radarr/ This gives a "You must be lost, nothing to see here." page inside an empty radarr instance - if I remove the radarr/ from the end and enter - then radarr works fine and all my settings and movies are there. So I am stumped as to why the extra 'radarr' is being added onto the end of the webui address here and how to eliminate it? Most times I will be accessing the dockers from Organizr using my reverse proxy - so this is more of an 'annoyance' than anything critical - not getting the proper webui address from the Unraid docker tab ... Any ideas where to look for an answer? Using Unraid 6.9.1 and the Radarr dockers are 3.0.2.4552-ls97 by linuxserver.io
  2. Not sure if this is appropriate or not but since changing to the ‘official’ OZNU docker I have had zero problems like this log problem. OZNU Homebridge Docker
  3. Is it possible to update the base container again? There have been several updates made that would help in the base install. Thanks!
  4. Thank you SO much - this helped to a point - now the plugin developer is telling me I need to run the Homebrisge@Beta to use his work. Is there some possible way to have this added to the docker as an option?
  5. I am using your Homebridge with Gui docker - have been quite sucessful - but a new NPM that i want to use throws this error: [4/21/2020, 10:02:16 PM] Error: Plugin /usr/lib/node_modules/homebridge-isy requires a HomeBridge version of >=0.4.53 which does not satisfy the current HomeBridge version of 0.4.50. You may need to upgrade your installation of HomeBridge. Is there any chance of getting the main docker pull to have this latest Homebridge version? Without this plugin the install is 0.4.50 and updates fine AFTER it is running - I need it to be 0.4.53 on the docker pull. Thanks for your work!
  6. Unraid has been a lot of fun for me - giving me much more to learn but making everything I want to do with a server reliable and very easy once set up. Looking forward to many years with this platform - thanks guys!!!
  7. Thank you - just a note that it works just fine with Hauppauge USB HD-PVR's - Thanks @CHBMB for your ongoing support of this DVB Edition
  8. This is the progression of releases: 6.7.1rc1 worked with USB Hauppauge 6.7.1rc2 did NOT work with USB Hauppauge 6.71 DOES work with USB Hauppauge and is NEWER that rc1 and rc2 - it is the release stable version - i.e.: Not a Release Candidate.
  9. I have tried using the 6.7.1rc2 versions of LibreElec and Digital Devices but neither of these will recognize my USB based Hauppauge HD-PVR’s within the SageTV Docker. Reverting back to 6.7.1rc1 version and they are all showing up again. Seems to me this happened before and a complete rebuild fixed the issue!? Not too sure though as most of this is WAY over my head ... Dwight
  10. I have tried that exact line but for some reason it makes not difference for me. I am using my dns through Cloudflare but I don’t know if that is my issue!?
  11. I have this added into my Nextcloud config.php but I am still getting this warning ... not sure what else to try. Can anyone help me with this Warning in the Nextcloud 16.0.1 Security & Setup Overview? "There are some warnings regarding your setup. The reverse proxy header configuration is incorrect, or you are accessing Nextcloud from a trusted proxy. If not, this is a security issue and can allow an attacker to spoof their IP address as visible to the Nextcloud. Further information can be found in the documentation." MyConfigFiles.zip
  12. This new compile of 6.7.0-rc8 LibreELEC works for me with my SageTV docker and Hauppauge HD-PVR's now - thank you @CHBMB !
  13. I, too, have lost the functioning of my HD-PVR's in the LibreELEC DVB edition on 6.7.0-rc8 in my SageTV Docker. Reverting back to rc7 as that worked and still does ...
  14. When was the last beta update done? 🤣 I can't resist pushing the update button as soon as the DVB version is ready - I know - I'm asking for it ...
  15. Thank you so much Niklas - this worked out great with your help! I could not have completed this without your help ... Dwight