surfshack66

Yes. I add the custom routes in the network settings page. They do not persist after rebooting. Is that normal? I figured they would persist.

Does anyone have some advice for this issue?

Looks like someone posted about this docker recently.. I was able to install blueiris by following this, however, I don't have the unraid particulars set correctly because my settings don't persist a reboot. I'm also not entirely confident on the path mappings I created. @bigjme Would you mind posting your path/port mappings? You also mentioned some registry edits in your previous posts...is this still needed? Thanks for your help. Excited to get this off my VM.

The error happens when the script runs...which is after rebooting the server and, subsequently, after the array starts...

Thanks @Jclendineng I added the script but received an error sysctl: cannot stat /proc/sys/vm/max_map_count: No such file or directory I attached a screenshot of the script

I have those stats fed to Grafana. Telegraf (docker) collects the data and feeds to influxDB (docker). Grafana reads from influxdb. Theres a popular reddit how to if you search unraid grafana...

@zandrsn Did you ever figure this out? I want my cyberpower ups stats in grafana as well. Instead of a VM, its possible (although not sure how to do this exactly) to install PPBE in a docker using WINE....

@sparklyballs Are you interested in this docker? I believe this is something similar to your pf-logstash docker, which I used prior to 2.4

The custom routes I enter in the routing table do no persist a reboot. Is there a way to make them stick?

Found this recent thread referencing the ELK docker. Tried the script @Jclendineng mentioned, but received an error sysctl: cannot stat /proc/sys/vm/max_map_count: No such file or directory Is no one else using an ELK stack?

Looks like Elasticsearch is failing to start. Two reasons for failing that I see are.. 1. Max file descriptors need to increase 2. Max virtual memory areas need to increase Supposedly, this is a fix for the second issue, but not sure if I want to be messing with unraids max_map_count. Anyone from Linuxserver.io interested in making an unraid compatible container for this?

Hi - I'm interested in using this docker image, but ran into a few issues trying to start it. https://hub.docker.com/r/sebp/elk/ Has anyone else successfully implemented this docker? Has anyone tried installing three separate containers of Elasticsearch, Logstash, and Kibana? Looking forward to the responses because having this log server would be awesome to complement Grafana! EDIT: Changed the topic from "Request ELK Stack" to "Elastic Stack Setup", since Beats has been added to the stack.

Thanks. Just wanted to double check because I didn't see it defined explicitly on https://hub.docker.com/r/linuxserver/letsencrypt/

Can we run this docker in a custom bridge mode with a fixed IP address, i.e. not host?

It has to do with vlan hopping, which is a potential security threat. Out of curiosity, do you have unraid in your LAN or one of the vlans?

The nguvu guide, and pfsense experts, recommend using an unassigned parent interface. The parent interface refers to the physical interface where the vlans will reside. So that is what I did. I have a 4 port nic, so em0 is wan, em1 is lan, and em2 is unassigned but used as the parent interface for the vlans. That being said, I changed vl20 parent interface from unassigned em2 to an already assigned em1, i.e the LAN. I'm now able to communicate with the docker from unraid and vice versa. I'll probably take this to the pfsense forum for more support, so I'll mark this solved from unraids perspective. However, I'd still like to follow the recommendation of not using an assigned parent interface. @DZMM what parent interface did you use?

VLAN ID of VL20_VPN = 20 physical interface is em2, which is an open port of the 4 port nic assigned to pfsense So is it safe to say unraid config is fine? Might be able to solve this by process of elimination...

Yes, this is not good. I posted all the screenshots of all my config. Anything else I can take a screenshot of? EDIT: added screenshot of VL20_VPN interface on pfsense

Sorry for the confusion. Hopefully this will make things clear. Desired behavior - Docker (192.168.20.3) in VL20_VPN to succesfully ping unraid (192.168.1.2) in LAN Actual behavior - Docker cannot ping unraid To make things simple for the sake of solving this issue, I have created a rule on VL20_VPN (at the top of the rule set) to allow ANY protocol from ANY source/port to ANY destination/port. This rule should eliminate any issue with pfsense configuration, so all that is left is either unraid config or the switch config.

Just to make sure I'm testing properly. 1. Select docker console 2. Ping 192.168.20.1 This test does not yield a response

Dockers in bridge mode can ping the router 192.168.1.1 Docker in VLAN cannot ping router. Does this have something to do with DNS, similar to this post? I posted in this yesterday (before starting this thread), but haven't heard a response.

When you say "have you tried the other way" do you mean pinging unraid from the docker? If so, yes I tried that as well but no response. Also, here is a screenshot of my lan rules.

Those guides are great! Yes, I do. The rules can be confusing if you're not familiar with the guides, but ultimately I'm looking for the second rule from the bottom to kick in and it does not. Unraid is 192.168.1.2 on the LAN net. Docker XYZ is 192.168.20.3 in VL20_VPN. The rules don't allow traffic from LAN to communicate with VL20_VPN, hence why I'm looking for the "VL20_VPN: Default reject ipv4" alert in firewall logs.

I use the windows VM as my main workstation, so I have 4 cores and 8 gb of ram assigned. As far as the cams, I have a DS-2CD3132 outside, but it looks like it's no longer available. I also have a rebranded hikvision doorbell cam https://www.amazon.com/gp/product/B077KW2T1H/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 Both cams have performed well and served the purpose. Blue iris is also well worth it and has a convenient mobile app.

I'm having the same issue as @DZMM and followed the recommendations from this thread. However, I'm still having an issue where unraid cannot reach a docker in a vlan. I've taken screenshots of my settings below. Would someone mind taking a look? Capture - unraid network settings Capture2 - docker settings 3 - unifi switch uplink port config 4 - unifi switch unraid port config 5 - switch port config, "all" = native LAN and tagged vlans 6 - vlan20 firewall rules 7 - routing table The docker in question is in VLAN20. Unraid is in LAN. As you can see in "capture6", the block rule "VL20_VPN: default reject ipv4" rule prohibits unraid from communicating with this vlan (because the allow rules are only for VL20_VPN Net). This is by design. However, this reject rule generates logs on the firewall and I'm not seeing any alerts. I've tried pinging/traceroute too.