I have a couple things set up:

The configuration:

  • DNS points to my IP
  • Nginx configured to point to Authentik for the metube subdomain
  • Authentik configured to point to the correct containers after authenticating

What I’m experiencing:
Upon initial login to Authentik, MeTube works correctly. Restarting or closing the browser causes MeTube to fail to connect to the server until I clear cookies and re-authenticate (see picture). Accessing MeTube by its port on the host IP works fine. All other services connect fine.

Does anyone know what is causing this?

Related note - I’ve seen MeTube do this before when the container wasn’t even running. I think it has something to do with how much info the container caches in the browser or something.

  • Footnote2669
    link
    fedilink
    English
    228 days ago

    I think I’ve had a similar problem with a different container. After restarting the browser, does it work if you authenticate another app?

    • @jws_shadotakOP
      link
      English
      1
      edit-2
      28 days ago

      No. MeTube only loads correctly after clearing the cookies and forcing me to re-login to Authentik. Even if I manually log out and try MeTube again, it doesn’t work. Only clearing cookies fixes it temporarily.

      The other apps authenticate and load correctly every time.

  • Turing spider
    link
    fedilink
    English
    128 days ago

    does anything weird appear in your browser console when opening metube for the second time?