Jump to content

Recommended Posts

Posted

yes, via a web browser, the external connection works very well. the previous version of the application worked very well, and I didn't change anything in my configuration.

Posted
On 4/19/2022 at 8:59 AM, Benit0 said:

yes, via a web browser, the external connection works very well. the previous version of the application worked very well, and I didn't change anything in my configuration.

Hello @Luke, do you have a way to solve my problem ?

Posted
On 4/23/2022 at 3:05 AM, Benit0 said:

Hello @Luke, do you have a way to solve my problem ?

Are you using a reverse proxy, and if so, which one?

Posted (edited)
12 hours ago, Luke said:

Are you using a reverse proxy, and if so, which one?

Yes, I use Yunohost, via a nginx server, which redirects requests to my emby server installed on a raspberry pi. It worked very well until now, and no change on my configuration.

Edited by Benit0
Posted
On 4/27/2022 at 2:45 AM, Benit0 said:

Yes, I use Yunohost, via a nginx server, which redirects requests to my emby server installed on a raspberry pi. It worked very well until now, and no change on my configuration.

OK, I would suggest comparing your nginx configuration to that or pir8radio: 

 

Posted

Hello @Luke,

My parameters are globally the same. I even tried to test the configuration proposed by pir8radio, but it still does not solve the problem. I only have the connection via the application (via the external network) which does not work. Is it not possible that it comes from the application itself? Because it was working fine before.
I tried a connection via https://app.emby.media/. Attached is the log file containing the errors.

app.emby.media-1651410957027.log

pir8radio
Posted
5 hours ago, Benit0 said:

Hello @Luke,

My parameters are globally the same. I even tried to test the configuration proposed by pir8radio, but it still does not solve the problem. I only have the connection via the application (via the external network) which does not work. Is it not possible that it comes from the application itself? Because it was working fine before.
I tried a connection via https://app.emby.media/. Attached is the log file containing the errors.

app.emby.media-1651410957027.log 5.63 kB · 1 download

what is that log from?   something is setup wrong on your proxy or emby server..    emby network settings should be: secure connection mode - handled by reverse proxy"  external domain and public ports should be set in emby too.    

Posted

This log comes from the debug mode of my browser when I try to connect via the link "https://app.emby.media/". The secure connection mode setting is of course handled by reverse proxy. The external domain and public ports are well defined too. Again, everything was working fine before, and I haven't changed anything.

Posted
On 5/7/2022 at 11:41 AM, Benit0 said:

This log comes from the debug mode of my browser when I try to connect via the link "https://app.emby.media/". The secure connection mode setting is of course handled by reverse proxy. The external domain and public ports are well defined too. Again, everything was working fine before, and I haven't changed anything.

It looks like you did a manual connection to your http address, that's not going to work from the https version of the emby web app because the browsers don't allow that. You either need to connect using your https address, or use the http version of the hosted web app, http://app.emby.media

  • Agree 1
  • 3 weeks later...
Posted

I put the port 443 corresponding to my proxy server, and it works again (not on all applications). This is strange because before everything worked fine with port 8096. Thanks for your help.

  • Thanks 1

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...