vyreks

Members
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

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

vyreks's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. As other people mentioned, the issues with permissions for MQTT stem from this line in run.sh: chmod -R 666 /config After i commented it out and applied 777 over MQTT folder in appdata, everything works.
  2. Here's screen record showing the issue https://streamable.com/ya6du0 I posted here because today i was trying to set up smb_extra.conf to allow for custom share in addition to normal one given by the UD plugin, after restarting the array i noticed the custom share appeared but the main UD share disappeared. Then i noticed that the share button is not sticking. I did some troubleshooting, removed the custom share, rebooted few times, unfortunately main share didn't come back. When i was mounting the drive with UD i could see in the log that the share was being created but it wasn't accessible via SMB. Then i gave up and posted here. I checked few hours later and saw that the main UD share was accessible but the button still is not sticking so i recorded this video. tower-diagnostics-20210116-0343.zip
  3. For the first question http://checkmyip.torrentprivacy.com/ . For the second one: they should just work. I can't say 100% because I moved on from this docker but I do remember the flags appearing normally when I was using it. Also I'm disabling notifications this thread because I forgot I still had them. Good luck.
  4. Hi, Recently you updated the docker to version 4.2.1 which broke most (if not all) private trackers as they don't have 4.2.X whitelisted yet. Could you create a tag on dockerhub for latest version on 4.1.X please?
  5. Actually VM only has 500mb of ram allocated. I will disable dynamix file integrity and see how it performs. Sadly i'm not able to purchase more ram ATM. I will try to buy it soon™
  6. Hello, I tried searching around but after reading a while i think that my issues are kinda weird. List of my problems: - My windows 10 VM crashes occasionally and i have no idea why. (VM data is on 750gb cache drive) - Disk 1 is continuously spinning even when i press spin down it will spin itself after short while. - My unraid is generally stable but i had few instances of it crashing in a weird way, something like array portion of webgui crashed and is inaccessible and SMB is down but the rest of webgui i can browse just fine. I think it was after 12days of uptime or something. After restart it worked fine. I know this is really broad and no one will be able to help me with this without providing more info but i don't know what info you need. I attached anonymised diagnostics, maybe it will help. My tower info: 4x4TB drives 2 parity 2 data disks. 750gb cache UPS protected. Short system info : Model: Custom M/B: Gigabyte Technology Co., Ltd. - F2A88XM-HD3 CPU: AMD A8-5500 APU with Radeon™ HD Graphics @ 3200 HVM: Enabled IOMMU: Enabled Cache: 192 kB, 4096 kB Memory: 4 GB (max. installable capacity 8 GB) Network: bond0: fault-tolerance (active-backup), mtu 9000 eth0: 1000 Mb/s, full duplex, mtu 9000 Kernel: Linux 4.14.26-unRAID x86_64 OpenSSL: 1.0.2n Uptime: 5 days, 11:33:02 tower-diagnostics-20180321-0827.zip EDIT: It happened again, here is recording how it looks like after it "crashes?" https://a.pomf.space/hmtzzrxcevvh.webm I couldnt create diagnostics because the button wouldnt do anything. EDIT2: even the reboot button is not doing anything. I had to restart by pressing restart on the case.
  7. I did try it. Router is smarter than static ip though. It catches ipv6 first and shows that instead of ipv4, even though unraid is perfectly reachable via the static ip I set.
  8. It is a badly designed router but sadly i cannot change it because it's ISP provided one. IPv6 still comes back after reboot so I will probably have to set up some kind of janky ass forwarding from other device to unraid just to make it work. Thanks for tips.
  9. Sadly its not okay in my case. My router only shows unraid box using ipv6 and not ipv4 which blocks me from port forwarding anything from unraid. 1 2
  10. How to completely disable IPv6 support on unRaid? I tried this guide but after reboot the sysctl.conf is reset to default. My network settings tab Ifconfig result : root@Tower:/# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 9000 inet6 fe80::76d4:35ff:fe57:10af prefixlen 64 scopeid 0x20<link> ether 74:d4:35:57:10:af txqueuelen 1000 (Ethernet) RX packets 796 bytes 192124 (187.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 981 bytes 947091 (924.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 192.168.2.12 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 fe80::8c4d:40ff:fe0c:1dff prefixlen 64 scopeid 0x20<link> ether 74:d4:35:57:10:af txqueuelen 1000 (Ethernet) RX packets 792 bytes 177654 (173.4 KiB) RX errors 0 dropped 6 overruns 0 frame 0 TX packets 953 bytes 941117 (919.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000 ether 74:d4:35:57:10:af txqueuelen 1000 (Ethernet) RX packets 11719 bytes 9582220 (9.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 9500 bytes 6130516 (5.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 4 bytes 312 (312.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 312 (312.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
  11. Okay this is weird. After ~12h of doing nothing, I tried again and it generated just fine. I hate technology. Thanks for tips anyway.
  12. I get the same error as Nick and easy-rsa 3.0.4 only generates ta.key for me. Nothing else.