• 1hitsong@lemmy.mlEnglish
    3·
    7 hours ago

    through re-sign-on after that latest update that forced it

    I’ve racked my brain to determine WHY that happened, but the only thing I can guess is Roku saw the channel differently because I packaged it instead of the previous person, so the config didn’t port over /shrug

    Never had that happen before.

    • Getting6409@lemm.eeEnglish
      2·
      7 hours ago

      I figured it was the enforcing of the trusted proxy mechanism mentioned in the release notes (only noticed because of an earlier thread here, thanks!). Once I updated my server and set the proxy settings all my clients needed to be signed again.