Spiritreader

Members
 View Profile  See their activity

  • Posts

    29

  • Joined

  • Last visited

 Content Type 

Everything posted by Spiritreader

  1. Spiritreader
    I think I am too dumb to figure out how to change the order of containers? If I drag a container in the "start order" section to the right, and then hit save and reload the page, it's at the old position again. Is there any additional step or save button that I am missing? container order in the config.json is empty "containerOrder": [] I thought that I might be able to set it manually but I don't know if it's a list of strings or some internal ids The configuration file is also missing some of my containers, and I cannot change their individual configuration or save that. The config ends at tika: "Tika": { "skip": "no", "group": "", "backupExtVolumes": "no", "updateContainer": "", "exclude": "", "skipBackup": "no", "verifyBackup": "", "ignoreBackupErrors": "" } }, "containerOrder": [] But there are more containers Here's a gif of trying to change order
  2. Spiritreader
    On 6.12 I have to configure my network adapters in Settings/NetworkSettings. I have added the wg2 and the tun5 interface of my wireguard and openvpn instance to the extra interfaces. I can reach the WebUI via both of them, including SSH. In addition, I also have added my zerotier interface. The ZT instance is running inside of docker, whereas OpenVPN and wireguard run on bare metal. However, I cannot access any SMB shares. If I inspect the smb.conf and smb_names.conf file I can see that it binds to the local interface, and my wireguard and openvpn interface. However, the shares are still not available. However, I have a ZeroTier docker container. Through this interface I can magically access the WebUI, SMB and SSH. It doesn't make sense at all to me. For now I'll have to downgrade because I can't really afford to have the server inaccessible, but I wanted to report this nonetheless. Other people reported they can't access the web UI at all, for me it's just SMB on interfaces that do NOT run in docker. I had the window with the smb configuration still open: This is what unraid configured (zerotier was not enabled at this time because the docker engine had crashed). the 194 interface is wireguard, the 10.11.12 is openvpn. root@Tower:/etc/samba# cat smb.conf [global] # configurable identification include = /etc/samba/smb-names.conf # log stuff only to syslog logging = syslog@0 # recycle bin parameters syslog = 0 logging = 0 max log size = 10000 # we don't do printers show add printer wizard = No disable spoolss = Yes load printers = No printing = bsd printcap name = /dev/null # disable aio by default aio read size = 0 aio write size = 0 # misc. invalid users = root unix extensions = No wide links = Yes use sendfile = Yes # ease upgrades from Samba 3.6 acl allow execute always = Yes # permit NTLMv1 authentication ntlm auth = Yes # default global fruit settings: #fruit:aapl = Yes #fruit:nfs_aces = Yes fruit:nfs_aces = No #fruit:copyfile = No #fruit:model = MacSamba # hook for user-defined samba config include = /boot/config/smb-extra.conf [global] # hook for unassigned devices shares include = /etc/samba/smb-unassigned.conf # auto-configured shares include = /etc/samba/smb-shares.conf root@Tower:/etc/samba# cat smb-names.conf # Generated names netbios name = Tower server string = Media server hide dot files = no server multi channel support = yes max open files = 40960 multicast dns register = No disable netbios = No server min protocol = NT1 local master = yes os level = 100 security = USER workgroup = WORKGROUP map to guest = Bad User passdb backend = smbpasswd null passwords = Yes idmap config * : backend = tdb idmap config * : range = 3000-7999 create mask = 0777 directory mask = 0777 bind interfaces only = yes interfaces = 192.168.1.126 10.10.194.5 127.0.0.1 fd94::5 10.11.12.5 root@Tower:/etc/samba# cat smb-names.conf
  3. Spiritreader
    Okay that is very good to know, because I can't get SMB to work at all with any interface that is not the default bond0.
  4. Spiritreader
    i have no clue what I'm doing wrong. My access randomly breaks, and even if I get WebUI access with wireguard/tailscale, I can't get SMB shares to work. Removing and re-adding the interface sometimes restores WebUI access, sometimes it breaks everything and I have to reboot the server.
  5. Spiritreader
    I'm really liking the update in general! Especially the revamped storage configuration is now super intuitive. However the new network interface configuration where unraid doesn't listen on my wg2 interface (which I configure manually on array start for split tunneling) doesn't seem like a good idea in this state. It would potentially be favorable to allow configuration to listen on all interfaces by default again. I've only had headaches, troubles and why the hell isn't this working moments and it resulted in many pulled out hairs. Update: I managed to get the reload script working after some fiddlng with how my wg interface is started up. However, a fixed timeout in the reload-script that is configured will at some point produce unreliable results and isn't something I feel confident in. I can see the security improvements that this brings, however for unproblematic operation I would wish that web services are automatically able to start listening to interfaces as they become available that have been configured. I am usually not able to access the server locally, so I'm not quite sure how this is supposed to work out for me in the long run. Update 2: Nope, still broken. SMB does not work. Update 3: Now everything is completely broken again and I can't get it to work at all anymore.
  6. Spiritreader
    How can I determine which container icon is causing the slowdown due to failed download? All of the icons seem to load fine and yet I have the exact same issue. I do have a few containers that have been created outside of Unraid's WebUI and thus have a question mark as symbol. But there's no icon URL there in the first place. Update: I've added icons via docker label to all of them and still get long loading times
  7. Spiritreader
    Ah I realized that template authoring mode got disabled for some reason. Probably had to do with me restoring a bunch of settiings from backup due to fixing another issue. Thanks for the replay nonetheless!
  8. Spiritreader
    When editing a docker container, Unraid does not remember that I picked the "Advanced View" anymore. Instead it always shows me the basic view. Is this intentional? It's a bit cumbersome, having to click this every time, as I regularily use/modify the fields that are hidden in basic view.
  9. Spiritreader
    Oh wow I didn't know the WebGUI source was inspectable. That's awesome! If I had known, I could've reported the bug way faster than I did! In any case, thanks for fixing it so quickly! Appreciate the team always being on the lookout in the forums! 😃
  10. Spiritreader
    Since 6.10 there are mutliple gpu drivers embedded, you may need to blacklist them https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Linux_Kernel I'm not sure if that's causing the problem, but it's something that came to mind when I read your post.
  11. Spiritreader
    I figured it out. There seems to be an issue with how the WebGUI matches usernames. I have a user called "rootshare" which exposes all shares via a custom smb config. When this user account exists, unraid's WebUI attempts to match the password for "rootshare" instead of "root". Using the password for the "rootshare" user then works for the "root" user. Seems like an oversight? (username.startsWith() / username.Contains() or something?)
  12. Spiritreader
    Hey everyone, all the way back when RC-1 came out, I tried upgrading, but it was stopped in its tracks because I was unable to log in with my correct credentials. I rolled back to 6.9.2 and everything worked fine again. Now that 6.10 is released as stable, I tried again, and I still cannot log in with the WebGUI. I tried downgrading to 6.9.2, setting the password to only letters, upgrading again, it still doesn't work. I tried removing/renaming the shadow file, which prompts me to set a new password. I set the password, press "logout", and I can not log back in again. The shadow file is written to, there's a new hash in there, so this seems to have worked. But it just won't let me access the WebUI? SSH works fine. The flash drive is fine, permissions are fine, there don't seem to be any corrupted files. I have no idea how to proceed here. This is the only thing that shows up in the log (I stay logged in after resetting the password until I log out again) May 26 04:47:09 UMS webGUI: Unsuccessful login user root from 192.168.178.84
  13. Spiritreader
    I've had this issue as well when upgrading. I was unable to resolve it and have not retried upgrading to 6.10.0-rc1 since. In my case my USB drive appeared to be in good condition though. Did you ever change the root password on that server at some point prior to upgrading?
  14. Spiritreader
    The password is 10 characters long, has uppercase and lowercase letters, numbers and exclamation marks. I did not use the password recovery, but instead downgraded back to 6.9.2 by restoring the flash backup I made. I still had ssh access, so I could easily do that. This also means that there were a lot of writes on the flash drive, but the system doesn't show any issues now, so I believe I can rule out the flash drive for now.
  15. Spiritreader
    I have updated to 6.10-rc1, and my webui root credentials are no longer working. WebUI reports: "Invalid Username or Password", but the entered credentials are correct. What are the recommended steps to fix this? Update: I can still log in via ssh with the same credentials as before.
  16. Spiritreader
    Using version-1.4.0 results in the following error message: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.4.0". Is that an issue on my end or is the used php version outdated? What do I need to do? UPDATE: fixed in latest container version
  17. Spiritreader
    I am aware that this report is lacking, but not reporting at all is something I would've considered worse given that this did happen and isn't what I think should be intended behavior. I will update as soon as I can take the server offline safely again. Unfortunately this is not a test system so I can't just play around with it willingly. And yes, running beta on a production system isn't ideal but I had no choice given the whole DVB driver meltdown that happened.
  18. Spiritreader
    When I press "check for updates" in the docker tab and refresh the page while it's still updating, the webUI seems to partially hang. The plugins page and unassigned devices pane no longer respond and it just shows an infinite unraid loading icon. I am also no longer able to observe any progress when updating docker containers. It just states "please wait..." in the update log and while the container is updated in the background (if you leave the window open long enough and close the page the container is updated afterwards) it still shows "please wait..." The only way to fix it was to reboot the server, after that it started working again immediately. Steps to reproduce: Switch to docker tab Press "check for updates" Refresh the browser page while the individual docker entries still say "checking for updates"
  19. Spiritreader
    Hmm, that is indeed very weird. Good to know it's not the driver version, must be something else then. Before trying 6.9b35, I also wasn't able to get the card working on 6.8.3 with the custom-kernel-helper builder. That kernel however, also picked up the S2 C6 fine. Here's the output of lsmod, I put it in a pastebin so it doesn't spam the forum. https://pastebin.com/5RkQRr74 Yes you can contact me, in fact I would be very glad to! My timezone is Europe/Berlin, GMT+1. Thank you for trying to help me out!
  20. Spiritreader
    Of course! Thank you! First, sanity check: The tuner is showing up. [dd01:000b] 25:00.0 Multimedia controller: Digital Devices GmbH Device 000b Then, to answer your questions: - Package that shows up is "digitaldevices". - I have performed a reboot after selecting download. Driver version shows as 0.9.33-integrated, while the latest digitaldevices drivers seem to be 0.9.37. The syslog also reports loading an out of date driver (c 2017) Nov 15 11:39:37 UMS kernel: ddbridge: Digital Devices PCIE bridge driver 0.9.33-integrated, Copyright (C) 2010-17 Digital Devices GmbH Since the DigitalDevices S8 series requires extra configuration, I have added this to the syslinux config kernel /bzimage append initrd=/bzroot ddbridge.fmode=3 ddbridge.msi=1 However, this used to be part of the documentation of the Unraid DVB post that was removed. This config step seems to be mandatory, although I am unsure whether not configuring that prevents the drivers from picking up the card at all. In case the syslinux config change isn't working anymore, what would be necessary is to create a config file in /etc/modprobe.d/ddbridge.conf which must persist between reboots. http://support.digital-devices.eu/index.php?article=151 I'm also unsure how to achieve this with the new dvb infrastructure Here's a screenshot of the page (Cine S2 V6 there, Max S8X not there)
  21. Spiritreader
    For the Unraid DVB plugin, Is there an option to select a newer driver version than 0.9.33-integrated? We have a DigitalDevices Max S8X basic and it is not picked up. The DigitalDevices Cine S6 V6 is picked up, not the S8X though. I'm assuming I need newer drivers. How do I accomplish this? root@UMS:~# dmesg | grep -i ddbridge [ 0.000000] Command line: BOOT_IMAGE=/bzimage initrd=/bzroot ddbridge.fmode=1 ddbridge.msi=1 [ 0.000000] Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot ddbridge.fmode=1 ddbridge.msi=1 [ 65.506126] ddbridge: Digital Devices PCIE bridge driver 0.9.33-integrated, Copyright (C) 2010-17 Digital Devices GmbH [ 65.506213] ddbridge 0000:21:00.0: enabling device (0000 -> 0002) [ 65.506322] ddbridge 0000:21:00.0: detected Digital Devices Cine S2 V6 DVB adapter [ 65.506344] ddbridge 0000:21:00.0: HW 0001000b REGMAP 00010004 [ 65.506422] ddbridge 0000:21:00.0: using 2 MSI interrupt(s) [ 65.507558] ddbridge 0000:21:00.0: Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2 [ 65.508574] ddbridge 0000:21:00.0: Port 1: Link 0, Link Port 1 (TAB 2): NO MODULE [ 65.509582] ddbridge 0000:21:00.0: Port 2: Link 0, Link Port 2 (TAB 3): NO MODULE [ 65.509955] dvbdev: DVB: registering new adapter (DDBridge) [ 65.509957] dvbdev: DVB: registering new adapter (DDBridge) [ 65.691770] ddbridge 0000:21:00.0: attach tuner input 0 adr 60 [ 65.691774] ddbridge 0000:21:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)... [ 65.734287] ddbridge 0000:21:00.0: attach tuner input 1 adr 63 [ 65.734291] ddbridge 0000:21:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...
  22. Spiritreader
    Works fine again on both servers. Thank you!
  23. Spiritreader
    Unfortunately nothing shows up. I omitted the unlink to check what else samba was logging, and there's nothing there except for when the daemon is restarted due to config changes root@Tower:~# cat /var/log/samba/log.smbd [2020/10/04 21:45:16.282004, 0] ../../source3/smbd/server.c:1775(main) smbd version 4.11.4 started. Copyright Andrew Tridgell and the Samba Team 1992-2019
  24. Spiritreader
    I've tried the following: - stop and restart the recycle bin - toggle logging off and on while the recycle bin is started - stop recycle bin, toggle logging off and on, start the recycle bin. No change, still not logging.
  25. Spiritreader
    I have removed the extra configuration. Now it's just unassigned devices and the recycle bin. #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end #vfs_recycle_start #Recycle bin configuration [global] syslog only = No syslog = 0 logging = 0 log level = 0 vfs:0 #vfs_recycle_end Still no logging when deleting files unfortunately.