You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to add a new section to an episode of a TV series.
However, when trying to save the section, an error is being thrown client-side (the Docker logs of Jellyfin do not show any error), preventing the changes from being saved:
Error: Promised response from onMessage listener went out of scope ExtensionMessagingService.js:89:34
Sicherheitsfehler: Inhalt auf https://jellyfin.femtopedia.de/web/ darf file:/// nicht laden oder verlinken.
< Everything above is before hitting "Save" - below is immediately after >
Operation failed after retries: Expected JSON response stores-DvwKlds6.js:1:1029
[Segments] Failed to create segment index.js:2:74321
Operation failed after retries: Expected JSON response stores-DvwKlds6.js:1:1029
[Segments] Failed to create segment index.js:2:74321
Here is a very short video demonstration:
2026-08-08.17-02-24.mp4
I can surely provide even more information, if necessary. I just don't know currently how I could find more useful details.
I am using Firefox 153.0.3 on Windows 11 and am currently running Jellyfin 12.0 RC4 with Intro Skipper 1.12.0.1 and Segment Editor 12.0.3.0.
Thank you very much! I am able to edit existing segments now (even though I don't know whether this was broken in the first place). However, adding new segments is still not working, sadly.
The errors in the JavaScript console are now gone and there is still no error on the server-side (i.e., in Docker).
The client now says that it successfully saved the segments, but they are still not saved, sadly.
I updated to the latest Intro Skipper prerelease for 12.0 (the one you linked) and I was able to save the segments now, indeed. Thank you!
However, the bug indeed still appears visually in the Segment Editor. Even after restarting the server, it still does not show the new intro segment there.
I searched for an option to purge Segment Editor's cache, but I cannot find one, sadly. Just in case this is just a caching issue.
After further investigation, this does not seem to be the case, though. Since the network request actually yields this:
In contrast to the request that Intro Skipper sends when opening the Timestamps tab in its config:
Oh my god, that was it! Thank you very much!
I find it a bit counterintuitive that this would affect Segment Editor, though. But I'm glad it's not something worse.
Thank you very much once again! :)
Activity
rlauuzo commentedon Aug 8, 2026
Will be fixed in the next release.
ThexXTURBOXx commentedon Aug 9, 2026
Thank you very much! I am able to edit existing segments now (even though I don't know whether this was broken in the first place). However, adding new segments is still not working, sadly.
The errors in the JavaScript console are now gone and there is still no error on the server-side (i.e., in Docker).
The client now says that it successfully saved the segments, but they are still not saved, sadly.
2026-08-09.10-10-19.mp4
rlauuzo commentedon Aug 9, 2026
Strange. Can you check if the segments appear in the intro-skipper timestamps tool after saving?
rlauuzo commentedon Aug 9, 2026
If they are in the timestamp tool and not in jellyfin try the intro-skipper pre release that fixes some issues with pushing segments to jellyfin https://github.com/intro-skipper/intro-skipper/releases/tag/12.0%2Fprerelease
ThexXTURBOXx commentedon Aug 9, 2026
I updated to the latest Intro Skipper prerelease for 12.0 (the one you linked) and I was able to save the segments now, indeed. Thank you!


However, the bug indeed still appears visually in the Segment Editor. Even after restarting the server, it still does not show the new intro segment there.
I searched for an option to purge Segment Editor's cache, but I cannot find one, sadly. Just in case this is just a caching issue.
After further investigation, this does not seem to be the case, though. Since the network request actually yields this:
In contrast to the request that Intro Skipper sends when opening the Timestamps tab in its config:
rlauuzo commentedon Aug 9, 2026
You could try opening the segment editor in its own tab with yourserverip:8096/SegmentEditor/
ThexXTURBOXx commentedon Aug 9, 2026
Same thing there, sadly. It seems like the
/MediaSegments/endpoint is returning old data in my case, for some reasonrlauuzo commentedon Aug 9, 2026
Is there a chance you have the skip first episode setting enabled in intro-skipper?
ThexXTURBOXx commentedon Aug 9, 2026
Oh my god, that was it! Thank you very much!
I find it a bit counterintuitive that this would affect Segment Editor, though. But I'm glad it's not something worse.
Thank you very much once again! :)