Login at Kodi Home

ToddeSwe · (This post was last modified: 2018-04-07, 14:49 by ToddeSwe.)

Hi

I had a meltdown yesterday and had to reinstall everything from scratch and now i can't find my NAS in the SMB list.
I have checked that SMB is activated in my NAS settings and it is. There's one device called VOLUME in my SMB list but i get an error message when trying to add it saying "Invalid argument".
When trying from the NFS list i get the device 192.168.1.22/home and the option between 2 accounts on my NAS.

I can find my NAS from the computer and every elsewhere in the network but not from the Librelec-Kodi installation.

Please help me find my NAS. Smile

error log:

https://pastebin.com/eCHVx4vA

**Klojum** · 2018-04-07, 14:34

13:53:30.509 T:140070546413248 NOTICE: Disabled debug logging due to GUI setting. Level 0.
For a debug log, please enable debugging and restart Kodi for a clean log file.

PS: I also cleaned up your signature a bit in order to adhere to the 4-line limit as per Kodi forum rules.

ToddeSwe · 2018-04-07, 14:43

(2018-04-07, 14:34)Klojum Wrote: 13:53:30.509 T:140070546413248 NOTICE: Disabled debug logging due to GUI setting. Level 0.
For a debug log, please enable debugging and restart Kodi for a clean log file.

PS: I also cleaned up your signature a bit in order to adhere to the 4-line limit as per Kodi forum rules.

I've just restored the whole Librelec and want to see what that can do for me. I'll be back in a while.
Thanks for the SIG editing, did not know that.

ToddeSwe · 2018-04-07, 14:49

(2018-04-07, 14:34)Klojum Wrote: 13:53:30.509 T:140070546413248 NOTICE: Disabled debug logging due to GUI setting. Level 0.
For a debug log, please enable debugging and restart Kodi for a clean log file.

PS: I also cleaned up your signature a bit in order to adhere to the 4-line limit as per Kodi forum rules.

Hi!

Here it is:

https://pastebin.com/eCHVx4vA

ToddeSwe · 2018-04-07, 16:51

I've manage to solve the problem by inserting the address and username & password for my NAS into the SMB-settings in kodi. Smile

**Klojum** · 2018-04-07, 16:52

12:46:20.634 T:140526507112192 ERROR: Failed to open(//[email protected]/) opendir call failed with "NFS: READDIRPLUS of /[email protected] failed with NFS3ERR_ACCES(-13)"

You probably have some user/file permission problem with your NFS share.
Have a look here: https://forum.synology.com/enu/viewtopic.php?t=88697

ToddeSwe · 2018-04-07, 16:55

(2018-04-07, 16:52)Klojum Wrote: 12:46:20.634 T:140526507112192 ERROR: Failed to open(//[email protected]/) opendir call failed with "NFS: READDIRPLUS of /[email protected] failed with NFS3ERR_ACCES(-13)"

You probably have some user/file permission problem with your NFS share.
Have a look here: https://forum.synology.com/enu/viewtopic.php?t=88697

I've looked into that but all my shares was permitted to everyone. But it's strange that my NAS doesn't shows up in the SMB-list.

**Klojum** · 2018-04-07, 17:31

SMB != NFS ...

ToddeSwe · 2018-04-07, 21:51

(2018-04-07, 17:31)Klojum Wrote: SMB != NFS ...

I took a peak at the NFS section as well and when i had shared one folder on my NAS i could see it in Kodi. SO maybe i've not made a good job when setting up my NAS.
Thanks you for you time and interest in my problem.

**DarrenHill** · 2018-04-07, 22:35

If the smb share is smb2 or smb3 then it won't show up, as only smb1 has such browsing/advertising capabilities.

But these days smb1 is discouraged as it has security risks that lead to the Wannacry problem a few months ago.

ToddeSwe · 2018-04-07, 22:59

(2018-04-07, 22:35)DarrenHill Wrote: If the smb share is smb2 or smb3 then it won't show up, as only smb1 has such browsing/advertising capabilities.

But these days smb1 is discouraged as it has security risks that lead to the Wannacry problem a few months ago.

Yes i noticed in my ReadyNAS setup that all was encrypted with SMB3 so ... but i have solved it and i think it was as i did before my crash so i'm happy.
I've not touched this settings for a couple of years now so it was refreshing to do so again. Smile