Jump to content

mr-hexen

Members
 View Profile  See their activity

  • 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. mr-hexen started following [SOLD] mini-itx Server for sale
  2. mr-hexen
    Interested in any trades? I'm also in Ontario (Brampton / Oakville area) but can travel. PM me and we can discuss.
  3. mr-hexen started following unRAID OS version 6.3.3 Stable Release Available, unRAID OS version 6.3.5 Stable Release Available, unRAID OS version 6.3.4 Stable Release Available and and 2 others
  4. mr-hexen
    I have a restart for 6.3.4 still pending, lol.
  5. mr-hexen
    I wonder if the unraidserver.plg can check for free ram before unpacking and post an alert if utilization is too high?
  6. mr-hexen
    Definately USD, as that would be almost half price CDN...
  7. mr-hexen
    Could not change the remote stream limit on the server side and/or client side?
  8. mr-hexen
    But does streaming work?
  9. mr-hexen
    Your LAN network is defined incorrectly. It should be 10.0.0.0/24
  10. mr-hexen
    Too much money. Custom build one or get a used from eBay.
  11. mr-hexen
    You should only have the ovpn file for the server you are trying to connect to in the config /openvpn folder.
  12. mr-hexen
    What are path settings in Sonarr for post processing?
  13. mr-hexen
    Indeed, he's trying to work with "M:\ ..... " no way Sonarr on uNRAID is going to know wtf that is.
  14. mr-hexen
    Maybe the microserver isnt fast enough to transcode it in keeping up with a remote connection.
  15. mr-hexen
    Also, there are settings for remote quality in Settings on the android client.
  16. mr-hexen
    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?
  17. mr-hexen
    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.