binhex

thats your issue in a nutshel;, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

i assume you got that info from this issue? https://github.com/Sonarr/Sonarr/issues/8249

apologies for the delay, so much going on IRL right now, i have just created a new image which should refresh the base this image is built upon, please pull down latest and try again and let me know the outcome.

no idea, you can take a look at the config file for soularr, it should be located in /config/soularr/ that will show you all options available, failing that raise an 'issue' on the github repo for soularr: https://github.com/mrusse/soularr/issues

A quick question, are you using my newly released soularr docker image or are you using the official one on CA?, just curious really. I have put in a bit of extra love into my template and created a new image, so you can define lots of the configuraiton of soularr via the env vars, something not present in the other template or official image.

OK so i have made some strides to make this easier, the slskd CA template now includes a new 'variable' named 'API_KEY', but as CA Templates do not auto update you wil have to add it in if you are using the template before this change, here is what it should look like: So the actual API_KEY can be anything, as long as its between 16 and 255 characters, if you want to follow the slskd guide then they suggest you run the following command inside the slskd container to generate a randomised string (left click icon, choose console) then execute openssl rand -hex 16then copy and paste the strng into the value field for the API_KEY. Once this is set apply the change (bottom button on the edit screen) and then set the 'variable' SLSKD_API_KEY in soularr to match and you should be good, pretty simply really.

If you are having issues with the application then i would advise posting an issue on the sabnzbd github repo:- https://github.com/sabnzbd/sabnzbd/issues

@bakkadps @mkirkelund I will try and get some time to take a look at this over the next couple of days.

Thanks for the heads up, i see the notice on the downloads page and i have now switched over to the tvheadend git branch, please pull down the latest image at your convienience.

Things seem to be in a state of flux right now, i would not advise moving for now until there is a first release, apparently the current latest release is simply jellyseer (something i was not aware of at the time of creating this image), if i see any movement and a new release is created then i will try and remember to post here to let people know.

Yep, ignore it, it is not critical even though the stupid message from Plex says otherwise. Yep this is a classic case of db corruption, it's the most common problem with Plex, luckily for you there is an included script in the image which should help you out (skip install instructions), instructions for use can be found here (script authors git repo): https://github.com/ChuckPa/DBRepair

I've come up with a better solution, edit the group for user nobody to match the docker sockets GID (281 in the case of unraid), its more secure and does not change permissions for the socket, please pull down image at your convienience.

i know what's going on!, so i had totally forgotten that i modified permissions to the docker socket as a pre-startup script for code-server (another awesome image), and that's why it worked for me and not you, these are the permissions i see: srwxrwxrwx 1 root docker 0 Dec 29 11:45 /var/run/docker.sock so as you can see you have only read and write for user root (srw-rw----), group docker, which PUID 99 (nbody) and PGID 100 (users) has no access to, whereas i have rwx for user root, group docker and everyone. This grants me full permissions for 'everyone' which obviously includes user 'nobody'. So i know what the fix is and i have put it in the image please pull down at your convieniece, it does mean it will modify your permissions to permit read and write for the docker socker for everyone, the alternative is to run this image as user root, neither are ideal tbh, but i think setting permissions on the socket is preferable.

ok ive created a new image, pull when you can, i have split the detection of the socket and the check for the daemon (performs docker ps ) so it may help work out what the issue is, let me know what the logs say.

Am interesting idea, possibly, try stopping the other container

Hmm interesting!, i had somebody with the exact same issue reported on github (no response back yet), can you try the same: Can you drop to the hosts terminal (not the container) and paste the result of ls -al /var/run/docker.sock also can you tell me what version of unraid you are using. For reference mine looks like this:- srwxrwxrwx 1 root docker 0 Dec 29 11:45 /var/run/docker.sock Please can you also try going to the containers 'console' and paste the result of docker ps Edit - FWIW i am running this with the same PUID and PGID as you and it works, so im unsure as to the cause.

Hi all, this Docker image is a little different to the rest, namely that i am the author of the app (bash script) and the creator and maintaner of the image, any issues with Healarr app or image please post here.

Overview: Support for Docker image arch-healarr in the binhex repo. Application: Healarr - https://github.com/binhex/arch-healarr Docker Hub: https://hub.docker.com/r/binhex/arch-healarr/ GitHub: https://github.com/binhex/arch-healarr 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

Hi, sadly i had to archive the medusa image, i was having some issues building it at the time and as this support thread was dead (last post ws over a year ago before yours) i called it day, i would encourage you to make the switch over to Sonarr, it really is pretty good, not perfect but still pretty solid. p.s. thanks for the donation.

This has now been done and is included in the latest image, please pull down at your convienience.

what is the url you are going to in your web browser?

Ah excellent!, I love a good ending to a story :-) Sure, it is highly tailored to what i want, which is the following: no porn whatsoever i am into emulation, so i classify rom file types. no unknown torrents, if bitmagnet cannot clasifiy it i don't want it. Gistbitmagnet classifier.ymlbitmagnet classifier.yml. GitHub Gist: instantly share code, notes, and snippets.This gives me a pretty clean library of just what i want.

It most probably will do, yes, because bitmagnet process will not be present, i should be able to add some code in to pass a flag to the healthcheck script i wrote to turn off healthchecking if a vacuum/reindex/backup/restore process is in operation. p.s. I was not aware of the docker image autoheal.

OK so do you know if there is any chance of a release from the develop branch any time soon (assuming that is what you mean by the separate branch)?, if not then i will switch to clone from develop branch until things stabilise.