Nem

Members
  • Posts

    177
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

Nem's Achievements

Apprentice

Apprentice (3/14)

4

Reputation

  1. Planning on building a new server. Would like to get a quick sanity check on components in terms of compatibility (with each other, and with unraid in general). I'll be migrating a few drives over from my current system (7 drives in total) Link: https://ca.pcpartpicker.com/user/nem2k/saved/C7yTHx Use case: # of concurrent users for all of the below: 2 Emby (iGPU transcoding) Media management (Radarr, Sonarr etc) Web server MySQL database for some side projects File server for backups Nextcloud Wireguard Will eventually be installing a GPU (3070) and passing it through to a VM for some machine learning things once in a while Might run a 2nd instance of pihole here incase my primary goes down Questions: Will the cooler fit inside the 4U case? Is the PSU overkill? Is the RAM compatible? (dont see it on the QVL for the motherboard) In terms of PCIe, eventually I can see myself filling the slots with GPU, HBA, 10Gb NIC. The GPU will likely be a dual slot card, rendering one of the PCIe inaccessible. How do people usually get around a problem like this? Was originally aiming for a 2378G, but those things are impossible to find. How much of a real world performance drop will the 2176G be? Instead of the Xeon/ECC/C246 combo, I was also considering a more consumer-level setup based on a 10th gen i7. Any major benefits one way or the other? Any other potential pitfalls to watch out for in terms of unraid compatibility?
  2. I've been eyeballing some of the new Xeon E-23xxG CPUs for a new server build, for example, the E-2378G (https://www.intel.ca/content/www/ca/en/products/sku/212262/intel-xeon-e2378g-processor-16m-cache-2-80-ghz/specifications.html) I see that it was released Q3'21, but have not been able to find a single retailer to purchase the CPU from in Canada Is this because of current supply chain issues causing low supply? Or is it because server-grade components don't reach consumer outlets until a while after their launch date? (I'm not sure how enterprise and consumer markets differ in terms of rollout schedules) In essence, when might I realistically be able to get my hands on one of these? If it's supply chain issues I can just keep searching and hoping for stock, but if its because consumer rollout is typically delayed then I might just look at the 22xx series instead...
  3. ah I didn't have the my servers plugin installed, so it all works now after installing that and forwarding some ports. thanks!
  4. @ljm42 tried a couple of tests... > ping rebindtest.unraid.net Pinging rebindtest.unraid.net [192.168.42.42] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.42.42: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), > ping <personalhash>.unraid.net Pinging <personalhash>.unraid.net [192.168.187.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.187.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), In the second case, it is trying to resolve <personalhash>.unraid.net to my old unraid ip (192.168.187.10), rather than the new one (192.168.1.10)
  5. that seems to work, thanks I think I'm confusing myself with my own setup. why does :4343 work, but not :8181? also, how does the redirect to xx.unraid.net:4343 fit into the picture? what is the purpose of that? that is the page that :8181 redirects me to, but now just leads to a connection time out (it used to work in my old apartment)
  6. https://192.168.1.10:8181 doesn't work. It doesn't even seem to redirect me to xx.unraid.net:4343. I just immediately get a ERR_SSL_PROTOCOL_ERROR
  7. I used to run my unraid machine at 192.168.187.10. Under management access, I had the HTTP and HTTPS ports set to 8181 and 4343, because 80 and 443 were being used by a docker container Therefore, on my local network I would access the webGUI at 192.168.187.10:8181 I just moved to a new apartment and set up a new network under 192.168.1.x. I went into the webGUI and set the static ip to 192.168.1.10. I seem to be able to access my shares and docker containers just fine, but I'm unable to reach the webGUI at 192.168.1.10:8181. It redirects me to xx.unraid.net:4343, where I get `ERR_CONNECTION_TIMED_OUT` ... is there something else I need to change somewhere? How much of this is due to incorrect settings, vs having a new public IP as a result of being in a new apartment and new ISP?
  8. I can only seem to find WDxxFFBX drives. Example: https://ca.pcpartpicker.com/product/2PYLrH/western-digital-red-pro-4tb-35-7200rpm-internal-hard-drive-wd4003ffbx Are they the same as EFZX?
  9. I've been using nothing but WD Reds (WDxxEFRX) in my server, which I believe are CMR drives, but it looks like theyre not being made anymore and are becoming harder to find. The newer alternatives (WDxxEFAX) are SMR drives, which I understand are not as good for NAS performance? A few related questions: 1) Is it ok to mix drives from different companies? For example, if I wanted to add some Seagate IronWolf drives to my current WD array? 2) What is the difference between IronWolf/NAS/Pro models? And are they CMR/SMR? 3) How are the IronWolf drives compared to WD Red? Any other companies that are recommended? The new drive will be used as a parity drive (for now). As a parity drive, it would have to be at least as large as my largest array drive, but I'm not sure if a 6GB Seagate is exactly the same size as a 6GB WD Red
  10. There is an apparent memory leak associated with the Mono version of Jackett. On my unraid server I end up hitting 100% memory usage after a few days. This affects more than just Jackett (Radarr, Sonarr etc), and one proposed solution is to switch to the .netcore version of Jackett. Is that possible with this docker? Source: https://github.com/Jackett/Jackett/issues/4088
  11. I have a VPN_REMOTE key in the container options. I think it may be from an old config. Is that still required, and if so, what should I manually set the value to?
  12. when you first install v3, it should launch a wizard to set up the server and to create an admin account. I dont believe theres a default admin account I had a similar problem when I installed v3 - think there were some settings or cache that was retained from my previous v3-preview container. Try clearing your cache or reinstalling the container (manually delete the appdata config directory)
  13. I changed my ciphers within the webgui itself. under advanced VPN config, I just added `cipher AES-256-CBC` to the server and client config directives
  14. any idea when the template on the community applications page will be updated? It still seems to install v2
  15. nice. has the lsio container been updated to 3.0 yet? currently using the lsio dev preview and would like to switch over to the more stable public release