Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vw-kombi

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just wanted to say to @ken-ji - Tnaks heaps - all working perfectly and now I can track and qos everything via IP address in my router.
  2. Ahhhhh. @ken-ji - Thanks for that..... I did not know that. So, the nginx container setup - where I enter port 85 and 4443 are negated when the nginx container is changed to its own IP address...... So I just needed to change the port forward in my router to 80 and 443 to the new nginx containers IP address - If I am understanding you correctly, then that would link the internet to the nginx container. How then do the other containers work ? with all their ports, once they also have their own IP address ? As they are 'talked to' locally from nginx - that will all be fine correct ? For example : emby - 8096 default in the app sonarr - 8989 default in the app radarr - 7878 default in the app etc etc
  3. OK - So I need some help with what I am trying to do - a simple yes/no on if this is possible, as I seem to have an issue with my proposed config. To recap the end solution - no vlans, one nic in unraid - I just want to set the IP address on my emby container. Currently, all docker containers are on bridge mode and work (obviously) and talk to each other and the unraid host. I have a router port forward of 80 and 443 to my nginx container on 85 and 4443. All been working for ages. After getting some answers in here (from a helpful @ken-ji), I found out that once I set an IP address on a container (emby), it can no longer be talked to the unraid host ip. So the solution as posted earlier was to set IP addresses on ALL my containers. So, I set ip to my nginx container, and for my emby container. Updated the nginx config for this IP address for emby, and changed the port forwards on the router from (unraid host) to (nginx container). It does not work - I cant access nginx remotely. I checked nginx logs and nothing is getting to it. I used the router to test the port from the wan side (pfsense), and not getting through to nginx. My port forwarding is correct - I only changed a .7 to .5. I have surmised that the WAN cant get access to the nginx container IP. Is there an issue with routing / port forwarding to a docker container that has a br: Custom IP address set ? Please help.
  4. Sorry - My Bad. The ones I was testing with had individual issues with the router vpn affecting their internet. I tested the ombi container, started with new virtual IP address, used it and it can connect to the internet fine. So my plan is to change the following containers to have BR Custom IP addresses - as they are all related to each other and need access between many of them : nginx emby ombi tvheadend sab deluge sonarr radarr Jackett I also have a VM web server that is also needed to be connected from the nginx container but I believe this will be fine. Then they can all communicate to each other and I believe only access host via the container options on start up. Or so I believe. Have to plan a time for this test as the nginx is in use often If anyone thinks I am on the wrong track, please advise.
  5. Hi - I now have VPN running on my router so dont want to use the vpn built into the clients. To remove this from using its configured VPN - is it more than just the changing of the vpn to 'no' ? I tried just that and while the webgui came up, I was not able to connect to sab from sonarr then.
  6. hhhhmmmm - so I am missing something here. The containers I change to have their own IP address cannot connect to the internet. Do they have to have the gateway set somewhere ?
  7. Nice 1. Thanks for that. Will get that done. I will one day get a new vlan switch. Router is pfsense so no worries there.
  8. OK - I did a load of googling / searching and I think the issue is that the virtual IP allocated container is not allowed to communicate to the unraid host IP (where nginx is runnng as a container). What I have is an nginx container as host which currently redirects to all the containers also on host, so when I separated the emby container to its own VIP, then nginx could not communicate with it. Apart from adding actual physical NIC's to the unraid server, or buying a smart vlan capable switch, what are my other options ? If I give every docker used by nginx, and the nginx container also a virtual IP address, can they communicate with each other then ? nginx, sonarr, radarr, sab, deluge, ombi and a web server Thanks
  9. I wish to change my emby docker so it has its own virtual IP for QOS/Routing etc. I only have the one nic in my unraid server. I noticed this was all possible when I recently created a pihole docker based on space invaders video. So, a simple edit on the docker, changed to Custom : br, then put the new IP address in it. All starts fine, and all works locally. I then changed the nginx reverse proxy for the emby subdomain to be the new ip address (simply changing to Restarted nginx My emby server is no longer contactable from the wan. All others remain fine. I'm thinking this is some sort of routing issue with this virtual IP but I have no idea where to look. As I cant have emby down for long, I set it back as it was and all good. I am now using my ombi docker instead for this testing. Thanks.
  10. hhhmmm - OK, Thanks for the reply. I may be able to do this from my asus router (running merlin). I have posted a question on that forum.
  11. Hi All. Im not too technical here so sorry for the questions. Can I put this cf-ddns.sh in a user share ? Can I create the calling script in user scripts where I have all my other bits and pieces ? The reason I ask is that I did this all, made the cf-ddns.sh executable and edited the calling script to /mnt/user/Scripts/cf-ddns.sh -k $CFKEY -z $DOMAIN -u $USER -h ${i}.${DOMAIN} , and ran it via user scripts and I got this : /usr/bin/env: 'bash\r': No such file or directory /usr/bin/env: 'bash\r': No such file or directory /usr/bin/env: 'bash\r': No such file or directory Script Finished Mon, 25 Mar 2019 18:39:48 +1000 Sorry - likely a noob question.....
  12. I just installed this, all configured and cool. For some reason, in the search for movies and tv shows, the 'Suggestions' dropdown shows the others (popular etc) but you cant select them, click on them and it is always suggestions..... I tries two browsers - same issue. Thanks.
  13. OK - I stripped out all the nice to have and only left the ones I have stuff for - and it still failed, so I stripped them all out and left the default oones you had and it works. Now I can add them back one at a time (I copied the text). Thanks for the help.
  14. Hi, OK, added this, start docker, and it seemed to be doing loads of stuff in the log for the docker on startup, but eventually crashed asgain, and the log shows this below : Thanks npm ERR! Linux 4.18.20-unRAID npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--unsafe-perm" "homebridge-pilight" "homebridge-info" "homebridge-wemo" "homebridge-roku" "homebridge-weather-plus" "homebridge-foscam-nextlevel" "homebridge-sonoff" "homebridge-music" "homebridge-xiaomi-roborock-vacuum" "homebridge-broadband" "homebridge-yamaha-home" "homebridge-ewelink-max" "homebridge-openhab2" "homebridge-apple-tv" "homebridge-konkeplatform" "homebridge-lifx-lan" "homebridge-ewelink-plus" "homebridge-garadget" npm ERR! node v8.10.0 npm ERR! npm v3.5.2 npm ERR! code ELIFECYCLE npm ERR! sodium@2.0.3 preinstall: `node install.js --preinstall` npm ERR! Exit status 1 npm ERR! Failed at the sodium@2.0.3 preinstall script 'node install.js --preinstall'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the sodium package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node install.js --preinstall npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs sodium npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls sodium npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /npm-debug.log