binhex

you sure about that?, i thought the known vulnerabilities were patched in 1.43.3.10861 or later (already built a while ago):- https://forums.plex.tv/t/important-security-update-for-plex-media-server-v1-43-2-and-earlier/942319/3 in any case 1.43.5.x was built automatically 2 hours ago.

Im working on filebrowser quantum, i shall post back here when its ready.

You didnt answer this question directly, what is the ip address of the machine?, i want to ensure LAN_NETWORK is defined correctly (a very common trip up), keep in mind if your machine is on a different VLAN it will be blocked irresepective of your VLAN ruleset. Can you also tell me is the network for the container is set to bridge?, i have a feeling its not, if not please switch it to bridge then try again.

well it's definitely there:- https://github.com/binhex/arch-plexpass/pkgs/container/arch-plexpass My guess would be internet connectivity or DNS issues.

you should be pointing your router at caddy NOT immich, set caddy to listen on port 8080 and then set immich to listen on another port (otherwise it will conflict with caddy), my suggestion set it to 2283 (standard immich port), then set the caddy file as i detailed above.

I do not support alpha/beta/pre-releases, when v5 drops as stable then it will be automatically picked up and built.

Are you talking about CA here when you say 'apps'? i assume so but it's not clear, thus screenshots would of helped here, as well as the 'tag' you are on about, again i assume this is the tag shown in CA right?. If my assumptions are correct then i cannot explain why a container that exists and was installed via CA would suddenly not be marked as installed, that sounds like a possible CA related issue, i can confirm only one VERY minor change to the template on my side, where i changed the webui link, but i very much doubt this would trigger what you saw. In any case i'm happy you got it resolved.

Nope it's not dead. But low effort posts like this are ignored by me, no logs, no screenshots, nothing!.

ok so the things you need in place: set your router to port forward to caddy container, port 8443 ensure immich is working and listening, if you have immich listening on port 8443 then you will need to change that as it will clash with caddy, the default port for immich is 2283, i would recommend using that. set your caddy config file like so (assuming you change the port for immich to 2283): <myname>.duckdns.org:8443 { import security_headers import log_settings <myname>.duckdns.org.2283 tls { dns duckdns {env.DUCKDNS_TOKEN} } reverse_proxy <unraid ip>:2283 }

This should now be fixed, please pull down latest.

yes you need to ensure that slskd is sharing the same network as gluetun, otherwise slskd will firstly (and most importantly) not be using a vpn and secondly you wont be able to get an incoming port.

So the portset.sh script (script used to talk to gluetun and get the assigned incoming port) will talk to gluetun using the loopback ip address (127.0.0.1), this is how the applications container can get an incoming port from the gluetun's container, so it has to use loopback as both containers must be in the same network, so its working as intended.

As promised, i have switched it over to direct pulls from jellyfin directly, so the latest image is now built against latest, which at the time of this post is 12.1, please pull down at your convienience. Note:- It is HIGHLY recommended that you copy your config folder for jellyfin before you perform the update, that way you can always roll back the container and configuration to the previous version if things go pete tong.

It's been marked as out of date, nothing more to do now other than wait. If nothing happens by the end of this week then i will consider doing a direct install from github jellyfin release, but i would rather not go down that route unless i have to (a fair chunk of work).

it's there, its fully automated so you dont need to nudge me.

That's your problem, unless you specify the user to exec into the container then root will be used, try this: docker exec -u nobody binhex-nzbget /usr/local/share/nzbget/nzbget -c /config/nzbget.conf -L H

It will be a corrupt database, extremely common sadly with plex, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md

you got it, i dont have anything to do with the code if crafty, i simply package up what is supplied by the crafty dev's into a unraid user friendly format.

i would suspect the issue is corrupt configuration, but your best bet for support is to talk directly to the crafty dev's, raise a issue here:- https://gitlab.com/crafty-controller/crafty-4/-/boards#/ or if you prefer chat then talk to them on discord:- https://discord.com/invite/XR5x3ZM

Thanks for that, yeah that's a poor design choice, up to 5 minute wait on shutdown?!, hmmm, def should be done on startup, not shutdown, and any 'optimisations' should be performed on a copy of the db, not directly on the live db, if the optimisation succeeds then the copied optimised db gets gets used on next run, if not it gets deleted and the process loops.

OK it looks like v12 dropped yesterday, here are the upgrade notes (full notes release notes here): > Notes on Updating Before upgrading from an earlier version, a full backup of the data directory is strongly recommended, as this release includes database changes that prevent rolling back without a full restore. Direct upgrades from 10.10.7 and 10.11.x to 12.0 are supported; intermediate upgrades are not required. Users running releases older than 10.10.7 are strongly encouraged to upgrade to 10.10.7 before migrating to 12.0. Installed repository plugins (anything not built-in) should also be removed before migrating. Plugins will likely need time to adapt to the new database changes, so re-adding them afterward is the safest approach for testing. Official plugins compatible with Jellyfin are available through the stable plugin repository. If you have changed to the unstable plugin repository please change it back. Go to Dashboard -> Plugins -> Manage Repositories Update the Plugin Repository URL to: https://repo.jellyfin.org/files/plugin/manifest.json After migrating please perform the following steps. Perform a full library scan to restore alternative versions Before anybody asks - yes it will be built soon but depends on the upstream Arch repository package being bumped, once that's done the build will be automatically built, no need to nag me, if you want to monitor the upstream package it's here (you can see its flagged out of date)

You are in the wrong support thread, this is for binhex jellyfin not LSIO jellyfin

i actually have 4 sets of tags, each with less specfics than the last, for example: latest - always the latest build, irrespective of the release number 10.11.1 - most specific, only match this specific release number 10.11 - less specific, match any 10.11.xx release number, where xx is any release number 10 - least specific, match any 10.xx.xx release number, where xx.xx is any release number so if you want to pick up the very last v10 release then set your tag to binhex/arch-jellyfin:10 then when you are ready either set this to 12 or change to latest

no idea!, but when it does drop on Arch Repository it will be automatically built by the github action workflow.

Just a heads up - watch out for this when it lands, it could be a bumpy ride!:- https://www.neowin.net/news/jellyfin-12-ships-with-version-jump-and-breaking-client-changes/