Posts: 15
Joined: Jan 2011
Reputation:
0
2018-11-06, 12:03
(This post was last modified: 2018-11-06, 12:08 by ArianHD.)
Hello!
I'm sharing my lib using Apache 2.4.25 listing directory and accessing remote as Web server directory (HTTPS).
Everything works great except external subtitles. Do I have to do something extra in order KODI to see them?
All of my external subs are stored in the same folder as the video using extension with language flag. Example movie.en.srt in same folder with movie.mp4.
Watching at home with Samba share, all perfect.
Thank you!
Posts: 14,103
Joined: Mar 2010
Reputation:
568
PatK
Team-Kodi Member
Posts: 14,103
2018-11-07, 18:43
(This post was last modified: 2018-11-07, 18:45 by PatK.)
Using SMB networking external .srt subtitiles work fine (they do need to be the same name as the video e.g I see you have 'movie.en.srt' vs movie.srt unless you're pathing them direct with the subtitle browser) as far as I can see if they have the proper path, they should load but "Apache 2.4.25 listing directory and accessing remote as Web server" is not something I'm using atm, perhaps others will chime in.
Posts: 4
Joined: Sep 2013
Reputation:
0
I have the exact same setup/problem... if you change your library connection to ftp instead it will find the subs but everything is way slower... I've tried almost everything i could but i was never able to autoload subs with http sources.
Posts: 2
Joined: Jan 2017
Reputation:
0
I can confirm this behavior and imho is a bug.
In my case I have SRT files (named correctly and working over SMB and other protocols) in the same folder as the video files (season of a tv show for instance) and I have to go to "subtitles -> browse for subtitle" to get a list of SRT files in the same folder and manually select the correct SRT for the epsiode that is currently playing in order for Kodi to load the subs. So it is able to find the SRT's over HTTPS source (otherwise it could also not list them when using "browse for subtitle") but it simply doesn't load them automatically.
I hope this can be fixed in a future release as I'm making my lib available to my sister on a remote connection but do not want to give her permission to delete anything in my lib. That's why I opted to use HTTPS because that way it would never be possible to delete anything in that source.
Posts: 1
Joined: Nov 2022
Reputation:
0
2022 almost finish, any update on this?
Posts: 283
Joined: Feb 2014
Reputation:
3
as a workaround you can use webdav which is like the same as https