Jump to content

Path Substitution with NFS shares...syntax?


Recommended Posts


Currently running Emby Version 3.0.5675.1 on my Windows 8.1 machine, and the Emby for Kodi addon version 1.1.17 on my Amazon Fire TV within my home network.  I also like to access my library remotely to stream via my mobile devices.  When trying to play from my Video Library while within my network, I receive the message that I am unable to direct play, and whether I want to stream via HTTP or HTTPS.


I believe my issue has to do with my path substitution being set up incorrectly.


I have my share permissions set up correctly for NFS, but think my syntax is wrong in my Emby Server for path substitution.  For example, my current path substitution is set up like:


From                                                     To

"G:\TV"                                                  "nfs://"

"H:\Kid Movies"                                     "nfs:// Movies/"

It's my understanding that NFS does not require a username/password to access the Windows shares, versus if I were using SMB I would need to configure the setting within the Emby for Kodi add-on with the credentials.


The above are a couple of examples, for which I thought were working correctly up until a few days ago when Emby for Kodi or my Emby Server were updated (I was out of town and something auto-updated).  Now I receive the HTTP message and 'Warning: Unable to direct play'.  I'd like to direct play my library from within my network, while still accessing media outside of my LAN.  My examples above include the quotation marks because I am not aware of how Emby will process paths that contain spaces, so that's how I originally entered them.


With borrowing from my above examples, what would be the official syntax to use for my NFS shares? For those paths that contain spaces, do I use quotes? Am I able to use the IP Address, or is Emby looking for the server name?


For those paths that DO NOT contain 'spaces', would I use:


Option A) nfs://

Option B ) nfs://

Option C) nfs://ServerName/TV

Option D) nfs://ServerName/TV/

Option E) None of the Above (please provide a better suggestion)


For those paths that DO contain 'spaces', would I use:


Option A) nfs:// Movies

Option B ) nfs:// Movies/

Option C) "nfs:// Movies"

Option D) "nfs:// Movies/"

Option E) nfs://ServerName/Kid Movies

Option F) nfs://ServerName/Kid Movies/

Option G) "nfs://ServerName/Kid Movies"

Option H) "nfs://ServerName/Kid Movies/"

Option FML) None of the Above (please provide a better suggestion)


Lots of play above with IP Address vs Server Name, quotes vs no quotes, slashes vs no slashes....


As you can see, just a little lost looking for some help.



Edited by DruTheFu
Link to comment
Share on other sites

you don't need to use quotes for spaces. it is a direct text replacement, so you can use machine name, ip address, whatever will allow the machine running the client app to directly access the content managed by the server.

Link to comment
Share on other sites


Thanks for the reply.


With being NFS based, do I need to include specific syntax to include that?


Is there a chance that you can provide a few examples based on my above information?


Thanks again

Link to comment
Share on other sites

i will have to leave that to someone who knows nfs and kodi better, but try opening your file explorer on the client machine. then try entering paths such as nfs://ServerName/Kid Movies/. If it works in the file explorer, then you know it will work in Kodi. So then once you know what the destination path is, you just have to come up with the search and replace values that the server can use to create it.

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

I'm having a similar problem.  I can access the NFS shares directly through Kodi (and through the Kodi file manager), but no matter what Path Substitutions I try, I can't play anything from the NFS shares using Emby library from any client machine. I just does nothing on Kodi (as if I didn't even click on it). If I remove the Path Substitution, the files play fine in Emby Library.  However, I believe they are being transcoded (what I wanted to avoid using Path Substitution).  Anyone using Path Substitution for NFS shares successfully in Emby for Kodi?

Link to comment
Share on other sites



Thank you for the reply! I read through that post and had a similar set-up to "puithove" for the "Path Substitution".  However, I did note one difference in his format.


I have the below format:



However, "puithove" has a colon after the IP in the screenshot he posted:



Is that what I'm missing or is this a typo? I can try when I get home today and verify.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...