sjaak

Members
  • Posts

    180
  • Joined

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

sjaak's Achievements

Apprentice

Apprentice (3/14)

13

Reputation

  1. i know, dangit, just test another nic with a static ip, i can access the gui... ssh is only listening to eth0 nginx is indeed listening on 0.0.0.0 and ::: so it is open on the other networks. i don't have enabled unraid to use ipv6, only some dockers and VM are using ipv6...
  2. i cant connect with ssh to unRAID on the second NIC, bind_mgt works fine for me... also nginx is only listening on eth0. i don't have ssl enabled so no listening on port 443 SMB/NFS is not affected with this setting, its not a management thing...
  3. just checked and indeed its 1/2 of the RAM. i always know that the / is full Disk (with unRAID RAM) but not with unRAID anymore... but still i prefer to limit the temp usage for docker containers, its better to let a docker container crash then have unRAID crash ;)
  4. You know that manual created files in /tmp will be gone after reboot? unless you created a script that create the file at boot... i personally recommended not to use /tmp for Plex etc. its better to use /dev/shm/ /tmp is full RAM, /dev/shm/ is 1/2 RAM..
  5. VM manager doesn't need python 2, "Libvirt Wake on lan" needs it, solution for now, temporary remove libvirt wake on lan plugin
  6. updated form 6.9.2 to 6.10rc1, Update when fine, everything came back online without any problem. but some things: - that "sign in" button is pretty big, would love to have an option to hide it. or better; disable it fully from my server! - why do i have in folder on my usb stick called "dynamix.my.servers" (boot/config/plugins)??? i didn ever touch this plugin, would never do, i don't use cloud stuff, this fiels like my server is now doing background crap to the "cloud" (i am going to monitor this) - under: settings > Management Access, there are options for "My server", i didn't install the plugin! (isn't this 'UPC' ?? ) - looks like not every plugin is ready for this version, FixCommonProblems isn't showing any old ignored warning anymore, extended scan take pretty long, 2 hours and it isn't finished yet. (previous it take not more then 30 minutes...) nerdpack isn't fully working, previous i had idle3-tool and powertop installed, on 6.10 they aren't installed anymore.
  7. i have backups for that so no problem. ( i hate the "cloud", its just someone else computer...) but after reading this its looks like it not possible to replace the USB key without using UPC, i dont wanna combine my unraid keys with my unraid forum account...
  8. i wonder too, i don't like this, i prefer the old way, unraid works fully offline is what i like. no telemetry/tracking API crap... this UPC is a big RED FLAG for me, i dont like it and would never going to use it. i was planning on a second server, but after reading this it wont be unraid, but i am going Truenas scale... i going to monitor this, and if its going this way i going to move my main server also away from unraid. NO tracking/telemetry/API crap on my server! luckily i have a pretty good firewall with DPI and IDS/IPS, going to monitor this stuff...
  9. so, if i understand correctly, i can't use this container to enable access to my services on IPv6? :(
  10. is here someone who got SWAG fully working on IPv6? i trying to get it working but after view weeks of trail and error i'm out of idea's... Docker is fully working on IPv6, can confirm this. i have a tor relay running on unraid/docker and it external accessible through IPv6... SWAG does have an working IPv6 address. but Cloudflare won't get connection to SWAG on IPv6, resulting many times with error 522 i did some research on nginx with ipv6, its needs '--with-ipv6'? when checking on SWAG with the command: nginx -V it gives me the following configure arguments: no --with-ipv6 in there... anyone have in idea what i can do???
  11. i had problems with unraid when IPv6 was enabled, when its enabled the vm's and docker container wont work with ipv6, so i disabled it and using the second NIC with IPv6 enabled only for the docker containers what need ipv6, and this solution works for me. the vm's got an ipv6 address and docker will work on ipv6. but sometimes unraid itself will try to use that nic to download stuff by using the ipv6 address and this will fail of course because unraid isn't setup for ipv6... i changed the firewall rule by only blocking 8.8.8.8 on port 53 (i want to prevent any device on my network to use googledns)
  12. yeah, i think i found the problem, the driver installer is trying to use IPv6, and unraid itself isn't setup for that. i'm going to temporary disable the second NIC by unplug the fiber (which is setup for IPv6) and then try again. the files are there where they belong, i uploaded it to unraid and 8.8.8.8 is banned on my network (i did found some reference to 8.8.8.8 in this plugin) jup, found the problem, disabled the second NIC and tried again, its finished and its report me to reboot the server
  13. yeah, i have Pi-hole, but unRAID is excluded from it. manual download did work. will trying a second time download.
  14. unRAID was trying to download the new driver but it fails, no idea to troubleshot this, can't find anything in the logbook: