bigjme

So the part that wasn't working was the addition of a camera The option to close, minimise, and go full screen were all missing. Removing those options added the options in so everything looked like normal. The main blue iris interface worked fine as the close options are rendered into the app

Ok so fresh install onto the docker set, i'm mapping this to a specific ip on the network so i stripped out all the port forwarding, this is the command unraid is running docker run -d --name='blueiris' --net='br1.20' --ip='192.168.20.32' -e TZ="Europe/London" -e HOST_OS="unRAID" -v '/mnt/cache/blueiris':'/root/prefix32':'rw' 'jshridha/blueiris' Now that should match your identically besides the extra bits unraid adds Port 8080 loads as normal and vnc loads, but there is nothing on the display. I'm also seeing the blueiris installer downloading on repeat still as its not running For testing purposes, is there any way to get an output from the wine command to echo into the docker log? Or even remove the suppression on the wine installer so we can see in novnc what is happening? Regards, Jamie Edit Right ok so i got this working by ssh'ing into it manually So i ssh'd into the docker and fetched a copy of the bluriris installer using wget http://blueirissoftware.com/blueiris.exe into the /root/prefix32/drive_c folder All of a sudden the novnc showed the following 2 messages, i clicked install on 1 and 2, then was shown 3. Ok so thats fine So i manually just ran wine blueiris.exe Followed the installer and it launched without an issue. So next things next, i'm going to delete the docker, re-install it, connect to it via ssh and novnc, and repeating the same again will install it My thought is that the installer may be having trouble due to where its storing (in the docker file not in the user array) One thing i would like to note, the novnc resolution is tiny so setup and usage may be an issue as everything only just fits Edit 2 Ok, more bug checking So i found that after a fresh install onto a disk array, the /root/prefix32 folder is not owned by root, see image 4.png So, i ran chown root:root prefix32, instantly the novnc started to show the above warnings as posted in 1.png and 2.png So i restarted the docker, the installer started immediately however it does not self install. It stops on the screen 5.png Doing the install by hand finished fine (although you have to tell it not to launch blue iris 4 from the tick box else it will try to launch it again) I'm now trying the cameras for testing Edit 3 Ok so all installed, camera added, and all working I've had to make a few changes to use certain aspects of blue iris properly, run this from command line within the docker winecfg -> This should open the ui -> Graphics -> Disable everything -> Apply That's all fine and working. Its also recording perfectly fine with a single 3mp camera Its a little glitchy, and i would love if blueiris launches in minimised after the install but it does run...

@Bungy Do you have a screen shot of your configuration to ensure I don't miss anything? I will give this a try when I get home, just want to make sure the paths for recording are passed through correctly --Edit Ok so i finally got round to testing this and its not working on my side i'm afraid. Attached is every config screen, the output of accessing the docker via port 8080, and by connecting using vnc. Ooo and this is the docker log if its useful /usr/lib/python2.7/dist-packages/supervisor/options.py:297: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2018-04-03 21:00:55,006 CRIT Supervisor running as root (no user in config file) 2018-04-03 21:00:55,006 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2018-04-03 21:00:55,015 INFO RPC interface 'supervisor' initialized 2018-04-03 21:00:55,015 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2018-04-03 21:00:55,015 INFO supervisord started with pid 1 2018-04-03 21:00:56,017 INFO spawned: 'x11vnc' with pid 9 2018-04-03 21:00:56,018 INFO spawned: 'X11' with pid 10 2018-04-03 21:00:56,020 INFO spawned: 'progman' with pid 11 2018-04-03 21:00:56,021 INFO spawned: 'x11vnc-loc' with pid 12 2018-04-03 21:00:56,023 INFO spawned: 'novnc' with pid 13 2018-04-03 21:00:57,051 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: X11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: progman entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: x11vnc-loc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:00:57,052 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:02:43,909 INFO exited: x11vnc-loc (exit status 0; expected) 2018-04-03 21:02:44,910 INFO spawned: 'x11vnc-loc' with pid 59 2018-04-03 21:02:45,921 INFO success: x11vnc-loc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:02:54,432 INFO exited: x11vnc-loc (exit status 0; expected) 2018-04-03 21:02:55,434 INFO spawned: 'x11vnc-loc' with pid 61 2018-04-03 21:02:56,447 INFO success: x11vnc-loc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-04-03 21:08:50,611 INFO exited: x11vnc (exit status 0; expected) 2018-04-03 21:08:51,614 INFO spawned: 'x11vnc' with pid 62 2018-04-03 21:08:52,624 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Accessing via port 81 does nothing other than connection refused Regards, Jamie -- Follow up number 2 So i found out my firewall was preventing the docker from downloading the blueiris exe file which would make sense why nothing worked. So i unblocked this and re-installed the docker from scratch while keeping an eye on network traffic Having started the docker i have seen the blueiris installer download around 25 times now all fully downloaded to completion but nothing happens in the vm still. I've stopped the docker for now as it seems to have some sort of a problem with the downloads ( i can't see where these are downloading to within the docker files ) ---- followup 3 OK so Ive had a quick look, now I don't know how to write a docker or anything else but as the blueiris file is downloading on repeat I think the issue is in the blueiris.sh file My though is, your using wget to download the file, is it worth putting in full file paths to the installer? Right now it looks like it finished downloading, fails to install and therefore to run the program and just repeats the loop over and over I do have the path passed through for persistence which makes me think this may be the issue It's currently going via my normal user share so I may move the docker to store on a specific drive instead in case that's causing a problem --- edit 4 So I set the docker to store on a specific disk in the array and had the same outcome, the installer downloads, and then a few seconds later another download launches

Hi All, So with the latest release candidate of unraid you now get the option to specify the rom file for a gpu from the gui rather than having to use the xml. I've avoided looking at this at all as i often change the VM configs and didn't want to keep editing my XML's My server currently contains: 2 x GTX 750Ti's 1 x GTX 1070 I'm using one 750ti for a vm, and the 1070 for another leaving one 750ti for the host which is fine I'm finding the potential need to put an additional pci card into my server, but with 3 dual slot gpus and a sas controller already in place, i'm out of room - i'd also prefer not to have to put a single slot gpu in as i would love to free up 2 pci slots if possible So my plan is to remove a 750ti, and have the one for the host passed to a vm as well. I know its a nightmare but as its now becoming more common i may as well give it a try. My one catch is that i need to fetch the rom for the 750ti and assign that to the vm to pass it through, but my unraid server is my only physical machine so i have nothing to connect it to in order to extract the rom So here's my question, if i run gpu-z on one of my vm's and save the rom from there, is that rom going to be one like a physical machine would fetch and therefore be usable or is it likely to be completely wrong due to pass through and cause issues? Regards, Jamie

Think I'm going to have to follow this as I've been running blueiris for about 2 years now on a vm and I'm hating having to dedicate memory, cpu power, and space on a Windows install I've never compiled any dockers but if I can help in anyway, let me know

If you suppress the alert it will still block the connection, suppression just means it won't tell you when its done it, where as disabling it stops it triggering (thus allowing the connection) As you don't have snort on your lan then it isn't going to be snort blocking it. My recommendation would be to try pinging something you can access normally when you have say ssh errors and see if its still connecting fine. Just to rule out any sort of networking error

Honestly I hadn't played with snort much. I had it enabled on all my interfaces but mine was set to block bad traffic. So all I did was go into alerts and monitor the interfaces for a while. Clear the alerts and blocks, Try connecting to what ever was being broken and watch for alerts from ips in the subnet having issues. The just allow them as needed (red x in the far right of the alert) I had rather a few connections being blocked by snort going to my Web server so you may have some being blocked for streams etc. If blocking isn't enabled on the rules then it won't be snort as at that point it's just logging potential issues

OK so your having ssh issues and accessing dockers. Since your network is all vlan'd, have you checked your router isn't dropping/blocking any packets? For example i have my vlan and lan ports monitored by snort, some rules in snort were periodically blocking requests until I allowed the rule At the same time, I presume all your devices like your vm's and laptop can ping the gateway without issues when you loose access? I know one thing I found was that for some reason, when I added my vlans to unraid it crashes my network switch entirely. I had sporadic connections between the vlans until I rebooted it

How is your docker set up? Vlans, host, etc.

Well so far so good, i've got all the vlans set up for testing, just 2 web servers in it right now IP's are allocated and everything is routing as expected. I put a small script on the one server to try and connect to the other web server and then a resource outside the vlan and its working like a charm. One thing i have notices is my webserver can be accessed using port 80 from br0 but not on port 443 (ssl) I'm 100% sure this is down to firewall routing which i'm currently working on but worth mentioning in case its something odd that i would never expect in the docker system. Extremely unlikely but worth noting Regards, Jamie Edit Ok so i've found a problem/items worth mentioning, i set up in the docker config with the DHCP pool as 192.168.20.128/26 like in the guide, except this means that the dockers have a very odd default gateway in that range, i think it was 192.168.20.253 As all i'm using is dockers with fixed ip's i have disabled those DHCP pools entirely, told my router to never give out DHCP, and i can allow unraid to do the rest which gave the dockers a default gateway of .1 which fixed all sorts of ip routing issues and allowed the docker to access the internet when i allow it to in the firewall

Hi Bonienl Perfect, thank you I will have to have a play with this a little over the weekend Regards, Jamie

I think it's safe to say that you have saved me a whole mess of trouble trying to figure this out for sure! Thanks so much bonienl So the dockers have to be assigned an ip by unraids built in dhcp server so it can't get one off my router at all? Is there a reason behind this? More curious than anything

Hi Ken-ji Ok so i think i've got a better solution for this I have a managed switch that sites between unraid and my router. Whilst i've never done it before as networking is entirely new to me, would it not be easier to set up unraid to use vlans and just route everything that way? In short i would do as follows: Unraid uses br0 as always - from what i can gather br0 also broadcats on vlan tag id 10 as well? i.e. br0.10? VM's use br0 as well (as these shouldn't be restricted) Dockers are separated to different vlans based on where i want them (br.20, br.21 etc.) as these should be isolated entirely from everything else I then make my switch aware of all vlans that will be accessing it and of course set up the VLANs in the router. In this instance the switch should then receive the vlan'd packets, route them to other vlan'd ips automatically and anything not in the vlan is sent to the router where i can then route as needed for the internet and other networks. The dockers should then get an ip from the router in their appropriate vlan range (i presume) and i can then use the router to manage the communications between them. My only concern is that if i want to associate a static ip to a docker, it still won't be aware of the vlan ip range i presume and therefore i would have to just reserve the IP at the router level? I may be 100% wrong but as i'm off work now for Christmas, its a great time to start tatting (hopefully i can't break access to my entire network doing this) Regards, Jamie

Hi Ken-ji I think i've found the settings screen you meant in the gui. Was this the correct one? I haven;t messed with this just in case since i can't give anything names etc. I would presume this is likely correct as i can't find anything else but it doesn't seem to request half the fields posted in the instructions so i don't want to break anything This is likely something i'm unlikely to get a response from until people jump to 6.4 on official release so for now i will wait and see Regards, Jamie

Thanks for the reply I had a feeling I may have missed something or missunderstood the way things work, honestly I don't know fully how everything is separated by unraid in terms of network interfaces. Everything has changed a lot and I haven't really kept up to date on it. Vm's are using br0 at the moment and just get a normal ip off the router by dhcp. The vm's can also access my dockers which are almost all set up as either bridged or set as host (they have been set up over a year now) I can give my router dhcp access to the different docker ranges and also put it on the ip range if needed using a virtual alias so that's not a problem although I will likely block the docker access to the router on the Web and ssh ports to prevent potential issues All I'm trying to achieve at the moment is the following, it may be doable in a much easier way than I imagine due to the ip and system restrictions from unraid Set up 3 dockers; Web, database, mail on the ip range 192.168.20.0/24 Set up another set on the ip range 192.168.21.0/24 My vm's and private network are located on the ip range 192.168.0.0/24 via dhcp from the router I have a few vpn ip address ranges on the network as well So this is what I want to achieve. My private network can access the vpn ips and can access the docker ip ranges without limitation The docker ips can only access themselves so they can't access each other, my private network, or my vpns I would then have completely separated out 2 full sets of hosting assets which could be used without being able to interact with each other or my personal network To give an example of my current issue, I have my Web server docker set up as bridged. This Web server is able to do Web requests to my unraid and router login pages meaning if I was to allow other people to host files on this server, they could create a way for my unraid and router login pages to be accessible by the Internet, hence me wanting to isolate things and secure them down Again I may be being dim here and missing something simple that makes what I want very easy Regards, Jamie

Hi All, So this may have been asked before but i can't seem to find exactly what i need I'm currently attempting to desperate out and secure my docker's on my unraid server. I've been on 6.4 beta for a while now and didn't know the option for setting separate IP's existed until today as i don't tend to mess about with my docker layout due to it using so many different forwarded ports I have a number of web servers and database servers in dockers on my server and am looking to set up some mail servers soon as well. I know Dockers aren't extremely secure but i'm looking to use them to host various different things and potential allow access to the servers for use by others for hosting websites etc. What i would like to do is set all of my dockers into isolated IP ranges and then use my router to prevent access between the ranges so as to prevent them accessing my home network. So in essence i would like to be able to separate things like so to make the dockers a little more secure: Private Home Range: 192.168.0.0/24 Home VPN Range 1: 192.168.1.0/24 Home VPN Range 2: 192.168.2.0/24 Docker Range 1: 192.168.20.0/24 Docker Range 2: 192.168.21.0/24 In short the top 3 ranges can talk together, the 2 docker ranges should be able to only talk to themselves. I can set up rules in my home network to prevent the cross ip range talking but i need to check a few things: How do i allow the dockers to use the other ip range that is different to my main server ip range? I have this article but i'm not sure if the ip range change is supported or not when adding in different ip rnages: Since both the docker rnages would be using the macvlan driver, i know the dockers would be unable to access unraid due to security which is what i want to achieve however my concern is that as unraid does some internal routing for vm's accessing network drives for example, would the dockers try to route traffic internally to vm ip's and to other docker ip's thus bypassing any rules i set up in my network firewall as they stay routed internally to the server? i.e. would it still try and route the requests internally or would the requests go out and be view able (thus manageable) by the firewall on the network? Again, sorry if this has been asked before but i don't want to start adding in docker networks and altering firewall rules if its not supported yet Regards, Jamie

OK so this issue has been resolved I created a brand new vm with ovmf but change the machine to Q35-2.9 and it's working perfectly on a fresh install of Windows 8.1 Its a bit of a strange one and the issue really didn't look like a vm issue but rather a driver or Windows problem Perhaps this will help someone in the future Jamie

Hi Squid Tried that one now and on bare bones the gpu is working perfectly. Plays doom on ultra at over 200fps for hours on end with no issues I've remove all the drivers on my vm and tried again and the same thing happens. So I've tried a new power cable to the gpu, different power supply slots as it's modular, new motherboard bios, new windows install entirely and still get the same problem Windows is fine and runs at 800x600 with no drivers, it will even plays videos at that resolution. Install any nvidia driver and I get white lines all over the screen but their not in fixed places and move as I do stuff but make the entire system unusable, it won't even load youtube videos The other vm's on the machine with gpu's are all fine so it's isolated to this gpu Besides posting a system diagnostic, is there anything further I should try before doing so that may provide more needed information? So far I've pretty much done everything I can think of to resolve the issue, but I'm not a master like some of you here Regards, Jamie

Hi Everyone So I've just replaced my 780 with a new 1070 but I seem to be having issues with my vms The vm that has the 1070 is showing constant white lines across the screen. If I remove the nvidia drivers so it's showing a very low resolution, it seems fine but the second I install a video driver it gets the lines back. These lines occur all the time regardless of what is showing and I've tried different outputs, display port, dvi, and on different screens I've tried the latest drivers and gone back and tried the last 5 drivers available and it's the same on each one I've also tried the card on a different vm as well as trying it in a different pic express and am getting similar issues Before I get this card sent back as having a fault of some sort, can anyone think of anything else I can check to see if it's a card fault? I'm on the latest build of unraid with Windows fully up to date Regards, Jamie

Do you mean no video in the blue iris preview? It has a setting that can limit or even disable video when it detects rdp. I'm not sure which setting section it's in but I had to set it not to limit the video to get a decent video feed Jamie

That's true, I will give that a shot instead, my server gets very hot with it running so many vms so a minutes without cooling is a long time

Hi Squid, I didn't realise it was so easy to make the data so easily seen. I'm guessing it's not possible but I know cron normally doesn't have a faster speed than once a minute. Is there any way to make it look and check more often? Regards, Jamie

Hi Squid, The system integrates with a number of server checks for both my local and remote servers I need to be able to fetch the response by a php script for processing. The main script runs loops every 100ms for various things Ssh was the only way I could find to get the sensor data from the system unless there is a way I can get the data directly on the server without ssh that I can fetch by remote system? In short the system will monitor how long the temp has been over a defined threshold as well as sending text, and email alerts and ensuring the system is shut down correctly Eventually I want to expand it to check on more so I can remotely monitor the server when I'm out the country Regards, Jamie

Hi Everyone, So this is likely to be a very unusual issue or query for someone to have but here goes I have a system that SSH's into my server every second, runs the "sensors" command and reports the hottest core on the server. This is done as my server is 24/7 and water cooled so a peek in temperature for a while would indicate issues like dead pumps, fans etc. I did have a pump die a few weeks back hence why i'm adding this in Running this system would allow a pro-active shutdown before the cores got too hot and did a forced system shutdown Right now unraid adds a log entry every time the SSH user connects, validates the user, and disconnects which is great except for this system it means i am going to fill the logs very very quickly making it cluttered and filling my logs folder - also making diagnosing any other issues impossible I do know the ip that these requests will come from as it is from an internal docker - does anyone know of a way to prevent log entries for SSH from a certain IP? I understand the risk of disabling the logs for SSH entirely due to brute force attempts etc. so removing them from this 1 ip would be ideal I'm happy to try and alter the system to keep just 1 ssh connection open for ever and just push commands to check but this has flaws in itself so i would prefer to supress the logs unless there are other issues with having so many connections to the server 24/7 Help would be greatly appreciated Regards, Jamie

I'm on version 6.3.0-rc6 and didn't get chance to upgrade to rc9 (due to being busy). When checking for updates i now have none. When i try and install the plugin to get back to stable i am greeted with the following message: plugin: installing: https://raw.githubusercontent.com/limetech/unRAIDServer/master/unRAIDServer.plg plugin: downloading https://raw.githubusercontent.com/limetech/unRAIDServer/master/unRAIDServer.plg plugin: downloading: https://raw.githubusercontent.com/limetech/unRAIDServer/master/unRAIDServer.plg ... done plugin: not installing older version As it stands i'm unable to update unraid through the gui at all, any ideas? Jamie