Unable to browse network when adding folders to a library

[d00zah 129]

Win 7 (x64), Server v3.2.36.0

 

Unsure when this happened, but I was doing some testing which required adding a new folder to an existing library. For years, I've been able to add a network folder:

 

 

by clicking on Network, which would traditionally expand to available network host content. Now, it just adds 'Network' as the path without expanding/displaying network content clearly visible when browsing with Windows Explorer:

 

 

Copying/pasting path from Explorer address bar to Emby management UI works, so it's still functional,  but I used to be able to browse directly to my target folder within the UI.

 

This happens in both FF 56.0.2 & IE (whatever), so it doesn't seem to be a browser issue.

[Luke 37251]

Thanks for the report. We'll take a look.

[mbguy 38]

same thing here on 3.2.50.0, since 3.2.46.0.

[Luke 37251]

You should be able to type in the path though, thanks.

[mbguy 38]

Yes, typing in the path still works.

[Luke 37251]

The network browsing will be restored for the next release, thanks.

[d00zah 129]

Confirmed fixed in server v3.2.60.0. Thank you!

[Luke 37251]

Thanks for the feedback.

[xbmcgotham 32]

Hi,

 

I have the same problem with the browsing, however also having some issues adding the file paths to the emby server. I must be typing something wrong.

 

Info:

 

Have all the media in separate folders on a NAS drive.

 

This would be the path for the movies:

 

xxx.xxx.xxx.xxx/media/VIDEOS/MOVIES

 

For TV-shows:

 

xxx.xxx.xxx.xxx/media/VIDEOS/TVSHOWS

 

But when I run setup and put the movies in the folder input line as:

 

 

smb://xxx.xxx.xxx.xxx/media/VIDEOS/MOVIES/ or

 

smb://xxx.xxx.xxx.xxx/media/VIDEOS/MOVIES or

 

xxx.xxx.xxx.xxx/media/VIDEOS/MOVIES/ etc

 

I get an error saying "The path could not be found"

 

 

But when I enter:

 

 

smb://xxx.xxx.xxx.xxx

 

is saves the main NAS address.

 

 

The paths are correct as I am running multiple Kodis from it. So must be something I enter incorrectly? How do I add the different folders to the emby server?

 

Thanks for the help.

 

 

 

 

[Luke 37251]

it sounds like your emby server is unable to reach those paths, or does not have permission. make sure they are accessible with anonymous access. thanks.

[xbmcgotham 32]

it sounds like your emby server is unable to reach those paths, or does not have permission. make sure they are accessible with anonymous access. thanks.

 

yes, its psw protected. however, for safety, I have to keep psw on nas. Anyway to add folders differently?

[xbmcgotham 32]

in kodi, it allows me first to connect the NAS with login details and after this I can select the folders. Anyway this is available for emby?

[Luke 37251]

You can mount it as a local share on the device, and then add the local share to Emby.

[xbmcgotham 32]

Thanks, I will check it out over the next few days. enjoy the coming days

[xbmcgotham 32]

Hi, still no luck.

 

made a link to the NAS in the ubuntu folder window and opened it to check if folders where accessible. They are.

 

Than opened the emby config browser and tried looking for the local share, but I cant find it. What am I doing wrong?

 

Thanks

[Luke 37251]

It won't show up automatically. Try typing in the path manually.

[xbmcgotham 32]

if i type in

 

smb://<nas>.local and click the search icon, it shows the list of folder shares on the NAS. however when clicking on the media folder, the page layout hangs up and I am not able to progress. This is probably related to the password protection on this folder share.

 

But as I understand, I had to make a local share of this NAS drive, and than select the media folder in the list. However, I cant find this in the list and I am not sure what the "local path" to this share is for typing. Not that familiar with linux.

[Luke 37251]

It probably is permission related, yes. If you can attach the emby server log from this timeframe then i can help verify that. t hanks.

[xbmcgotham 32]

Hi, please find below the log snipped. It looks like it has a problem with the login access:

 

2018-01-02 12:14:04.620 Info HttpServer: HTTP GET http://localhost:8096/web/css/images/favicon.ico. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:04.620 Info HttpServer: HTTP Response 304 to 127.0.0.1. Time: 1ms. http://localhost:8096/web/css/images/favicon.ico 2018-01-02 12:14:04.806 Info HttpServer: HTTP GET http://localhost:8096/emby/Localization/cultures. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:04.817 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 12ms. http://localhost:8096/emby/Localization/cultures 2018-01-02 12:14:04.921 Info HttpServer: HTTP GET http://localhost:8096/emby/Localization/countries. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:04.935 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 14ms. http://localhost:8096/emby/Localization/countries 2018-01-02 12:14:10.279 Info HttpServer: HTTP GET http://localhost:8096/emby/Environment/DefaultDirectoryBrowser. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:10.284 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 6ms. http://localhost:8096/emby/Environment/DefaultDirectoryBrowser 2018-01-02 12:14:11.544 Info HttpServer: HTTP GET http://localhost:8096/web/css/images/favicon.ico. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:11.545 Info HttpServer: HTTP Response 304 to 127.0.0.1. Time: 1ms. http://localhost:8096/web/css/images/favicon.ico 2018-01-02 12:14:12.032 Info HttpServer: HTTP GET http://localhost:8096/emby/Environment/Drives. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:12.038 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 6ms. http://localhost:8096/emby/Environment/Drives 2018-01-02 12:14:19.217 Info HttpServer: HTTP GET http://localhost:8096/emby/Environment/DirectoryContents?includeDirectories=true&path=smb%3A%2F%2Fmultimedia-nas.local. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:19.242 Info HttpServer: HTTP GET http://localhost:8096/emby/Environment/ParentPath?path=smb%3A%2F%2Fmultimedia-nas.local. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:19.284 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 42ms. http://localhost:8096/emby/Environment/ParentPath?path=smb%3A%2F%2Fmultimedia-nas.local 2018-01-02 12:14:19.431 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 214ms. http://localhost:8096/emby/Environment/DirectoryContents?includeDirectories=true&path=smb%3A%2F%2Fmultimedia-nas.local 2018-01-02 12:14:23.155 Info HttpServer: HTTP GET http://localhost:8096/emby/Environment/DirectoryContents?includeDirectories=true&path=smb%3A%2F%2Fmultimedia-nas.local%2Fmedia. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:23.165 Error HttpServer: Error processing request	*** Error Report ***	Version: 3.2.60.0	Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh	Operating system: Unix 4.8.0.36	64-Bit OS: True	64-Bit Process: True	User Interactive: False	Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Tue May  2 22:26:20 UTC 2017)	Processor count: 2	Program data path: /var/lib/emby-server	Application directory: /usr/lib/emby-server/bin	SharpCifs.Smb.SmbAuthException: Access is denied.	  at SharpCifs.Smb.SmbTransport.CheckStatus (SharpCifs.Smb.ServerMessageBlock req, SharpCifs.Smb.ServerMessageBlock resp) [0x000a5] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	  at SharpCifs.Smb.SmbTransport.Send (SharpCifs.Smb.ServerMessageBlock request, SharpCifs.Smb.ServerMessageBlock response) [0x0021f] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	  at SharpCifs.Smb.SmbSession.Send (SharpCifs.Smb.ServerMessageBlock request, SharpCifs.Smb.ServerMessageBlock response) [0x000b3] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	--- End of stack trace from previous location where exception was thrown ---	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at Emby.Server.Implementations.Services.ServiceHandler+<ProcessRequestAsync>c__async1.MoveNext () [0x0016b] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	--- End of stack trace from previous location where exception was thrown ---	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at Emby.Server.Implementations.HttpServer.HttpListenerHost+<RequestHandler>c__async0.MoveNext () [0x00756] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	SharpCifs.Smb.SmbAuthException	  at SharpCifs.Smb.SmbTransport.CheckStatus (SharpCifs.Smb.ServerMessageBlock req, SharpCifs.Smb.ServerMessageBlock resp) [0x000a5] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	  at SharpCifs.Smb.SmbTransport.Send (SharpCifs.Smb.ServerMessageBlock request, SharpCifs.Smb.ServerMessageBlock response) [0x0021f] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	  at SharpCifs.Smb.SmbSession.Send (SharpCifs.Smb.ServerMessageBlock request, SharpCifs.Smb.ServerMessageBlock response) [0x000b3] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	--- End of stack trace from previous location where exception was thrown ---	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at Emby.Server.Implementations.Services.ServiceHandler+<ProcessRequestAsync>c__async1.MoveNext () [0x0016b] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	--- End of stack trace from previous location where exception was thrown ---	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 	  at Emby.Server.Implementations.HttpServer.HttpListenerHost+<RequestHandler>c__async0.MoveNext () [0x00756] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 	2018-01-02 12:14:23.166 Info HttpServer: HTTP Response 500 to 127.0.0.1. Time: 10ms. http://localhost:8096/emby/Environment/DirectoryContents?includeDirectories=true&path=smb%3A%2F%2Fmultimedia-nas.local%2Fmedia 2018-01-02 12:14:23.191 Info HttpServer: HTTP GET http://localhost:8096/emby/Environment/ParentPath?path=smb%3A%2F%2Fmultimedia-nas.local%2Fmedia. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:23.196 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 6ms. http://localhost:8096/emby/Environment/ParentPath?path=smb%3A%2F%2Fmultimedia-nas.local%2Fmedia 2018-01-02 12:14:28.305 Info HttpServer: HTTP GET http://localhost:8096/web/css/images/favicon.ico. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:28.306 Info HttpServer: HTTP Response 304 to 127.0.0.1. Time: 1ms. http://localhost:8096/web/css/images/favicon.ico 2018-01-02 12:14:29.253 Info HttpServer: HTTP GET http://localhost:8096/web/css/images/favicon.ico. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:29.254 Info HttpServer: HTTP Response 304 to 127.0.0.1. Time: 1ms. http://localhost:8096/web/css/images/favicon.ico 2018-01-02 12:14:33.003 Info HttpServer: HTTP GET http://localhost:8096/web/css/images/favicon.ico. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:33.005 Info HttpServer: HTTP Response 304 to 127.0.0.1. Time: 2ms. http://localhost:8096/web/css/images/favicon.ico 2018-01-02 12:14:33.256 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:33.262 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 6ms. http://localhost:8096/emby/System/Logs 2018-01-02 12:14:33.573 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:33.579 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 6ms. http://localhost:8096/emby/System/Configuration 2018-01-02 12:14:33.592 Info HttpServer: HTTP GET http://localhost:8096/emby/Plugins/SecurityInfo. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.02018-01-02 12:14:33.598 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 6ms. http://localhost:8096/emby/Plugins/SecurityInfo 2018-01-02 12:14:35.193 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs/Log?name=server-63650491377.txt. UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0

[Luke 37251]

Yes, you'll need to make sure the smb share is accessible anonymously. We haven't yet added the ability to enter a username and password for it. Thanks.

[xbmcgotham 32]

Yes, you'll need to make sure the smb share is accessible anonymously. We haven't yet added the ability to enter a username and password for it. Thanks.

 

Hope you add soon. When is it on planning for release?

 

In the mean time, you suggested to save the share first in ubuntu and than open the share in emby and select the folder. However what is the url format to select this local saved share in emby library selection path manual as i cant find it while browsing for it.

[Luke 37251]

I can't offer a timeline, sorry. But if you mount the path to Ubuntu using fstab, then it would look something like /usr/share/etc

 

Please let us know if this helps. Thanks !

[xbmcgotham 32]

Hi, it worked. :-)

 

Luckely I had some experience with configuration of cumputers, however normal users would not be able to get it done I guess. Dont know why linux (Ubuntu) is still not more configuration friendly after so many years.

 

Just to help out, I have written down the steps I took below and the errors I received. Feel free to move this to another threat.

 

***************************************

 

1. First edit fstab.

 

used the following information to open fstab for editing. It also shows some extra info on config options (https://community.linuxmint.com/tutorial/view/1513)

 

 

 

 

2. Add the correct mounting line to the fstab.

 

I used the following information as basis for config of my NAS drive. (https://unix.stackexchange.com/questions/178187/how-to-edit-etc-fstab-properly-for-network-drive)

 

 //192.168.0.67/test  /home/pi/test  cifs  username=myname,password=123,iocharset=utf8,sec=ntlm  0  0

 

 

3. I saved the fstab file and rebooted PC.

 

 

4. When opening the "Files" browser the NAS drive was not mounted and I got an error saying:

 

 

Only root can mount ...

 

 

5. I found out that I needed to add an extra option to the fstab entry I added in step 2. (https://askubuntu.com/questions/336387/only-root-can-mount-dev-sdb1-on-media-sdb1-contribute-to-external-usb-drive/336764)

 

So I added "user" to the line:

 

//192.168.0.67/test  /home/pi/test  cifs  user,username=myname,password=123,iocharset=utf8,sec=ntlm  0  0

 

 

6. I rebooted PC and got the following error:

 

mount: wrong fs type, bad option, bad superblock ...

 

 

7. I found the following information that solved the problem. (https://askubuntu.com/questions/525243/why-do-i-get-wrong-fs-type-bad-option-bad-superblock-error)

 

So in my case, as I used "cifs" I installed cifs-utils by adding the line "sudo apt install cifs-utils" in terminal. and after install I rebooted and the NAS drive was correctly mouted and accessible in Emby library browser. :-)

[Luke 37251]

Great info, thanks !

[djhifi 55]

I'm just digging this one up to ask something. I've been testing browsing the "manage library" section of the server to outside my NAS paths. I have the same problem as the OP clicking "Network" does nothing. But if I manually type \\192.168.2.69 (one of my windows pc IP adresses) I can see the shares. Was this issue never fixed?

And also, why isn't the server accepting the name of the PC as a smb path but rather only the IP?

 

I'm planning on adding a second Synology to my library so I was just testing this.