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
Here a few issues i have found on the app. I spot them on an old installation and i did a new installation to descant data issues.
Stripchat plugin import of Favorite performers stop to work and you need to add the performers manually to shown on Live Cam when you filter by "Stripchat live" and "Favorites"
When you "Cancel recording" or "Stop and save recording" on an active recording, a new recording for the same performer is never triggered, even though the performer is still online. And the "Hard reset" do nothing to fix the issue.
Cancelling a recording could take an infinite amount of time.
On going recordings data dont survive an application restart. You can have on going a long session recording, if you restart the app, that recording is lost.
Thanks for the detailed report — all four issues are now fixed (see the merged PR #32):
Stripchat favorites import — Stripchat increasingly refuses direct API requests from servers (HTTP 403/418). When that happens, the followed list is now read inside a real Stripchat page in the bundled Chromium, using the saved account session. If that also fails, your local favorites are kept and both reasons are logged under "Stripchat favorite synchronization skipped".
No new recording after stop/cancel — "Stop and save" no longer blocks the room: if the performer is still online, a new recording starts as a new video on the next check. A cancel (or delete) still keeps the room suppressed until a scan sees it offline, but a hard refresh of the source now lifts that block immediately.
Endless cancellation — a cancel that the recording process ignores is now force-killed after 10 seconds, and a stop that hangs gets a second stop signal after 45 seconds, so neither can run forever.
Recordings lost on restart — on shutdown, running live recordings are saved first (up to EASYX_SHUTDOWN_GRACE_SECONDS, default 60). If the container is killed anyway, the recorded parts are joined into a video in the library on the next start; unreadable data is kept in media/.recording-recovery. Note: add stop_grace_period: 90s to your compose service (the bundled compose file now does this), otherwise Docker only allows 10 seconds to shut down. Recordings made via yt-dlp (e.g. Chaturbate) are only saved on a clean shutdown; Stripchat/CAM4/BongaCams recordings can also be recovered after a hard kill.
Activity
MajorLOL commentedon Oct 15, 2026
issues should be resolved in new commit
raccommode commentedon Oct 20, 2026
Thanks for the detailed report — all four issues are now fixed (see the merged PR #32):
EASYX_SHUTDOWN_GRACE_SECONDS, default 60). If the container is killed anyway, the recorded parts are joined into a video in the library on the next start; unreadable data is kept inmedia/.recording-recovery. Note: addstop_grace_period: 90sto your compose service (the bundled compose file now does this), otherwise Docker only allows 10 seconds to shut down. Recordings made via yt-dlp (e.g. Chaturbate) are only saved on a clean shutdown; Stripchat/CAM4/BongaCams recordings can also be recovered after a hard kill.raccommode commentedon Oct 20, 2026
All four issues are resolved in the merged PR #32 — closing this. Thanks again for the careful report! Please reopen if you still hit any of them.