[[Support] binhex - Jackett]

1 hour ago, jonathanm said:

Think of each container as a tiny VM. loopback only works inside each individual container. Container to container communication goes through the docker network.

Ohhhh that's true! I'm new to Docker and containers.

Thanks a lot Jonathanm.

[[Support] binhex - Jackett]

24 minutes ago, binhex said:

because if you set the url to localhost then radarr will try to connect to jackett using the localhost address inside the radarr container, obviously the radarr container is only running radarr (and not jackett) and thus it fails.

 

not sure what the difference is with the url's but mine works :-).

Thanks for the reply!

Yea but they both have their network set to bridge. Both have the same IP address. Wouldn't at leats the loopback work? Or am I missing something?

[[Support] binhex - DelugeVPN]

8 hours ago, binhex said:

yeah you are right, pia have changed their zipped ovpn config files and removed the extension, how annoying grrrrr. ok well you did the right thing, i will contact pia and see if they will change it to have the extension again, no promises though as pia support isnt too fantastic.

I have sent an email to them too. But maybe we should update the FAQ too  

 

[[Support] binhex - Jackett]

Hi guys,

Radarr would only work when the URL had the exact ip address of my unraid box, but it wouldn't if I set the URL as "localhost:9117(...)" or "127.0.0.1:9117(...)". Not sure why that is happening.
 

On 2/7/2018 at 8:55 AM, binhex said:

so for example you would configure sonarr/radarr etc with the following:-

http://<host ip>:<port number>/api/v2.0/indexers/all/results/torznab/

 

Right now my URL is set to "http://10.0.7.15:9117/torznab/all/". Is there a difference between that and the URL you mentioned, i.e. "http://10.0.7.15:9117/api/v2.0/indexers/all/results/torznab/"?

[[Support] binhex - DelugeVPN]

Hello guys, I was having an issue and managed to solve it, However I'm not sure if this is the right place to post it.

 

I downloaded the OVPN files from PIA and copied all the necessary files and the supervisord.log kept showing there were no OVPN files... Took me too long to finally see that the OVPN file did not have the ".ovpn" extension. I simply had to edit the edit to add the extension and everything worked fine.

Every one of the files was missing the ".ovpn" extension. I downloaded it again to verify and could confirm. I'm not sure if this is for some reason only happening with me.

[Container issue, port 80 access and own IP address]

42 minutes ago, bonienl said:

macvlan support is built-in in unRAID version 6.4, currently available as RC. This will allow you to make assignments from the GUI.

 

If you decide to use version 6.4 then make sure you delete all manually added macvlan assignments, these can not be used together with the new functionality in 6.4.

 

Thanks Bonienl! I was looking the changelogs and new features for 6.4 and it looks really nice. I will delete the assignments and do some backups before trying it out. 

 

Maybe editing the emby's xml would make the webui to be listened on port 80... I will try that now and report back.

No success in editing the system.xml or even the emby's template xml... Have no idea where its the config that a container must use such port.

[Container issue, port 80 access and own IP address]

Hi guys, I'm not sure if this is the right place to post this and since this is my first topic I apologize in advance for any mistakes.

 

As the title says, I have been trying to run an Emby docker with it's own IP and its WebUI accessible via port 80. That way any user on the local network can access it by just typing the hostname instead of typing "hostname:8096" on the browser.

 

I was able to configure it to have its own IP by creating a network with macvlan drivers called "embynet". But I'm having no success in enabling it to be accessible by port 80.

docker network create -d macvlan --subnet=10.0.7.0/24 --ip-range=10.0.7.128/27 --gateway=10.0.7.1 -o parent=br0 embynet

 

The docker run command I used (IIRC as I ran it a couple of months ago) was something like this:

docker run -d --name=Emby-server --net=embynet --ip=10.0.7.154 -p 80:80 -p 443:443 -p 7359:7359/udp -p 1900:1900/udp -e TZ=America/Sao_Paulo -v "/mnt/user/Media/":"/mnt":rw -v "/mnt/user/appdata/EmbyServer":"/config":rw emby/embyserver

 

I tried to run the command with the port variables in many different manners "-p 80:80 -p 443:443", "-p 10.0.7.154:80:80 -p 10.0.7.154:443:443" etc... and nothing worked. the Emby container was always listening on the same 8096 port. I also tried configuring the port inside the WebUI config with no success.

 

I'm thinking about running the Embyserver on a windows server VM that I already have, or maybe try this again on unraid 6.4...

 

I'm not sure what's the workaround for this... Do you guys have any clue or is there a different route to accomplish this? 

I do understand that making a container listen to port 80 would cause issues with unraid, but since the container has a different IP I don't see why I shouldn't do it...

[***GUIDE*** Passing Through Network Controllers to unRAID 6 Virtual Machines]

On 13/04/2016 at 11:35 AM, saarg said:

 

You should try this from the unraid wiki

 

The extra line added is supposed to be added. It is the address inside the specific VM. So nothing to worry about.

 

 

 <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>

 

 

 

OMG! Thank you so much Saarg, I've been trying the whole day to passthrough my dual interface Intel NIC.
Tried with and without the "pci-stub" and "vfio-pci" in the syslinux config. Also tried to pass just one of the interfaces.... Tried so many things until i stumbled upon your post with the link for the "vfio_iommu_type1.allow_unsafe_interrupts=1" command. This should be added to the OP's post, I think.