Okay great, thanks.
I'm uploading a new pre-release build now with this feature.
1 Like
Did this ever work? I'm having problems too.. My test URL seems to show the content correctly:
When I try to play some files I've moved over to the SMB NAS (I'm running UNRAID) it fails.
I thought maybe it would be an authentication problem, so I tried setting the service to run as my domain account, but it makes no difference, and since the test URL does return content, I'd say authentication isn't the issue. Is there anything else which needs to be done? My understanding is that if the file isn't found on the primary directory, it's looked for on the secondary. For what it's worth, the relative path (file structure) has been maintained in my move, so all the directory structure still exists on the secondary - I assume this is desired?
Thanks!
OK.. replying to my own post, in order to hopefully help someone else.. I figured it out, and the problem was indeed path.. I had the shows directly in the folder structure configured in the GUI, but when I went to look at where Channels puts it, all the show folders are under \tv.. As soon as I moved them all under TV, it works, at least on the web client. As soon as I can regain control of the TV remote, I'll make sure it works on the FireTV client app as well, but I'm sure it will.. This is awesome.. I have a script configured to move shows over 2 days old onto my NAS to keep the channels VM drive less full.. Should work great!
Thanks for an awesome product!
1 Like
Should this be working in the current release ??. When I test using local storage path, it works fine. When I test using UNC path, I get an open bracket like mentioned earlier in the thread:
http://localhost:8089/filesystem?path=G:\ChannelsDRV-Playon-TVImport\ChannelsDVR.Extra - Works
http://localhost:8089/filesystem?path=\wdmycloud\ChannelsDRV\ChannelsDRV-Playon-TVImport\ChannelsDVR.Extra -No works []
Server version is 2021.10.27.1449
Thank you!!!!
That's not a correct UNC.. You need 2 backslashes before the server name. \wdmycloud...
It is working still for me.
Thank you....Yep...I made a typo....but once corrected...It still doesn't work. So for the Devs....does this error indicate the server can't read the share ??. I can go to the share directly and play vids:
Failed to read directory \WDMyCloud\ChannelsDRV\ChannelsDRV-Playon-TVImport\ChannelsDVR.Extra: open \WDMyCloud\ChannelsDRV\ChannelsDRV-Playon-TVImport\ChannelsDVR.Extra: The specified server cannot perform the requested operation.
Sorry if this is a dumb question, but I dont want to assume everyone on the forum understands networking, but if you're using "https://localhost" you are running the browser from the CHANNELS server directly, right? "https://localhost:8089" does bring up the channels web interface, right?
If so, any permissions issues on the wdmycloud? Any authentication errors in the logs? Sorry, I'm not familiar with the WD device.. I am using UnRaid for my NAS
Yes...running https://localhost:8089 brings up Channels Web interface. I'm starting to think the MyCloud doesn't support SMB, except I can go directly to the share and play videos since its a public share.
I guess I'll test theory with sharing from Linux and Windows.
So what is hosting your Channels DVR Server?
Sounds like you're trying to use it as the DVR, but record over an SMB share to your MyCloud?
From your few posts looks like your DVR is running on a Windows machine?
Are both of them using the same WORKGROUP?
Do you have the same User and Password on both of them?
That is really strange.. Only thing I can think of is permissions, but like I said, I dont have a WD..