this post was submitted on 22 Apr 2024
14 points (93.8% liked)

Selfhosted

40296 readers
428 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 7 months ago

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