betaman
-
Posts
614 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by betaman
-
-
I'm sharing how I finally solved this in case anyone else has this problem.
Solution: delete all credentials from 'Windows Credentials' and then create unique usernames for each user in unRAID that aren't the same as Windows ones.
So then you have your family members use the unRAID login credentials on the Windows machine to connect to your server? I was thinking of doing this for my FireTV's and Popcorn Hour units so I can control access better. I've also been reading up on ransomware and this has me a bit paranoid as well (i.e. using the same login with r/w permissions to my server).
-
Specify the IP address instead. 46.166.190.180
Thanks...was just about to ask if that would work (plus get the address)!
EDIT: Didn't work for me
EDIT 2: Now it's working...
-
Which gateway? The nl seems to work for most people.Been running this container for about a week using PIA.
Any ideas?
Having issues connecting to the Webui. I just noticed this in my supervisord.log:
2016-10-21 15:28:07,490 DEBG 'start-script' stdout output: Fri Oct 21 15:28:07 2016 RESOLVE: Cannot resolve host address: nl.privateinternetaccess.com: Name or service not known
All I did was update the container. Same issue with SABnzbdVPN from binhex after a container update?!
-
-
Anyone know how to downgrade mono in the docker? I see I have 4.4.1 and now having issues playing videos. I know there have been reported problems with Emby and 4.4.1. I can connect to the docker and see my version but no idea how to downgrade.
Thanks
Have you experienced any issues or are you just preparing for possible issues? I have upgraded to latest version and everything seems to be running just fine.
I'm running latest without any major issues as well. The only thing I note is the Safari browser isn't matching titles with coverart correctly but I think this is a "known" bug?!
-
Its use is in the description. RTFMIs the additional port "needed" for the VPN dockers? I get what 8080 and 8090 are for but no idea for 8118.
(At least it is in DelugeVPN, I don't use SABnzbdVPN but I assume he reused most of the same text.)Ah ok, it's used for privoxy.
-
More of a dockerMan issue than binhex's. Never really noticed, but 6.2 may stop you from duplicating ports (it at least shows you which host ports are already in use). Regardless of which version you're running, the docker run command would have pointed out the same error through the GUI at the bottom when adding / reinstalling / editing.LOL...that did it! Since I was using the defaults in both dockers maybe it's a good idea to change them in the templates to not be the same? Anyway, thanks for all of the help!
Is the additional port "needed" for the VPN dockers? I get what 8080 and 8090 are for but no idea for 8118.
it does = had the same problem once, removed the port on one of the vpn dockers
Myk
-
More of a dockerMan issue than binhex's. Never really noticed, but 6.2 may stop you from duplicating ports (it at least shows you which host ports are already in use). Regardless of which version you're running, the docker run command would have pointed out the same error through the GUI at the bottom when adding / reinstalling / editing.LOL...that did it! Since I was using the defaults in both dockers maybe it's a good idea to change them in the templates to not be the same? Anyway, thanks for all of the help!
Yeah, I would've thought the GUI should flag the same error. Perhaps I just missed it in the pop up window during the docker install? The weird thing is it said it installed successfully.
-
Yeah that's the idea, plus the environment variables (-e flags) basically take the example and replace it with your settings then paste it into your ssh session and see what happens.
Sent from my SM-G900F using Tapatalk
Ok, I think we made some progress! It says:
Error response from daemon: Cannot start container 6edb439f57e061a37224d5dc8e45a658c75a3a36198e0fd06768bad090bb3beb: Bind for 0.0.0.0:8118 failed: port is already allocated
I just noticed that DelugeVPN is also using port 8118?!
right, yes indeed that will cause you an issue, either change the host side port number to something else that isnt used or simply remove the port.
LOL...that did it! Since I was using the defaults in both dockers maybe it's a good idea to change them in the templates to not be the same? Anyway, thanks for all of the help!
-
Yeah that's the idea, plus the environment variables (-e flags) basically take the example and replace it with your settings then paste it into your ssh session and see what happens.
Sent from my SM-G900F using Tapatalk
Ok, I think we made some progress! It says:
Error response from daemon: Cannot start container 6edb439f57e061a37224d5dc8e45a658c75a3a36198e0fd06768bad090bb3beb: Bind for 0.0.0.0:8118 failed: port is already allocated
I just noticed that DelugeVPN is also using port 8118?!
-
does the docker need to start for the /config directory to be populated with files? I just tried a different /config directory and it still won't write any files to this directory. I let the docker create the new directory as well.
when the docker container has started and sabnzbd is running it will auto create files/folders as part of its initialisation of the app, creating sqlite db, config.ini etc, the odd thing with your situation is that it doesnt start at all, and by that i mean it doesnt even get to the first echo command, it literally is doing nothing, other than creating the /config folder.
one idea i thought might be fun is to get old school on it and execute it this via a good old docker run command and see it is gives you a hint as to what it going on, examples of using docker run are shown on the docker hub (see post 1 for a link to it) if your feeling up to this.
I reviewed the docker hub page. Would i just issue a command like this:
docker run -d binhex-sabnzbdvpn
Well...kinda, with all the other parameters too of course :-)
Sent from my SM-G900F using Tapatalk
Ok, I'm kinda of linux syntax n00b so something like this:
docker run -d --cap-add=NET_ADMIN -p 8080:8080 -p 8090:8090 -p 8118:8118 --name=binhex-sabnzbdvpn -v /mnt/cache/appdata/SABnzbdVPN/:/data -v /mnt/cache/appdata/downloads/:/config
Where the attributes are separated by spaces and <variable> is replaced by the actual name (e.g. replace <container_name> with binhex-sabnzbdvpn or should it be <binhex-sabnzbdvpn>)?
-
does the docker need to start for the /config directory to be populated with files? I just tried a different /config directory and it still won't write any files to this directory. I let the docker create the new directory as well.
when the docker container has started and sabnzbd is running it will auto create files/folders as part of its initialisation of the app, creating sqlite db, config.ini etc, the odd thing with your situation is that it doesnt start at all, and by that i mean it doesnt even get to the first echo command, it literally is doing nothing, other than creating the /config folder.
one idea i thought might be fun is to get old school on it and execute it this via a good old docker run command and see it is gives you a hint as to what it going on, examples of using docker run are shown on the docker hub (see post 1 for a link to it) if your feeling up to this.
I reviewed the docker hub page. Would i just issue a command like this:
docker run -d binhex-sabnzbdvpn
-
Try telling it VPN - no - and see if it starts up. I had the problem before with something wrong on the vpn side and it would not start up, Disable vpn - it would start up so then i knew something was wrong with vpn setup.
might help narrow it down
Myk
Thanks for the suggestion. I tried it with no change in behavior. One question I have is does the docker need to start for the /config directory to be populated with files? I just tried a different /config directory and it still won't write any files to this directory. I let the docker create the new directory as well.
-
ahh one thought, you dont have a /data" volume defined do you? i see you have renamed it /downloads instead, i do a chown and chmod on both /config and /data, if /data doesnt exist then its going to error, can you try changing the name to /data.
Ok, so I just added /data as an env variable and gave it the same path as /downloads. Pulled the image and still the same issue. Docker just refuses to start and no files are in the /config directory.
Thanks for trying. I'm in the process of replacing my cache drive with an SSD so I'll just do everything at once. I'll report back if deleting the docker.img file helped.
ok its got me stumped, re-create docker.img is the last thing i can think of, i would be surprised if that fixed it, but hey its possible i guess. all i can say is this docker does work, i have several people using it, if i pull it down from a clean state (no config present) then it starts fine, its an odd issue thats for sure!.
-
ahh one thought, you dont have a /data" volume defined do you? i see you have renamed it /downloads instead, i do a chown and chmod on both /config and /data, if /data doesnt exist then its going to error, can you try changing the name to /data.
Ok, so I just added /data as an env variable and gave it the same path as /downloads. Pulled the image and still the same issue. Docker just refuses to start and no files are in the /config directory.
-
that is an option but i didnt really want to suggest that unless i run out of ideas (which i nearly have hehe). ok last thing to check, can you double check the folder you are pointing at on the host side does exist, this has to be true for all of the volume mappings you have defined, also double check there is no accidental whitespace at the start or the end of the paths (both container and host paths) for all defined volumes.
Attached is the output of my /mnt/cache/appdata/ directory. I used the dropdowns in the docker config to avoid any typos.
-
wrong name, your container is called "binhex-sabnzbdvpn"
LOL...sorry. I forgot I left the default name to reduce variables. Now it is the exact same output.
ok now that is really wierd, so the container looks to do a big fat nothing, hmmm, ok cane you delete the container AND the image, then use the my templates again to select the config details you had earlier to repull it down.
one quick question, are you running anything on port 8080 or 8090 on your unraid host?, unmenu for instance?.
I did that exact procedure the last 3 times (hence the change to the docker name). It's as if the docker isn't really installing because the /config directory never populates with any files.
The only thing running on ports 8080 and 8090 is SABnzbd. I completely removed the non-VPN version to avoid any possible conflict but the same result. The only think I haven't tried is blowing away my image file completely and reinstalling all dockers. I was thinking of upgrading to 6.2 RC2 if I go that far though.
-
wrong name, your container is called "binhex-sabnzbdvpn"
LOL...sorry. I forgot I left the default name to reduce variables. Now it is the exact same output.
-
here is my folder and its contents
Myk
Which is exactly how the non-VPN SABnzbd folder looks (of course minus the VPN stuff). Where can I tell if the docker installed correctly or not? The syslog is not helpful and per my pic, the docker shows installed but stopped on my docker page. When I try to start it, nothing happens. I stopped the other SABnzbd docker (binhex version as well and works perfectly) to avoid a port conflict.
ok can you please ssh into unraid and run this command, it should give us a clue as to what is going on:-
docker logs <name of your sabnzbd container>
please paste the output here
i know youve stated above that the logs dont contain anything useful, but the above command should give us something.
also if you can screenshot your settings for the container, make sure to select the advanced view option so we can see all defined values, obviously hiding your username and password.
It's pretty much the same as before:
http://lime-technology.com/forum/index.php?topic=45822.msg482984#msg482984
Except now I get the notification there's no such container. If you review the pic I posted above, you can see the container is installed but not running. Log output works for SABnzbd and DelugeVPN (both are your dockers). See attached.
-
here is my folder and its contents
Myk
Which is exactly how the non-VPN SABnzbd folder looks (of course minus the VPN stuff). Where can I tell if the docker installed correctly or not? The syslog is not helpful and per my pic, the docker shows installed but stopped on my docker page. When I try to start it, nothing happens. I stopped the other SABnzbd docker (binhex version as well and works perfectly) to avoid a port conflict.
-
Not the application log, but the docker log.
Available at the docker tab in the unraid webgui (you may need to click advanced view)
Hmmm...can't find it. I tried both views. The log link is for syslog and the other logs are docker dependent with this one being blank?! Maybe a screenshot?
First one in on regular view, second one is advanced view.
In advanced view you can see then the log did get created, how long is has been for the last change/edit.
Just click there I have marked with red.
We were talking about the same thing. Mine says "none" which makes sense because my /config directory where the log is stored is completely empty.
-
Not the application log, but the docker log.
Available at the docker tab in the unraid webgui (you may need to click advanced view)
Hmmm...can't find it. I tried both views. The log link is for syslog and the other logs are docker dependent with this one being blank?! Maybe a screenshot?
-
No SABnzbdVPN log is generated since no files are being written to the /config directory and the UnRAID log is useless.
What about the docker log?
See above. The log is stored in the /config directory (/mnt/cache/appdata/SABnzbdVPN/) and nothing is currently being written to this directory during docker install. I think this is the root cause of my problem but I can't seem to figure out how to fix it.
-
ok im stumped for now, i will have to rack my brain for any ideas, just to double check i did a clean install here and it started with no issues
Ok, I've successfully got strong encryption running on your DelugeVPN docker but I still can't get this docker to start. One thing I noticed is that nothing is written to the /config folder (in my case, /mnt/cache/appdata/SABnzbdVPN/). The directory is however created successfully when pull down the image. Here's the folder permissions of my /mnt/cache/appdata directory:
drwxrwxr-x 4 nobody users 113 Jul 19 10:11 SABnzbd/ drwxrwxrwx 2 nobody users 6 Jul 19 11:33 SABnzbdVPN/ drwxrwxrwx 7 nobody users 256 Jul 19 10:58 delugeVPN/ drwxrwxr-x 3 nobody users 24 Jul 19 11:19 downloads/ drwxrwxrwx 13 nobody users 168 Jun 2 13:29 emby/ drwxrwxrwx 7 nobody users 232 Jul 19 13:04 sonarr/
All other dockers are working correctly and the non-VPN verison of your SABnzbd docker is also working correctly?! Still stumped...just thought I'd check back on whether there's any other info I can provide? No SABnzbdVPN log is generated since no files are being written to the /config directory and the UnRAID log is useless.
(At least it is in DelugeVPN, I don't use SABnzbdVPN but I assume he reused most of the same text.)
How To Permanently Fix "You Require Permission From Nobody" in Windows
in General Support
Posted
Thanks...that post explains a lot!