Nem

Members
  • Posts

    175
  • 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)

3

Reputation

  1. ah I didn't have the my servers plugin installed, so it all works now after installing that and forwarding some ports. thanks!
  2. @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)
  3. 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)
  4. 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
  5. 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?
  6. 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?
  7. 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
  8. 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
  9. 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?
  10. 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)
  11. 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
  12. any idea when the template on the community applications page will be updated? It still seems to install v2
  13. 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
  14. I just updated my container (lsio-preview ombi 3) and the page is only half loading (menu shows, but nothing else) and devtools is showing the following error: ERROR Error: Uncaught (in promise): Error: No NgModule metadata found for 'undefined'. Error: No NgModule metadata found for 'undefined'. at t.resolve (vendor.js:1) at t.getNgModuleMetadata (vendor.js:1) at t._loadModules (vendor.js:1) at t._compileModuleAndComponents (vendor.js:1) at t.compileModuleAsync (vendor.js:1) at t.compileModuleAsync (vendor.js:1) at e.project (vendor.js:1) at e._tryNext (vendor.js:1) at e._next (vendor.js:1) at e.next (vendor.js:1) at t.resolve (vendor.js:1) at t.getNgModuleMetadata (vendor.js:1) at t._loadModules (vendor.js:1) at t._compileModuleAndComponents (vendor.js:1) at t.compileModuleAsync (vendor.js:1) at t.compileModuleAsync (vendor.js:1) at e.project (vendor.js:1) at e._tryNext (vendor.js:1) at e._next (vendor.js:1) at e.next (vendor.js:1) at O (vendor.js:1) at O (vendor.js:1) at vendor.js:1 at t.invokeTask (vendor.js:1) at Object.onInvokeTask (vendor.js:1) at t.invokeTask (vendor.js:1) at e.runTask (vendor.js:1) at m (vendor.js:1) at <anonymous> It @ vendor.js:1 vendor.js:1 Uncaught (in promise) Error: No NgModule metadata found for 'undefined'. at t.resolve (vendor.js:1) at t.getNgModuleMetadata (vendor.js:1) at t._loadModules (vendor.js:1) at t._compileModuleAndComponents (vendor.js:1) at t.compileModuleAsync (vendor.js:1) at t.compileModuleAsync (vendor.js:1) at e.project (vendor.js:1) at e._tryNext (vendor.js:1) at e._next (vendor.js:1) at e.next (vendor.js:1)
  15. I just upgraded to 6.4.1 and on my main dashboard I'm seeing warnings regarding a couple of drives and their SMART status The warning is UDMA CRC error count: 1 and CRC error count (no UDMA): 1 Can anyone explain what these errors mean, whether theyre serious, and what can be done about them?