Jump to content

misterbeetz

Members
  • Content Count

    58
  • Joined

  • Last visited

Community Reputation

0 Neutral

About misterbeetz

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Got a funny error with updating the Plex docker after going from 6.1.9 to 6.2-rc3... anyone know how to fix this? IMAGE ID [latest]: Pulling from limetech/plex. IMAGE ID [6ffe5d2d6a97]: Already exists. IMAGE ID [f4e00f994fd4]: Already exists. IMAGE ID [e99f3d1fc87b]: Already exists. IMAGE ID [a3ed95caeb02]: Already exists. IMAGE ID [ededd75b6753]: Already exists. IMAGE ID [1ddde157dd31]: Already exists. IMAGE ID [8d7d45a813c4]: Pulling fs layer. Downloading 100% of 771 B. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [eeb36e73ebd8]: Pulling fs layer. Downloading 100% of 117 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [9c89f037a839]: Pulling fs layer. Downloading 100% of 564 B. Verifying Checksum. Download complete. Extracting. Pull complete. TOTAL DATA PULLED: 117 MB Error: layers from manifest don't match image configuration
  2. Thanks Squid! I have narrowed it down to the Sickrage plugin that I have. I have also determined that the destination IP is one of the lesser known usenet trackers that I have enabled to search from. Oddly enough the packets seem to go through fine when the source IP is that of the unraid machine. They don't go through though when the source IP is 172.17.0.4 ... The only difference I see with the 172. packets is that they are TCP-RA rather than TCP-S. The other trackers I use do not trigger this behavior. Any ideas why source IP would flip flop like this?
  3. Just a quick question for the unraid wizards out there. My router setup allows me to track and block unapproved network connections and I see that there is one curious source that attempts outgoing connections on a regular basis from my unraid machine to the same IP in Europe. Normally I would expect the source IP to be the one I had assigned to the unraid box during setup ( i.e. 192.168.x.x) however the source IP in this case is always 172.17.0.4 I currently have a 6.1.6 setup with a handful of dockers (CP, SB, Plex etc), but no vms. Given that I am not a networking/IT guru... Does anyone know of a way that I can dig deeper and find from where these attempts are coming from?
  4. So I recently have gotten the itch to beef up the security on my network using OSSIM/OSSEC. In order to make this more effective I should install the agent software on all client machines and servers. Has anyone here put OSSEC on their Unraid box before? I've been spoiled by the dockers and plugins so its been awhile since I have installed something manually on Unraid. I encourage everyone to take a look at OSSEC if you are unfamiliar with it. It a great way to gain visibility of security related events in your network. Once installed OSSEC reports security events back to a centralized server (Alienvault, OSSIM, Security Onion etc.) so you can keep tabs on all machines on the network. Some examples of what OSSEC does: - integrated log analysis - file integrity checking - Windows registry monitoring - centralized policy enforcement - rootkit detection - real-time alerting and active response On top of that OSSEC is free and open source. Here are some links for further reading: en.wikipedia.org/wiki/OSSEC ossec.github.io/
  5. So PMS version 0.9.12.8 is the latest public release as of August 7th. I am restarting the limetech docker however it is not updating ... all it does is remain at 0.9.12.4 ... I'm confused. Edit: So deleting the docker and reinstalling made it go to 0.9.12.8 as expected ... not sure what happened there.
  6. Great success on the ZM docker! All feeds run in HD as expected. Thanks for your hard work!
  7. I also had some issues when switching over. You may want to try a new local config directory and start fresh. This is what ultimately worked for me...
  8. From within the docker tab make sure you click "update repositories" next to the search box. I didn't see the new stuff until I did that.
  9. I seem to have trouble getting this new ZM docker started. I wiped the config folder clean but no luck. It basically never starts so I don't get a log to see what is happening. Is this one confirmed to work with rc5? (I haven't tested it with rc4 yet. I will be away for the next few days so I will try again when I come back.)
  10. Any luck with that ZM docker? I'm ready for another round of testing
  11. This thing is really cool. I just got it working. I guess the trick here is to realize that pfsense typically sends out those logs to a specific port by default however the docker suggests a different one which is probably smart. I should also mention that graylog is another amazing docker that can be used to capture logs from pfsense in addition to anything else you would want (desktop syslogs, unraid main syslog etc.) It's in sparkly's beta repo.
  12. Thats alright. I know they take some effort in order to be done properly.
  13. Hey sparkly. I would like to give this one a go however the docker will not start at all (no log text available or config files in local.) Any ideas?