Master_of_None

Hello, Not sure if this has been resolved and/or even know the whole story as didn't read rest of replies, so please excuse me but from up above, i would put back the firewall rule to block vlan20 to main lan. I dont know what you are using for firewall or your setup but by default, firewall rules should process from top to bottom. That being said, above the rule you just set, i would make another rule to allow, from vlan20 for the application, ip address, port on the main lan. This will allow that app to communicate from vlan 20 to main lan and nothing else. Hope this works. If your rules are blocking the opposite way, you will need to create another rule from the other side from host network to vlan20. Hope this helps and as I said, not sure of whole story.

Never Mind, I just deleted the network.cfg file and started over. I have backed it up so now I have the file I wanted.

Hey guys, I know this has been discussed before but couldn't find my answer. I don't think what i am asking has been asked or answered yet but if it has please forgive me as i couldn't find it. I am asking if anyone can tell me what the last lines of the network.cfg file is. I changed my gateway through the gui and for the life of me I have no clue why i put the wrong address in, not thinking, but right after that the gui was inaccessible. So i went into console and edited the network.cfg file using vi and deleted the last lines at the end after, i believe, bro(0). Now when i boot up my system isn't pinging as it can`t read the whole network.cfg file as the last lines aren't there. I used to have a copy of that file but can't find it. Can anyone tell me what is at the end of the file that closes it out so unraid can read the entire network.cfg file so my unraid box will come back online. Any help is appreciated, Thanks and sorry for the dumb question. EDIT:: If at all possible i would rather not delete the network.cfg and rules file and start over. Thanks!

I updated to newest version of this docker and after updating I am getting a can`t login error after 15 seconds. I have attempted to login repeatedly with same error. UPDATE: I stopped the Crashplan Pro docker and then started it again. After that I was able to login without an issue. Just an FYI for anyone experiencing the same issue.