Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

EvilTiger

Members
  • Joined

  • Last visited

Everything posted by EvilTiger

  1. the error started three builds ago ... when it was upgraded to 1.32.1 anything before this works fine
  2. interesting ... i just did that and now recieving the same error with the plexpass container. so it must not be an issue with the container, it must be an issue with the config files in /mnt/user/appdata/binhex-plex ... i wonder if there was an upgrade to the database which was missed in a prior version or something ... i really dont know. I think the best thing to do is just create a new appdata dir and rebuild my libraries
  3. Plexpass latest works fine, i also just tried to re-install the docker app and got the same results. i guess i will use the plexpass version going forward ... question ... can i point the /config property at my old /mnt/user/appdata/binhex-plex directory so i dont have to copy all my metadata files to/mnt/user/appdata/binhex-plexpass??
  4. i appreciate that and i fully understand -- let me try to deploy the plexpass latest version side by side to see if makes a difference
  5. I just posted what appears to be the same issue with the "latest" tag docker image. Sorry for reposting, i didnt see this post prior to submitting mine. I've been able to workaround it by doing the same as you, using a specific version tag and not grabbing the latest version of the docker image. Following this thread now as well as mine ... Best regards, -Tiger
  6. Hi all, I'm hoping that this is an easy fix or something i over looked. Either way i appreciate the your time to look at this. I've been running the docker image binhex/arch-plex:latest for many years without issue and i have my docker containers setup to automatically upgrade when there is a new version of the image. At some point over the past several weeks the "latest" build is now failing on start up with the following errors.. This is the error after which the server stops and it tries to relaunch. I've been able to work around this by not using the "latest" docker tag and using this version of the docker image So, i'm up and running now but over time this image willl get more out of date. Is anyone else seeing this with the latest image? any pointers to get this resolved would be greatly appreciated. All the best, -Tiger
  7. scratch that, i dont think its a NAT loopback issue ... its works fine in Chrome locally and only goes to the 'Welcome ...' page in Microsoft Edge must be a browser setting issue, any clues?
  8. thank you for the quick response 1) you're correct ... there was an extra space after the api key from the copy / paste 2) for testing sake, i tried to access via an external connection [over my mobile] and it worked, so i must be internal NAT loopback issue. i need to figure out how to address via Unifi USG
  9. 2 issues ... 1) Downloading GeoIP2 City database. tar: invalid tar magic I've added my api key for MaxMind but getting an invalid tar magic error 2) nginx isnt routing requests to my downstream app container on the same subnet letsencrypt component seems to be working, nginx is just getting me to the welcome page. not seeing issues in the container log file. app specific sample .conf files have been changed to map to the specific container names in my environment [no other change other than renaming the file to remove .sample] any pointers as to why nginx isnt forwarding on the request to my downstream app container? or where to look for log files? Thank you in advance
  10. will do, thx
  11. thank you, that should do it as I now see it created the sub dirs. in the correct location. I assume I need to remove the directories that were created within the container. actually, I cannot find where the 7gb is being consumer, I assume the process cleans up after itself and the 7gb is the highwater mark of where it was at one point in time. if, how do I shrink the container so its not using almost 50% of my docker.img allocation? again, much appreciated.
  12. Hi @jonathanm, Thank you for the reply. In my case all 'Paths' are defined as ${AppDir} or ${MainDir}. For the former, this is an environmental variable which is a volume mapping per my original post (/data <--> /mnt/user/downloads/) and the latter, is a nzbget variable which points to ${AppDir} and defines a sub directory within. I cannot find any other references to any other location within the configuration of nzbget. Any other ideas?? What is a typical size of other users nzbget containers? Thank you in advance.
  13. just checked the sizes of my various containers and noticed an anomaly. My binhex-nzbget container is currently taking up 7GB of space which is approx 7-10x bigger than any other container. I don't know if its growing, will keep an eye on this. Is this typical? if not what could be the cause? FYI, my /data <--> /mnt/user/downloads/ and my /config <--> /mnt/user/appdata/binhex-nzbget
  14. just got this up and running ... is there a UnRaid team i can join?
  15. yup, i was editing within the container ... it worked when i edited from outside the container. thank you for the help.
  16. just trying to get this setup using Google Domains and i'm editing the ddclient.conf file but the file is overwritten back to the original each time i restart the container. I'm editing the file via docker exec -it ddclient bash and running vi ddclient.conf is there a correct way to edit the file? should i be passing in the edits via the container template? thank you in advance.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.