Cloudflare tunnel & emby connect

[markpeo 11]

Hi,

I have read through lots of posts here, on reddit & unraid forums but just cannot find a way to resolve my issue.

In a nutshell, I have a cloudflare tunnel that points to my emby server. (unraid server, official Emby docker, and Unraid-Cloudefared-Tunnel docker.) 

Using https://subdomain.mydomain.com (the same remote address url that is displayed on my server dashboard) in a web browser from anywhere outside of my LAN network, on any device, works perfectly. 

I cannot login using the android app or via app.emby.media. When I log into emby connect, the server is not shown.

If I manually add the server, I get an "Unable to reach server" message.

I use port 443 as the port when manually adding the server.

I previously had a reverse proxy setup, using a domain name (it was different to the one I am using now) and using port 443 when adding a server manually allowed me to connect from outside my LAN. The server also showed up when I signed in with emby connect. SWAG docker is now not running and port forwarding has been removed from my router (pfSense)

 

 

Edited February 14, 2024 by markpeo
missing info

[Luke 42219]

Hi, have you taken a look at this?

 

[KegTapper 8]

I setup cloudflare per sticky instructions. I just checked,  app.emby.media manual login as well as emby connect work fine through my cloudflare tunnel. 

[markpeo 11]

Thanks Luke, Yes I did read that guide/topic and couldnt find anything that related to my issue.

 

Thanks @KegTappergood to know that it works. I'll keep checking and trying some things.

I think my cloudfare setup is all good, because like I said, I can access via a web browser (direct to my https domain name and it works perfectly!

Im wondering what the android app does differently to a web browser to connect?

[Luke 42219]

Quote

When I log into emby connect, the server is not shown.

Did you link your server with Emby Connect?

Emby Connect

[markpeo 11]

Yep, i linked it and it shows when I login with emby connect, but only shows the LAN address and so it does not connect when im outside of the LAN

 

[Luke 42219]

Just now, markpeo said:

Yep, i linked it and it shows when I login with emby connect, but only shows the LAN address and so it does not connect when im outside of the LAN

 

Nothing wrong with the fact that it's showing that address. That is just indicating the most recent one used.

[markpeo 11]

ok thanks. So when i click it, i just get a message that's its unable to reach the server.

I'll keep trying

[darkassassin07 673]

A couple settings to check:

 

Public https port number: 443

External Domain: <your domain>

Secure Connection Mode: <anything except 'disabled'>

 

 

Restart the server and ensure 'Remote (WAN) access:' on the dashboard is correct: "https://<yourdomain>" (:443 may or may not be displayed in the end, it's not shown for me anymore in server v4.8)

[markpeo 11]

HI, thanks for the checklist.

public port number is 443, external domain is set and secure connection mode is set to 'handled by reverse proxy'

:443 does not show at the end, but clicking the external domain link works, so i dont htink its an issue with my remote access setup.

[darkassassin07 673]

The only other thing I'd suggest is removing the server from connect and re-adding it, now that you've ensured the remote access settings are correct.

If that still doesn't work, I'd be inclined to think there's a bug with connect not receiving the correct connection info.

[markpeo 11]

unfortunately, that didn't work, same results as earlier - Unable to reach server message

 

[markpeo 11]

OK, looks like I found the issue. Without realising it, I had 'Under attack mode' turned on in cloudflare.

I changed it to 'High' level security setting, and now I can connect using the android app & emby connect!

So, I guess the app and connect cant beat the interstitial page, but a web browser obviously does.

Thanks for the pointers guys, much appreciated.

[mbc0 68]

@markpeoHi, I am looking to go down the cloudfare route as I am using a 5G router and Vodafone do not allow port forwarding, can I ask what your overall experience is please? any problems?

 

Thank you!

[markpeo 11]

Hi, @mbc0

Experience with CloudFlare tunnel has been great! I only really use it for audio, but have done some testing with video and didn't find any difference between having ports directly open or using a reverse proxy set-up. 

 

Edited April 27, 2024 by markpeo

[mbc0 68]

7 hours ago, markpeo said:

Hi, @mbc0

Experience with CloudFlare tunnel has been great! I only really use it for audio, but have done some testing with video and didn't find any difference between having ports directly open or using a reverse proxy set-up. 

 

Thank you for the reply! Would love to know if anyone is using this for video?

[KegTapper 8]

I use it for video. I have no problems 

[mbc0 68]

1 hour ago, KegTapper said:

I use it for video. I have no problems 

Thanks for the comment, did you set it up like in this guide? I hear talk of disabling cache for video, can I ask how you did it?

 

 

[KegTapper 8]

Sorry for late response. I already had cloudflare set up as per the sticky instructions as well as caddy. I moved and only isp option was cgnat over wisp. So, I quickly spun up a CF tunnel. I couldn't believe how easy it was. It's been running for close to two years now without any problems.

[GlewShrake 1]

Check if Cloudflare's security settings are blocking non-browser requests. Try lowering the security level for your Emby subdomain, like switching from ""Under Attack Mode"" to ""High"" or ""Essentially Off.""

Make sure the external domain in Emby's remote access settings matches what you've set up with Cloudflare Tunnel. You could also try temporarily disabling the Cloudflare proxy (grey cloud mode) to see if that helps.

Using a booter service might also help you identify any issues with how your server handles traffic.

[AncyAndal 1]

Hey I am having this issue too but my "Under Attack Mode" is disabled. Anyone else figure the solution to this ive been stuck on it for about 12 days now. Just want to use the app on my GF's TV 

[Luke 42219]

On 1/11/2025 at 12:56 AM, AncyAndal said:

Hey I am having this issue too but my "Under Attack Mode" is disabled. Anyone else figure the solution to this ive been stuck on it for about 12 days now. Just want to use the app on my GF's TV 

Re: 

 

[T_Tronix 16]

I have a question relating to this topic. My cloudflare is on my hassio (homeassistant server). The cloudflate domain works but cloudflare already added the 8096 port into it. I noticed when I place this domain under the External domain it add an extra 8096.

So lets say my cloudflare domain is: emby.server.com (which is linked to 196.168.1.XXX:8096), Emby makes it emby.server.com:8096 which is basically 196.168.1.XXX:8096:8096 hence it doesn't work when I click on it fromt the emby dashboard but when I use emby.server.com on its own it works but brings me to a login page that doesn't work (no matter what login I use it won't connect me).

Edited 1 hour ago by T_Tronix

[darkassassin07 673]

Domains point at IP addresses, NOT port numbers.

 

Your domain only points to 192.168.1.xxx. With http, web browsers will try port 80 unless told otherwise. (https, they'll try 443)

Cloudflare however is a proxy that is listening to port 80/443, and proxying to port 8096.

Set your 'public http port number' to 80 under 'dashboard'>'network', and the address displayed on the dashboard will work.

Edited 1 hour ago by darkassassin07

[T_Tronix 16]

10 minutes ago, darkassassin07 said:

Domains point at IP addresses, NOT port numbers.

 

Your domain only points to 192.168.1.xxx. With http, web browsers will try port 80 unless told otherwise. (https, they'll try 443)

Cloudflare however is a proxy that is listening to port 80/443, and proxying to port 8096.

Set your 'public http port number' to 80 under 'dashboard'>'network', and the address displayed on the dashboard will work.

Now both lan and wan don't work. I set the port from 8096 to 80 inside my Emby server http port. In cloudflare I have:

  - hostname: emby.server.com
    service: http://192.168.1.xxx:8096