Jump to content

Reverse Proxy with a 301 redirect from port 80 to 443


plupien79
Go to solution Solved by plupien79,

Recommended Posts

plupien79

Got emby behind a Sophos UTM so an Apache based Reverse Proxy. WebSocket passthrough is enabled. SSL is from LetsEncrypt. Current Active Premier account

Local Ports are set to default in Emby

Public http is 80 public https is 443 port 80 redirects to https on port 443

The roku app connects (over WAN) is able to be signed in (manually, not using emby connect) can browse but can't play anything. Browser works fine.

 

Is there something wrong with this config, if so what, and can it be fixed without resorting to using an unencrypted connection?

 

Link to comment
Share on other sites

3 minutes ago, plupien79 said:

SSL is from LetsEncrypt

Hi.  This may be your issue but we need more details on exactly what you are doing and what isn't working.  Thanks.

Link to comment
Share on other sites

plupien79

I have a user who logs in remotely to use emby. The emby android app works just as expected.

The Reverse proxy points to the 8096 port using http internally.

I had her setup her Roku to connect to my emby server. She entered the FQDN ETC. It will connect and she can browse content, but when she tries to play anything, it give the loading circle, no progress then just stops.

I have a FQDN emby.mydomain.com with emby as a subdomain. The SSL cert is assigned with the subdomain. Emby's Secure Connection mode is set to (Reverse Proxy Handles)

It works 100% with LAN roku devices, and 100% using web browsers LAN or WAN

 

Edited by plupien79
Link to comment
Share on other sites

pwhodges
19 minutes ago, plupien79 said:

I had her setup her Roku to connect to my emby server. She entered the FQDN ETC.

Just to be clear, does she specify https:// ?  If not, I wonder if the client can act on forwarding but the player cannot.

Paul

Link to comment
Share on other sites

plupien79
12 minutes ago, pwhodges said:

Just to be clear, does she specify https:// ?  If not, I wonder if the client can act on forwarding but the player cannot.

Paul

We have tried both https:// prefixing the FQDN and just the FQDN. Both result in the same behavior.

Link to comment
Share on other sites

19 hours ago, plupien79 said:

Sent approx 350pm Eastern Time. Username Amanda file attempted Encanto.mkv

Hi. I found a log at 3:41 but the user was "SCRUFFY" and there was no attempt at playback in it.

Link to comment
Share on other sites

  • 4 months later...
  • Solution
plupien79

This is now working.

Backend connection pooling was disabled. Enabling that in the proxy has resolved the issues. Remote Roku devices can now play movies.

Edited by plupien79
  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...