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.

binhex

Community Developer
  • Joined

  • Last visited

Everything posted by binhex

  1. try a force update, go to unraid web ui/docker click on toggle at top right to 'advanced view' then click on the link 'forced update' for the jellyfin container
  2. OK so what i currently suspect is going on is as follows:- Plex release a new version that requires database modifications The user does not realise this and updates and notices no access to the web ui (due to the database upgrade being in progress), the user then restarts the container part way through the database upgrade User still cannot access the Plex web ui and looks at the logs and notices either the message 'database or disk is full' (i suspect this really means database is corrupt) or 'database disk image is malformed', which are a result of 2. User rolls back to previous version which does not reference the new database modifications and therefore is not aware of the database corruption until the user attempts upgrade of plex again. The only way for me to identify if this is the case is to look at the log file, please can you post both /config/supervisord.log and the plex log located at /config/Plex Media Server/Logs/Plex Media Server.log Note:- Please do keep this in mind.
  3. just because your disk is not full does not mean your docker image isn't, take a look at the unraid webui/dahsboard/system and look at docker utilisation, what is this at? screenshot perhaps.
  4. Disk is full, you need to sort that first
  5. interesting!, initially i had this issue, but the image never got published as my smoketest picked it up, i corrected the issue and the test passed, i have also just downloaded the latest image and done a clean startup (no pre-existing config) and it started correctly, so im not sure how this is happening for you, what is 'repository' set to for the container?.
  6. i have rebuilt the base recently, so i will kick off a rebuild of the image in the next few days and hopefully that will fix it up.
  7. this is interesting, as that package is installed in the base and ALL images are built from the base image:- https://github.com/binhex/arch-base/blob/2cf699902bd1727a983c9957b8aafbede3dad0fb/build/common/root/install.sh#L110
  8. ahh i see, that looks like a quoting issue, i have reverted back to my previous code for that section, i was attempting to keep the code DRY but it looks like its a PITA to do, pull down latest image and let me know how you get on.
  9. Yep sorry that's my fault, coding issue, its now fixed and a new image has been created, please pull down latest image and you should be good.
  10. OK that's fine, just double checking here as a lot of people get tripped up on port and volume bindings in docker. Hmm well the only other things you can try is attempt connection to the webui via different machine, different browser, try renaming your config folder and restart to recreate from scratch - see if you can access the webui then, if you can' then there is something fundamentally wrong with your networking stack, try a reboot of the host.
  11. that is not the correct port, from your scrrenshot I see you have set it to 8083, so you should be attempting connection to http://192.168.1.2:8083 have you tried that?
  12. at a guess without the seeing the plex log i would say database corruption ,see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
  13. there is nothing obviously wrong there, i see a database migration happened successfully (or at least no errors were shown), can you post a screenshot of the container settings (left click, select edit and screenshot all settings).
  14. I have now switched the build scripts over to https://github.com/nzbgetcom/nzbget/releases next release incoming shortly will be from here and for the foreseeable future.
  15. reserved
  16. Overview: Support for Docker image arch-gonic in the binhex repo. Application: Gonic - https://github.com/sentriz/gonic Docker Hub: https://hub.docker.com/r/binhex/arch-gonic/ GitHub: https://github.com/binhex/arch-gonic Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer 😁 For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here
  17. it would require the Arch package maintainer to update the package, but this MAY have some reliance on the Jellyfin team, it would depend on how its packaged. Yes, the images i produce are Arch Linux based, other developers tend to use other base images, such as Alpine. Is there a reason for the urgency in getting updated?, a specific issue you are trying to solve perhaps?
  18. once the upstream is updated then the image will auto build
  19. Please do not create support requests here:- @SpencerJ i thought this was locked down (it should be)? fallout from the upgrade perhaps?
  20. I am not sure what is going on with your setup but this issue is unique to you, so let's try forcing an update for starters and go from there:- toggle 'basic view' to 'advanced view' (top right in unraid/docker web ui) click on 'force update' for each container, this should result in a forced pull down of the latest image check troublesome container.
  21. They were EXAMPLES, if your host path is something else then use that, same for container path. Do as Hogwind suggests, you might as well fix up Jackett, same issue, change container path to /data (currently set to /downloads) or remove it (not required for jackett.
  22. See Q4, get this sorted first:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
  23. yes sorry i wasn't clear enough, i meant switch back to openvpn IF you were forced to switch to Wireguard and you WANT to move back (for whatever reason - multi remote endpoint support being the main one).
  24. wireguard is unaffected by CRL (specific to openvpn)
  25. Thanks for the reply, personally for me I don't mind saying bye to Tapatalk as long as there is a mobile friendly replacement, which by the look of it there is!, just tried hitting the forum and yep it looks pretty good on the face of it, time will tell what functionality is missing (if any). Figured out PWA's allow you to 'add to Home screen' which is kinda cool, makes it feel a little more app like 🙂

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.