binhex

January 28, 2016

Hi guys, are you only seeing a broken icon for sonarr or are other icons not displaying too, just want to make sure i get to the bottom of this.

January 28, 2016

Hi Binhex! I posted in /plugins (v6), but was told to post here as well.

Hi all,

I've recently made the move from FreeNAS to Unraid and I'm trying to get used to the whole docker setup. I feel like I've gotten most of my docker apps setup and running without a hitch, the one I can't seem to figure out is DelugeVPN from binhex. I'm using IPVanish as my vpn and have gone into the advanced settings to get everything properly set up based on these threads [https://lime-technology.com/forum/index.php?topic=38055.210] [https://lime-technology.com/forum/index.php?topic=38055.0]. Any help would be greatly appreciated as the rest of this process has been incredibly awesome.

I have the ca.ipvanish.com.crt file as well as the ovpn file sitting in mnt/cache/

Could this be causing the issue?

Here are the logs pulled:

2016-01-27 23:16:55,088 DEBG 'start' stdout output:

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -j ACCEPT

-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --sport 443 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT

-A INPUT -i eth0 -m iprange --src-range myserverports-myserverports.254 -j ACCEPT

-A INPUT -i eth0 -m iprange --dst-range myserverports-myserverports.254 -j ACCEPT

-A INPUT -p udp -m udp --sport 53 -j ACCEPT

-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT

-A INPUT -i lo -j ACCEPT

-A OUTPUT -o tun0 -j ACCEPT

-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --dport 443 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT

-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT

-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT

-A OUTPUT -o lo -j ACCEPT

2016-01-27 23:16:55,088 DEBG 'start' stdout output:

--------------------

2016-01-27 23:16:55,088 DEBG 'start' stdout output:

[info] nameservers

2016-01-27 23:16:55,089 DEBG 'start' stdout output:

nameserver 8.8.8.8

nameserver 8.8.4.4

2016-01-27 23:16:55,089 DEBG 'start' stdout output:

--------------------

2016-01-27 23:16:55,093 DEBG 'start' stdout output:

[info] Starting OpenVPN...

2016-01-27 23:16:55,097 DEBG 'start' stdout output:

Wed Jan 27 23:16:55 2016 DEPRECATED OPTION: --tls-remote, please update your configuration

2016-01-27 23:16:55,097 DEBG 'start' stdout output:

Wed Jan 27 23:16:55 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015

Wed Jan 27 23:16:55 2016 library versions: OpenSSL 1.0.2e 3 Dec 2015, LZO 2.09

Wed Jan 27 23:16:55 2016 WARNING: file 'credentials.conf' is group or others accessible

Here are the VPN settings I used=

VPN_ENABLED yes

VPN_USER myusername

VPN_PASS mypassword

VPN_REMOTE ams-a08.ipvanish.com

VPN_PORT 443

VPN_PROTOCOL udp

VPN_PROV custom

ENABLE_PRIVOXY no

LAN_RANGE mynetworklan.3-mynetworklan.3.254

Let me know if there's anything else you guys need as far as info and thanks again.

Hi and welcome to unRAID forums!, your going to love it here, people are friendly and knowledgeable, best forum ive ever been on for sure!.

OK so first thing ive spotted is this:-

mynetworklan.3-mynetworklan.3.254

so the lan range needs to be an ip range, an example:-

192.168.1.1-192.168.1.100

secondly you state this:-

I have the ca.ipvanish.com.crt file as well as the ovpn file sitting in mnt/cache/

so once you have created your cache only share on your cache drive and defined this for the /config volume mapping then you would start and stop delugevpn via the unraid webui, this wll create a folder under /config called "openvpn" so the path would then be /config/openvpn/ (obviously /config is a volume mapping to the host) you then copy the ovpn config file from your provider and any certificates supplied or referenced in the ovpn file to that folder and start delugevpn again.

if your still struggling after this then please post the entire /config/supervisord.log (noticed the one above is not complete) and also the contents of your ovpn config file from your provider, please ensure any sensitive info is removed before posting either of these.

January 28, 2016

reserved

January 28, 2016

I was looking for a list of the changes in the new build, and ended up here...

https://hub.docker.com/r/binhex/arch-sabnzbdvpn/

From there, there is a link to the support page, but it takes you to the old support thread, which you just closed. No big deal, just letting you know it didn't get updated in all your recent changes

yeah i knew about that, unfortunately the link between github and docker hub is broken for readme files, not sure why, it used to work but doesnt now (readme on github is correct), it was after midnight and the matchsticks supporting my eyelids were starting to bend so left it, thanks for the reminder mate i shall do the manual edit's today :-).

January 22, 2016

reserved

January 22, 2016

reserved

January 22, 2016

Overview: Support for Docker image arch-teamspeak in the binhex repo.

Application: TeamSpeak - https://www.teamspeak.com/teamspeak3

Docker Hub: https://hub.docker.com/r/binhex/arch-teamspeak/

GitHub: https://github.com/binhex/arch-teamspeak

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

January 22, 2016

reserved

January 22, 2016

reserved

January 22, 2016

Overview: Support for Docker image arch-sonarr in the binhex repo.

Application: Sonarr- https://sonarr.tv/

Docker Hub: https://hub.docker.com/r/binhex/arch-sonarr/

GitHub: https://github.com/binhex/arch-sonarr

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

January 22, 2016

Existing users please read

If you download the latest Docker image as of 16th Feb 2016 then permissions and ownership will be applied on startup, if you want to avoid this happening then please create an empty file called "perms.txt" in the root of the host mapped /config folder. Please note permissions will ONLY be applied on FIRST RUN with the new image, after that a perms.txt file is automatically created and it will not re-apply permissions unless the file is manually deleted.

The reason i am doing this is to further allow the user to define the user and group the container runs as via UID and GID env vars, this means non unraid users can now more easily run the containers as any user, as opposed to being forced to set perms manually for user "nobody". This also helps people easily sort out any permissions issues by simply deleting the /config/perms.txt file to force a re-apply of the correct permissions for the container.

Note

If you do not create /config/perms.txt then please expect a wait whilst permissions are set on the first run, you can expect wait times of up to 15 mins for large metadata collections, if your unsure whether its still applying changes then please check /config/supervisord.log

January 22, 2016

IMPORTANT - This Docker image allows Plex Pass account holders to get early access to new features which is great, HOWEVER it also means you are more susceptible to newly introduced bugs.

If you value stability over shiny new features then please consider running binhex-plex instead, link to support below:-
https://forums.unraid.net/topic/44141-support-binhex-plex/

Note - To be clear, the binhex-plex Docker Image still allows you access to all the additional features you get with a Plex Pass account, it just means you will get delayed access to any NEW features added by Plex developers.