Hello,

Long time lurker, first time poster and eternal newbie in selfhosting.

I have installed cloudflare tunnel in order to allow my Emby installation to be reached externally. (Previously was using tailscale but now trying this solution to expand my ‘reach’ and include my parents houshold)

The tunnel with email OTP works like a charm, but the access seems to be browser specific, so the Emby app doesn’t seem to be able to connect (as it faces the email OTP challenge I suppose)

Is there a way to combine both?

I actually went down the path of writing a little script that tries to authorize the IP of someone that managed to pass the OTP challenge via browser. ( I get the user’s IP and update the cloudflare policy via its API)

Seems to be overkill, any suggestions?

Thx

@Unmapped@lemmy.ml
link
fedilink
English
3
edit-2
1M

From what I understand running high bandwidth things like video streaming through cloudflare tunnels will get your cloudflare account banned or charged (which is why they require payment info to setup tunnels).

Best to keep things like emby, jellyfin, and Plex to tailscale or just open the port.

Idk how emby works but with Plex I feel pretty safe having port open. Since any logins have to auth though Plex’s servers.

@Dust0741@lemmy.world
link
fedilink
English
11M

I have setup the same thing as a temp measure, but i believe that something like Authelia or Keycloak should replace and be better than Cloudflare’s email OTP.

@athes@lemmy.world
creator
link
fedilink
English
1
edit-2
1M

But this implies the check happens on my server right ? Which probably makes sense for advanced hosters.

@Dust0741@lemmy.world
link
fedilink
English
11M

Correct. But also public access should be considered advanced

Create a post

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!

  • 1 user online
  • 81 users / day
  • 114 users / week
  • 245 users / month
  • 853 users / 6 months
  • 1 subscriber
  • 1.54K Posts
  • 8.72K Comments
  • Modlog