[ARCHIVE] binhex docker repository

[danger781]

Hey Binhex,

 

I do not know what my CouchPotato username and password is. I recently reinstalled Windows so now I'm being prompted to login again. When I enter an incorrect credentials it does give me a warning or an error, just brings me back to the login prompt. What are my options here to re-gain access to the GUI?

 

I looked in the config folder and found a config.ini with a username and password entry under core but I tried logging in with this and it did not work. A bit of googling shows I'm looking for a settings.conf but I can't find this file in the config folder.

 

Thanks!

[michaelmcq]

Hi Binhex - they way i have get_iplayer on my ubuntu box (which i'm trying to replace with docker containers on my unraid box) is:

• get_iplayer installed from source
  
• scheduled cron job to trigger schedule updates every 3 hours
  
• get_iplayer pvr web interface to manage the watchlist
  
• cron jobs every 3 hours passing custom parameters to download tv shows and podcasts (radio) with specific metadata tagging e.g. MP3 tags, conversion options etc.
  

 

this works really well for me - i can use the GUI to manage the watchlist by e.g. searching for items in a clear catalogue, setting up complex searches etc. I have no idea how to build a docker, but would be happy to help enhance your one if you have some pointers about where to start?

 

hi rara1234, thanks for the volunteered help on this, its appreciated!. couple of questions for you:-

 

1. where does the webui store its configuration information?, can this be configured or would it have to be symlinked in some manner?

2. can you pre-configure some of the options in the webui, or again is this going to have to be done only using the webui?.

 

whilst the way i currently have it running is a little low tech, it generally works quite well, so i want to make sure if i do move to using the webui that its just as solid. right im going to have a play with this now, i may come back with more questions :-).

 

oh and btw this is a quite old thread, best to keep any future posts in my new snagly docker support thread here:- http://lime-technology.com/forum/index.php?topic=38055.0

 

1. The web app simply automates the use of the PVR functionality: https://github.com/get-iplayer/get_iplayer/wiki/documentation#pvr-usage

So if you were to map that folder (~/.get_iplayer/pvr/) the searches would persist between refreshes.

2. Not sure what options you'd want to configure? or do you mean about searching, download options etc.?

 

I kinda lost track of this conversation here - to me, it makes no sense to have 1 thread per publisher, wouldnt 1 thread per image be better?? - anyway, i created my own docker which implements what i needed - basically, it's get_iplayer pulled ppa:jon-hedgerows/get-iplayer and with apache running the web pvr. You can find it here: https://hub.docker.com/r/mnbf9rca/getiplayer

 

I've made it so that the list of already recorded files and the PVR searches are stored outside the container for persistence. The programme cache is updated every hour, and you can add radio, tv and podcasts. The PVR runs every 6 hours.

 

Map the folders listed in teh dockerfile:

# /output = location of downloaded files

# /tmp for transcoding? not sure

# /var/www/get_iplayer/.get_iplayer --> profile directory, including PVR searches and cache

# /etc/get_iplayer --> options file stored here

I've been using your get_iplayer docker and I've made a few (Probably ill informed!) tweaks to make it work better for me.

 

I created the nobody user

 

usermod -u 99 nobody

usermod -g 100 nobody

 

I removed the ownership change part of /etc/my_init.d/startup.sh and instead set the owner to nobody

 

I changed the apache user to nobody via /etc/apache2/envvars

 

Without making those changes I couldn't edit/create PVR saves outside of SSH/WebPVR

 

I also removed the copy bits from the crontab and instead use the paths I want in my PVRs to the mapped download folder (/output)

 

I wanted to get the latest 50fps downloads so I updated both get_iplayer and the web interface to the latest dev version (just via wget)

 

Finally I ran echo "export TERM=dumb" >> ~/.bashrc so that I could run top and see what's going on

 

As a result, for now at least it's working exactly how I want it to, thanks for your excellent docker!

 

I'm a total novice when it comes to docker and linux (& unraid for that matter) so if any of the above was a bad idea, feel free to let me know I won't take offence!

[binhex]

Hey Binhex,

 

I do not know what my CouchPotato username and password is. I recently reinstalled Windows so now I'm being prompted to login again. When I enter an incorrect credentials it does give me a warning or an error, just brings me back to the login prompt. What are my options here to re-gain access to the GUI?

 

I looked in the config folder and found a config.ini with a username and password entry under core but I tried logging in with this and it did not work. A bit of googling shows I'm looking for a settings.conf but I can't find this file in the config folder.

 

Thanks!

 

you wont be able to recover your password as its obfuscated in the config.ini file, the bit your looking for is in /config/config.ini and its in the [core] section, example from a default config.ini:-

 

[core]
api_key = 3bd3ba789201430aacfd46c138ba0d74
username = admin
ssl_key = 
proxy_server = 
ssl_cert = 
data_dir = 
use_proxy = 0
permission_file = 0644
proxy_password = 
dereferer = http://www.dereferer.org/?
permission_folder = 0755
dark_theme = False
development = 0
proxy_username = 
ipv6 = 0
debug = 0
launch_browser = True
password = 5f4dcc3b5aa765d61d8327deb882cf99
port = 5050
url_base = 
show_wizard = 0

 

so you can see the username is "admin" but the password is unreadable, simply stop couchpotato docker, open the file with something like notepad++ that understands linux line endings, and then delete the value for username and password but NOT the key and then start couchpotato docker, this should then allow you in with no credentials and you can then set them to what you want.

[JustinChase]

I restarted my server again today and got an error when I clicked the SAB tab (didn't copy it, sorry).

 

I wend to the docker tab and re-saved the docker thinking it would force it to rebuild it and get it working again.  Instead, i was greeted with this before it tried to re-create the docker (which then failed)...

 

Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25

Pulling image: binhex/arch-sabnzbdvpn:latest

 

Seems serious.

 

I've recently turned on the PCIe override to get a second VM working with a second nVidia video card passed thru to to, and I'm thinking this override is causing me these new problems.  is that possible?

[eggsbenedict]

Apologies if this is not a Deluge issue, but I'm very much past the limit of my understanding of how computers work here! A torrent site I visit has recently updated their security after a DDOS attack. I'm now getting an error when attempting to add a torrent from URL (which I pull from the RSS feed generator, it's easier than copying cookies that change all the time).

 

2016-01-21 15:25:40,275 DEBG 'deluge-web' stderr output:
[ERROR ] 15:25:40 json_api:661 Error occurred downloading torrent from https://<removed>/download.php?type=rss&secret_key=<removed>&id=123456
2016-01-21 15:25:40,278 DEBG 'deluge-web' stderr output:
[ERROR ] 15:25:40 json_api:662 Reason: [('SSL routines', 'SSL23_GET_SERVER_HELLO', 'tlsv1 alert internal error')]

 

Apparantly this has something to do with this issue: http://dev.deluge-torrent.org/ticket/2765 but I can't tell if that means that it should be fixed in the current version, or if the fix will not be available until some future version? Any thoughts?

[binhex]

I restarted my server again today and got an error when I clicked the SAB tab (didn't copy it, sorry).

 

I wend to the docker tab and re-saved the docker thinking it would force it to rebuild it and get it working again.  Instead, i was greeted with this before it tried to re-create the docker (which then failed)...

 

Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25 Warning: mkdir(): File exists in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 23 Warning: chown(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 24 Warning: chgrp(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 25

Pulling image: binhex/arch-sabnzbdvpn:latest

 

Seems serious.

 

I've recently turned on the PCIe override to get a second VM working with a second nVidia video card passed thru to to, and I'm thinking this override is causing me these new problems.  is that possible?

 

that does look particularly nasty!, throwing an internal error from unraid by the looks of it, i would say you either have found a new unraid bug there or you have some hardware issues, possibly cache drive related. if i were you i would post this in the general support thread for unraid and see what other people more knowledgeable with the internal workings of unraid think to it, my gut feeling is its corruption of the loopback docker image and/or corruption of your cache drive

[binhex]

Apologies if this is not a Deluge issue, but I'm very much past the limit of my understanding of how computers work here! A torrent site I visit has recently updated their security after a DDOS attack. I'm now getting an error when attempting to add a torrent from URL (which I pull from the RSS feed generator, it's easier than copying cookies that change all the time).

 

2016-01-21 15:25:40,275 DEBG 'deluge-web' stderr output:
[ERROR ] 15:25:40 json_api:661 Error occurred downloading torrent from https://<removed>/download.php?type=rss&secret_key=<removed>&id=123456
2016-01-21 15:25:40,278 DEBG 'deluge-web' stderr output:
[ERROR ] 15:25:40 json_api:662 Reason: [('SSL routines', 'SSL23_GET_SERVER_HELLO', 'tlsv1 alert internal error')]

 

Apparantly this has something to do with this issue: http://dev.deluge-torrent.org/ticket/2765 but I can't tell if that means that it should be fixed in the current version, or if the fix will not be available until some future version? Any thoughts?

 

I would say this is indeed a Deluge issue, if i were you i would raise a ticket on the Deluge bugtracker or post on their forum and see what they say as its an internal Deluge bug and not related to Docker or unRAID.

[binhex]

This thread will be locked shortly, why am i doing this?, because this thread is getting far too long (over a 100 pages) and needs to be split out to a thread per Docker image, this will help users searching for answers to questions that may of already been asked and also make it easier for people to answer questions without the original question getting lost in the cross talk from other issues.

 

To prepare for this i have created a General thread which is to be used for requests, general FAQ, news and Docker template support, this will also include links to the support threads for each Docker image so should be a starting point for all new users.

 

I will be requesting that the moderators lock this thread but do NOT delete it.

[Squid]

This thread will be locked shortly, why am i doing this?, because this thread is getting far too long (over a 100 pages) and needs to be split out to a thread per Docker image, this will help users searching for answers to questions that may of already been asked and also make it easier for people to answer questions without the original question getting lost in the cross talk from other issues.

 

To prepare for this i have created a General thread which is to be used for requests, general FAQ, news and Docker template support, this will also include links to the support threads for each Docker image so should be a starting point for all new users.

 

I will be requesting that the moderators lock this thread but do NOT delete it.

Hopefully, you will also update the support threads within each template to reflect the new threads.

[binhex]

This thread will be locked shortly, why am i doing this?, because this thread is getting far too long (over a 100 pages) and needs to be split out to a thread per Docker image, this will help users searching for answers to questions that may of already been asked and also make it easier for people to answer questions without the original question getting lost in the cross talk from other issues.

 

To prepare for this i have created a General thread which is to be used for requests, general FAQ, news and Docker template support, this will also include links to the support threads for each Docker image so should be a starting point for all new users.

 

I will be requesting that the moderators lock this thread but do NOT delete it.

Hopefully, you will also update the support threads within each template to reflect the new threads.

 

i will indeed mate, its on my list to do (yes i have a list lol)

[femin]

I'm offering $20 for someone to help me setup DelugeVPN via Teamviewer/Skype.

 

I spent many hours try to get it working, i got all the necessary info,  and I know it's gotta be something simple and stupid that i'm missing.  please PM me with your contact.

 

 

[mr-hexen]

Did you update your auth file for your username / password?

[femin]

I can't even browse to the GUI,  port mapping is there, but page shows nothing when I browse to 8112 port.  I dont think it's even listening on that port,  i tried with putty to test that port, its not working.

 

I SSH'ed into the unraid server, and did all of below, still not browsable (I'm using Torguard so I changed to PROV to "custom",  and whatever necessary info)

 

docker run -d \

    --cap-add=NET_ADMIN \

    -p 8112:8112 \

    -p 8118:8118 \

    --name=<container name> \

    -v <path for data files>:/data \

    -v <path for config files>:/config \

    -v /etc/localtime:/etc/localtime:ro \

    -e VPN_ENABLED=<yes|no> \

    -e VPN_USER=<vpn username> \

    -e VPN_PASS=<vpn password> \

    -e VPN_REMOTE=<vpn remote gateway> \

    -e VPN_PORT=<vpn remote port> \

    -e VPN_PROV=<pia|airvpn|custom> \

    -e ENABLE_PRIVOXY=<yes|no> \

    -e LAN_RANGE=<lan ipv4 range> \

    binhex/arch-delugevpn

[JonathanM]

I can't even browse to the GUI,  port mapping is there, but page shows nothing when I browse to 8112 port.

The web GUI won't start if the VPN isn't connected. Are you sure you have all the needed modifications to the VPN setup to make it work with Torguard? I'm using PIA, so I don't know what all you have to change, but I'm sure it isn't insignificant.

[ulic]

I'm offering $20 for someone to help me setup DelugeVPN via Teamviewer/Skype.

 

I spent many hours try to get it working, i got all the necessary info,  and I know it's gotta be something simple and stupid that i'm missing.  please PM me with your contact.

Have you verified your username/pass in a desktop client?  Are you sure it's not different for linux?  My provider has a different username depending if I'm using a custom client (ie. not theirs).  Also did you put your ovpn file in config directory as instructed?

[binhex]

This thread will be locked shortly, why am i doing this?, because this thread is getting far too long (over a 100 pages) and needs to be split out to a thread per Docker image, this will help users searching for answers to questions that may of already been asked and also make it easier for people to answer questions without the original question getting lost in the cross talk from other issues.

 

To prepare for this i have created a General thread which is to be used for requests, general FAQ, news and Docker template support, this will also include links to the support threads for each Docker image so should be a starting point for all new users.

 

I will be requesting that the moderators lock this thread but do NOT delete it.

 

OK so i'm now ready to make this happen:-

 

ALL USERS THIS THREAD WILL BE LOCKED SHORTLY, PLEASE USE THE LINK BELOW:-

 

http://lime-technology.com/forum/index.php?topic=45811.0

 

Please note the above link is a general support thread, please use the separate support threads shown in the Docker Apps section of the first post when requesting help.

 

Moderators - Please lock this thread but do not delete, many thanks guys!.