If I don’t put anything there at all and just try to have a file separator it also fails with a 404, although the error log shows a different path than expected:
MediaReaderH264.open[vod/mp4:]: Not found: C:/Wowza/content/127.0.0.1/myStream/myStream_20181129_0912/myStream_160p.mp4.
I’ve used this sort of subdirectory setup with other instances and not had any problems, so I’m guessing it is something related to my setup, but what? What controls this sort of behavior? And why is the localhost address being used in the file lookup?
Hello @kurt mehlhoff, thank you very much for sharing this information with us. Typically, our engineers require a support ticket to run tests on your files so we can more accurately identify the cause.
We’d also like to check to see if it has anything to do with the Engine version you’re using since we now offer 4.7.6. But, again we’d like to take a closer look to identify the issue. Thank you.
Ok thanks for trying that first @kurt mehlhoff. The engineers are suggesting you submit a support ticket and they will work with you directly at this point.
Note that definst will show up in our sample player when you add “mp4:subdirectory/testfilemp4” to the Media File Name section. We also have a blog post that addresses this.
When using a subfolder for content, or a folder other then the /content folder, you will need to name an application instance, or use definst to access the files.