NodeZero

Found that adding the following to the SMB extra config works. server min protocol = NT1

Further update, tried with Netbios enabled via the SMB menu, to get v1 support, but no joy there either :-( - updated logs based on that attempt below. Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.188862, 3] ../../lib/util/access.c:372(allow_access) Mar 23 20:53:17 NodeCentral smbd[1367271]: Allowed connection from 192.168.102.34 (192.168.102.34) Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189010, 3] ../../source3/param/loadparm.c:4031(lp_load_ex) Mar 23 20:53:17 NodeCentral smbd[1367271]: lp_load_ex: refreshing parameters Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189069, 3] ../../source3/param/loadparm.c:562(loadparm_s3_init_globals) Mar 23 20:53:17 NodeCentral smbd[1367271]: Initialising global parameters Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189140, 3] ../../source3/param/loadparm.c:2933(lp_do_section) Mar 23 20:53:17 NodeCentral smbd[1367271]: Processing section "[global]" Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189210, 1] ../../lib/param/loadparm.c:1912(lpcfg_do_global_parameter) Mar 23 20:53:17 NodeCentral smbd[1367271]: lpcfg_do_global_parameter: WARNING: The "null passwords" option is deprecated Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189323, 3] ../../source3/param/loadparm.c:2933(lp_do_section) Mar 23 20:53:17 NodeCentral smbd[1367271]: Processing section "[global]" Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189358, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:53:17 NodeCentral smbd[1367271]: Processing section "[appdata]" Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189403, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:53:17 NodeCentral smbd[1367271]: Processing section "[documents]" Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189459, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:53:17 NodeCentral smbd[1367271]: Processing section "[media]" Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189501, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:53:17 NodeCentral smbd[1367271]: Processing section "[system]" Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.189553, 3] ../../source3/param/loadparm.c:1735(lp_add_ipc) Mar 23 20:53:17 NodeCentral smbd[1367271]: adding IPC service Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.190191, 2] ../../source3/lib/interface.c:641(interpret_interface) Mar 23 20:53:17 NodeCentral smbd[1367271]: interpret_interface: Adding interface 192.168.102.148/24 Mar 23 20:53:17 NodeCentral smbd[1367271]: added interface 192.168.102.148 ip=192.168.102.148 bcast=192.168.102.255 netmask=255.255.255.0 Mar 23 20:53:17 NodeCentral smbd[1367271]: added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0 Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.190253, 3] ../../source3/smbd/smb2_oplock.c:1488(init_oplocks) Mar 23 20:53:17 NodeCentral smbd[1367271]: init_oplocks: initializing messages. Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.191786, 3] ../../source3/smbd/smb2_negprot.c:1152(smb2_multi_protocol_reply_negprot) Mar 23 20:53:17 NodeCentral smbd[1367271]: Requested protocol [NT LM 0.12] Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.191833, 3] ../../source3/smbd/smb2_negprot.c:1199(smb2_multi_protocol_reply_negprot) Mar 23 20:53:17 NodeCentral smbd[1367271]: smb2_multi_protocol_reply_negprot: No protocol supported ! Mar 23 20:53:17 NodeCentral smbd[1367271]: [2026/03/23 20:53:17.192029, 3] ../../source3/smbd/server_exit.c:230(exit_server_common) Mar 23 20:53:17 NodeCentral smbd[1367271]: Server exit (no protocol supported Mar 23 20:53:17 NodeCentral smbd[1367271]: )

OK, to keep people updated - I tried the following in the SMB Extras - but sadly that did not work.. client min protocol = NT1 Here is the log output from that change.. Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524051, 3] ../../lib/util/access.c:372(allow_access) Mar 23 20:32:33 NodeCentral smbd[1290041]: Allowed connection from 192.168.102.34 (192.168.102.34) Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524204, 3] ../../source3/param/loadparm.c:4031(lp_load_ex) Mar 23 20:32:33 NodeCentral smbd[1290041]: lp_load_ex: refreshing parameters Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524287, 3] ../../source3/param/loadparm.c:562(loadparm_s3_init_globals) Mar 23 20:32:33 NodeCentral smbd[1290041]: Initialising global parameters Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524370, 3] ../../source3/param/loadparm.c:2933(lp_do_section) Mar 23 20:32:33 NodeCentral smbd[1290041]: Processing section "[global]" Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524449, 1] ../../lib/param/loadparm.c:1912(lpcfg_do_global_parameter) Mar 23 20:32:33 NodeCentral smbd[1290041]: lpcfg_do_global_parameter: WARNING: The "null passwords" option is deprecated Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524588, 3] ../../source3/param/loadparm.c:2933(lp_do_section) Mar 23 20:32:33 NodeCentral smbd[1290041]: Processing section "[global]" Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524622, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:32:33 NodeCentral smbd[1290041]: Processing section "[appdata]" Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524667, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:32:33 NodeCentral smbd[1290041]: Processing section "[documents]" Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524718, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:32:33 NodeCentral smbd[1290041]: Processing section "[media]" Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524762, 2] ../../source3/param/loadparm.c:2950(lp_do_section) Mar 23 20:32:33 NodeCentral smbd[1290041]: Processing section "[system]" Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.524819, 3] ../../source3/param/loadparm.c:1735(lp_add_ipc) Mar 23 20:32:33 NodeCentral smbd[1290041]: adding IPC service Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.525447, 2] ../../source3/lib/interface.c:641(interpret_interface) Mar 23 20:32:33 NodeCentral smbd[1290041]: interpret_interface: Adding interface 192.168.102.148/24 Mar 23 20:32:33 NodeCentral smbd[1290041]: added interface 192.168.102.148 ip=192.168.102.148 bcast=192.168.102.255 netmask=255.255.255.0 Mar 23 20:32:33 NodeCentral smbd[1290041]: added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0 Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.525503, 3] ../../source3/smbd/smb2_oplock.c:1488(init_oplocks) Mar 23 20:32:33 NodeCentral smbd[1290041]: init_oplocks: initializing messages. Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.527059, 3] ../../source3/smbd/smb2_negprot.c:1152(smb2_multi_protocol_reply_negprot) Mar 23 20:32:33 NodeCentral smbd[1290041]: Requested protocol [NT LM 0.12] Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.527112, 3] ../../source3/smbd/smb2_negprot.c:1199(smb2_multi_protocol_reply_negprot) Mar 23 20:32:33 NodeCentral smbd[1290041]: smb2_multi_protocol_reply_negprot: No protocol supported ! Mar 23 20:32:33 NodeCentral smbd[1290041]: [2026/03/23 20:32:33.527313, 3] ../../source3/smbd/server_exit.c:230(exit_server_common) Mar 23 20:32:33 NodeCentral smbd[1290041]: Server exit (no protocol supported Mar 23 20:32:33 NodeCentral smbd[1290041]: )

HI I am trying to connect my Panasonic TV to a share on my Unraid NAS, using the TV’s in built network drive link facility, but I’m struggling as it keeps telling me the “connection to the server failed”. Share is ‘movies’, set to Public, a new ‘pani’ user is set up too. Reading some threads online, it made me think that this might be SMB version related so I updated the SMB Extras with the following (restarted the Array).. log level = 3 logging = syslogAnd ran some more tests and the output in the Sky’s logs was as follows.. Tthe requested protocol looks to be Requested protocol [NT LM 0.12] - does anyone have any ideas how to fix this ? Mar 23 19:58:08 NodeCentral smbd[1160817]: [2026/03/23 19:58:08.339091, 2] ../../source3/lib/interface.c:641(interpret_interface) Mar 23 19:58:08 NodeCentral smbd[1160817]: interpret_interface: Adding interface 192.168.102.148/24 Mar 23 19:58:08 NodeCentral smbd[1160817]: added interface 192.168.102.148 ip=192.168.102.148 bcast=192.168.102.255 netmask=255.255.255.0 Mar 23 19:58:08 NodeCentral smbd[1160817]: added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0 Mar 23 19:58:08 NodeCentral smbd[1160817]: [2026/03/23 19:58:08.339158, 3] ../../source3/smbd/smb2_oplock.c:1488(init_oplocks) Mar 23 19:58:08 NodeCentral smbd[1160817]: init_oplocks: initializing messages. Mar 23 19:58:08 NodeCentral smbd[1160817]: [2026/03/23 19:58:08.340699, 3] ../../source3/smbd/smb2_negprot.c:1152(smb2_multi_protocol_reply_negprot) Mar 23 19:58:08 NodeCentral smbd[1160817]: Requested protocol [NT LM 0.12] Mar 23 19:58:08 NodeCentral smbd[1160817]: [2026/03/23 19:58:08.340747, 3] ../../source3/smbd/smb2_negprot.c:1199(smb2_multi_protocol_reply_negprot) Mar 23 19:58:08 NodeCentral smbd[1160817]: smb2_multi_protocol_reply_negprot: No protocol supported ! Mar 23 19:58:08 NodeCentral smbd[1160817]: [2026/03/23 19:58:08.340978, 3] ../../source3/smbd/server_exit.c:230(exit_server_common) Mar 23 19:58:08 NodeCentral smbd[1160817]: Server exit (no protocol supported Mar 23 19:58:08 NodeCentral smbd[1160817]: )

I’m looking at doing this too, it seems like there will be little to no issues Out of interest, is there a recommended guide tutorial to follow for a board, cpu replacement / upgrade ? Any lessons people have learned in doing it ?

Many thanks for responding and letting me know..

I currently have two streams showing, but there’s no one in the house using any media, so why would they still be there ? Are they using resources when in that state ? Is it possible to see what files are being streamed - and is it also possible to stop them ?

Hi, probably a quick one to answer for someone who has been living Unraid longer than me, but as I couldnt find anything specific about this elsewhere, I thought it best to post my question here.. I have just finished formatting two drives and getting them mounted to the array, but i noticed as soon as they came up they had a chunk of space taken up straight away. (See attached) - is this expected and if so what’s the allocation for ? I can see they are the same amount and combined at close in size to the 4Gb drive I already had in there.

OK, quick update I managed to open .fuse_hidden000000fc00000001 and it does seem to be the file I had deleted.. Weird ?? Being new to Unraid is this to be expected /

Hi. Not sure this is an issue, perhaps more an observation - as I haven’t’ been able to reproduce it again - but sharing for awareness . I have a SMB set up from a coding app (Textastic) on my iPad, linked to my Unraid - where I upload scripts etc. to run within a container I have running (stored via a mnt/user/appdata/). I just needed to delete a file and while it went away, it seemed to be instantly replaced with another one named .fuse_hidden000000fc00000001 and is 11.2kb in size. (I don’t have the original left to compare sizes but I think it’s different.) Curious if anyone has seen this before, can I just delete this new file ? :-) ?

I’m having trouble seeing all the volumes defined in my compose, I see some, but not all. When looking that issue up I saw a post where someone had used the following mix of /mnt/user/ and /mnt/cache/ ?? Please could someone help me understand / explain which is right? FYI - I currently have all mine compose file mapping all volumes to /mnt/user/ and the Unraid disk is set to write to cache first and then the array, so I assume in both cases - I’m writing to the cache first? Any insight would be appreciated.. volumes: - /mnt/user/appdata/mosquitto/config:/mosquitto/config - /mnt/cache/appdata/mosquitto/data:/mosquitto/data

What I can’t seem to do is have the labels that I included in the compose to be picked up by Docker Compose Manager ? Is there a particular format / structure I am missing ? E.g example from another one I’m working on. - net.unraid.docker.icon=https://raw.githubusercontent.com/selfhosted/unRAID-CA-templates/master/templates/img/filebrowser-icon.png - net.unraid.docker.webui=http://[IP]:[PORT:8081]

Thanks @bmartino1 and @apandey , the cause looks to have been the conf.json and the port that was listed in there. It should have mapped to the host port 5000. Simple in the end, just needed fresh eyes - thanks again.,.

Having used QNAP for years, I’m still getting familiar with Unraid and docker compose manager, I’ve successfully created one (open-web ui) but I’m really struggling with my next one (scriptserver). Everything seems to be up and running, at least to some degree (it’s all Green), but I can’t access the containers webui and there is nothing obvious in the logs. The compose I started with was one I’ve had on my QNAP many times no issue. Here is the compose file, if anyone has time, please can you help me find what’s wrong ? ```` services: scriptserver: container_name: scriptserver network_mode: bridge deploy: resources: limits: pids: 2048 environment: - TZ=Europe/London - HOST_OS=Unraid - HOST_HOSTNAME=Tower - HOST_CONTAINERNAME=scriptserver labels: - net.unraid.docker.managed=dockerman - net.unraid.docker.webui=http://[IP]:[PORT:5012]/ - net.unraid.docker.icon= volumes: - /mnt/user/appdata/scriptserver/conf/conf.json:/app/conf/conf.json - /mnt/user/appdata/scriptserver/runners/:/app/runners/:rw - /mnt/user/appdata/scriptserver/scripts/:/app/scripts/:rw - /mnt/user/appdata/scriptserver/media/:/app/media/:rw - /var/run/docker.sock:/var/run/docker.sock:ro ports: - 5012:5000/tcp image: bugy/script-server:latest ```` The required conf.json is something like this . ```` { "port": 5012, "title": "Node Central Scripts", "address": "0.0.0.0", "access": { "admin_users": [ "*" ] } } ````

Hi, how did you install open-webui? Was that from a docker compose? If so are you able to share what you used on your unraid?