#Concurrent Session Rule terminating streams not in scope

1 messages · Page 1 of 1 (latest)

hearty fulcrumBOT
#

Hi @stone karma! Thanks for opening a support thread! Before the community can help, please make sure you have included the following:

Required Information

  • What version of Tracearr are you running?
  • Are you running in Docker, LXC, Unraid, TrueNAS, or another environment?
  • Provide your full docker compose file.
  • Include any relevant logs ( via https://pastebin.com ) or screenshots.

Describe the Issue

  • What did you expect to happen?
  • What actually happened?
  • If applicable, steps to reproduce the issue.

Useful Links

Guidelines

  • Search existing threads — your issue may already have a solution.
  • Be patient and respectful — everyone here is volunteering their time.
  • Do not ping or DM maintainers directly for support.
  • Abuse of staff or community members will not be tolerated.
granite solar
#

@stone karma ^

stone karma
#

what am i missing? 🫠

#

i think the screenshots came through

granite solar
stone karma
#

i guess it helps if i don’t try to do 3 things at a time. updating original thread

granite solar
#

So the issue is that it works, and your user just restarts the stream? This really isnt clear

stone karma
#

it’s not consistent on the first kill attempt. when it does kill it successfully if a user starts that 2nd stream again it runs

granite solar
#

please just write new messages - i cant keep scrolling up to see waht you change

stone karma
#

done, sorry. i restructured the message so its clear

granite solar
#

please slow down and focus on what is being asked so we can get to the bottom of this

stone karma
#

ok copy that i’ll post a brand new message then

granite solar
#

i mean the damage is done, lets just try harder for any future communication