Jump to content

mr-hexen

Members
  • Content Count

    2295
  • Joined

  • Last visited

Community Reputation

10 Good

1 Follower

About mr-hexen

  • Rank
    Advanced Member
  • Birthday August 11

Converted

  • Gender
    Undisclosed
  • Personal Text
    My mITX build: https://forums.lime-technology.com/topic/33536-downsizing-my-unraid-e-atx-to-mini-itx/

Recent Profile Visitors

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

  1. Interested in any trades? I'm also in Ontario (Brampton / Oakville area) but can travel. PM me and we can discuss.
  2. I have a restart for 6.3.4 still pending, lol.
  3. I wonder if the unraidserver.plg can check for free ram before unpacking and post an alert if utilization is too high?
  4. Definately USD, as that would be almost half price CDN...
  5. Could not change the remote stream limit on the server side and/or client side?
  6. Your LAN network is defined incorrectly. It should be 10.0.0.0/24
  7. Too much money. Custom build one or get a used from eBay.
  8. You should only have the ovpn file for the server you are trying to connect to in the config /openvpn folder.
  9. What are path settings in Sonarr for post processing?
  10. Indeed, he's trying to work with "M:\ ..... " no way Sonarr on uNRAID is going to know wtf that is.
  11. Maybe the microserver isnt fast enough to transcode it in keeping up with a remote connection.
  12. Also, there are settings for remote quality in Settings on the android client.
  13. So some more reading has identified the KoD packet as a Kiss-of-Death packet, stemming from abuse of the NTP server. Did the system change the NTP polling interval from 6.3.2 to 6.3.3 at all?
  14. Seeing this every minute in syslog since. This update. ntpd[1607]: receive: KoD packet from 13.66.62.111 has inconsistent xmt/org/rec timestamps. Ignoring I've disabled ntp for now even though it seems harmless as it's been safely ignoring it for 3 days now. However it's a nuisance for sure.