Can't change HTTPS port from 8920 [Cloudflare, VPN]

[Pankookis 10]

Hi

Been using Emby with Cloudflare for a year soon. I'm trying to experiment with using Emby behind a VPN (paid, not my own) but I'm running into trouble. I need to change to port from 8920 but then it fails to connect.

I used this guide https://blog.awelswynol.co.uk/2018/01/setting-up-cloudflare-with-emby

I don't forward 443 to 8920 like he does in the guide. I've been using 8920 strictly. If I change this to 60001, nothing works. Even with the VPN off, port open in router, correct IP at Cloudflare, firewall off etc. Canyouseeme show that the port is open. If I change the port back it works as usual. According to (https://support.cloudflare.com/hc/en-us/articles/200169156-Identifying-network-ports-compatible-with-Cloudflare-s-proxy), 8920 shouldn't work either (if I''m interpret it correctly)

Does anyone have experience with this setup and can point me toward a sollution?

Thanks

[Carlo 4561]

Hi,

Here is what you need to remember. Port 8096 is what Emby uses for non SSL connections and 8920 is what's used for SSL connections.  You can setup port forwarding from something like port 443 on the router to port 8920 on the Ember server machine, then you adjust the network settings to use port 443 as the external port.  However Emby is still listening only to 8920 for SSL ad your router is doing the forwarding.

Does that help clarify the way it works?

[horstepipe 422]

4 hours ago, Pankookis said:

 According to (https://support.cloudflare.com/hc/en-us/articles/200169156-Identifying-network-ports-compatible-with-Cloudflare-s-proxy), 8920 shouldn't work either (if I''m interpret it correctly)

Yeah that should be true. Are you sure that your connection really runs through cloudflare with that setup?

[Pankookis 10]

4 hours ago, cayars said:

Hi,

Here is what you need to remember. Port 8096 is what Emby uses for non SSL connections and 8920 is what's used for SSL connections.  You can setup port forwarding from something like port 443 on the router to port 8920 on the Ember server machine, then you adjust the network settings to use port 443 as the external port.  However Emby is still listening only to 8920 for SSL ad your router is doing the forwarding.

Does that help clarify the way it works?

 

1 hour ago, horstepipe said:

Yeah that should be true. Are you sure that your connection really runs through cloudflare with that setup?

I had a massive brain fart. Was running Emby with port 2087 when it was working, but it was changed to 8920 in Emby so I just read that from the Dashboard page. If I change it back to 2087 it started working again.

Seems I'm out of luck with CF unless I use the pre specified ports, unless I want to pay for the Pro package. Thanks for your time both of you!

[Carlo 4561]

Any reason why you don't want to use 80 and 443?

[horstepipe 422]

9 minutes ago, cayars said:

Any reason why you don't want to use 80 and 443?

Yeah or one of the other ports supported by Cloudflare...?

[Pankookis 10]

2 hours ago, cayars said:

Any reason why you don't want to use 80 and 443?

The reason if I remember correctly was that I used to use my VPN with a static IP that the VPN company provided as an addon. For some reason I couldn't get 443 to work because something with the VPN routing because I had the VPN on my computer and not in the router.

The reason I'm trying this now is I've moved over to Wireguard instead of OpenVPN. The VPN provider has not yet made the "static IP addon" available for Wireguard and I'm testing out some stuff in the meanwhile. I don't know if it's even possible but I can only open ports over at the VPN provider over port ~45000.

2 hours ago, horstepipe said:

Yeah or one of the other ports supported by Cloudflare...?

Must use a port number over ~45000 at my VPN provider and CF only has:

• 443
• 2053
• 2083
• 2087
• 2096
• 8443

 

[Carlo 4561]

That won't work via CF.  You can however  setup VPN directly on the Emby server and set it for whatever ports you want.  However, you'll want to watch out for matadata providers blocking VPN IP pools due to abuse from those IP ranges.

Any particular reason why you're wanting to run your Emby server behind a public VPN?

[Pankookis 10]

10 hours ago, cayars said:

That won't work via CF.  You can however  setup VPN directly on the Emby server and set it for whatever ports you want.  However, you'll want to watch out for matadata providers blocking VPN IP pools due to abuse from those IP ranges.

Any particular reason why you're wanting to run your Emby server behind a public VPN?

I use a VPN on all my computers in order to gain a bit of anonymity online so that's the reason. This was just an experiment from my part while I'm waiting for the "static ip addon" I mentioned earlier. But I had missed the CF port range when I made the post so I'll just have to wait. In the meantime I just shut off the VPN if I need to access my Emby server remotely.

Thanks