binhex

SickChill is now available (renamed fork that was as far as you guys are concerned, sickrge) so it should be a drop in replacement once the container is configured the same way. Sent from my SM-G935F using Tapatalk

reserved

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

READ THIS BEFORE RUNNING:- ok so after a bit of work on this i have fied it up, HOWEVER there has been a lot of chat regards sickrage and the fork now called sickchill, please be aware of the following notes shown on the sickchill github repo regards the current sickrage app:- i personally dont want to get involved in this fight, but i wont be running sickrage on my system any time soon, i would recommend switching to sickchill (to be created) or the other very active fork called Medusa (check CA) but the choice is of course yours. btw the issue building was caused by a bug in the girhub api and the release tag names, so for now the tag has had to be hard coded in (not good), this only affects the sickrage repo.

so yur log looks clean and that is a successful start so im not worried that its something obvious, im assuming that your lan network is defined correctly (can connect via deluge app), just incase double check this value as shown in the log:- 2018-10-11 22:21:43.576691 [info] LAN_NETWORK defined as '192.168.1.0/24' see here for how to calculate it Q3:- https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613 so if that value is correct then i would assume its one of the following:- 1. pc firewall - try temporarily turning off any firewall running on the pc, alternatively try from another pc/tablet/phone 2. browser plugin - try running your browser in safe mode with NO plugins enabled, alternatively install another browser and try using that. 3. router/firewall blocking - take a look at any firewall/router you might have on your lan (running pfsense?) and make sure the connection isnt being blocked.

i will see if i get time tonight to take a deeper look at the issue.

follow steps in url below:- https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

one more thing to check, are you copying and pasting the credentials or are you manually typing the credentials into the unraid web ui configuration for the docker?, if you are copying and pasting then watch out for spaces at the beginning/end of the username and/or password (encountered by other user).

no idea then all I can say is there are no restrictions for the VPN tunnel it is completely open for all ports and protocols outbound Sent from my SM-G935F using Tapatalk

are you usng a vpn on your laptop? if not you are comparing apples with pears. it could be the tracker is blocking vpn ip ranges or it could be you have no incoming port which may be causing connectivity issues, are the trackers public or private? ahh i see you said its public earlier on.

im sorry but there is no way this is related to unraid, and if there were issues with this container then with all respect i would expect a lot more reports than 1 (10+ million downloads of this image). i have seen this symptom before and every time its been related to login details, not sure what else i can say or suggest at this point, maybe contact the vpn provider and see if they can see anything on their end as to why you cant authenticate correctly.

Pia does not support static port assignment, airvpn does so you would have to switch it that's a requirement. Sent from my SM-G935F using Tapatalk

Ok try the following:- Ensure you are using the correct account details, not forum login details, make sure it's the right login name. Change your password and then change it for container to match to ensure there is no issues on the providers end. Double check your account is still active and you have paid. Sent from my SM-G935F using Tapatalk

So i spotted that cleanup of the pid file is required on crash around August and put some code in to delete the pid file if it exist before attempting to start deluge, so this should be doing this automatically for you, are you running latest or are you running a specific tagged version? (synology user?). As to why deluge is crashing, thats difficult to say, but thats why the pid file is not getting deleted.