Jump to content


Photo
- - - - -

[BUG] app.emby.media Insecure Content Blocked

bug connect app login

  • Please log in to reply
9 replies to this topic

#1 roblav96 OFFLINE  

roblav96

    Member

  • Members
  • 13 posts
  • Local time: 05:28 PM

Posted 12 June 2019 - 05:52 PM

I have the http route redirect to https with a reverse proxy,

 

5d0174eace550_ScreenShot20190612at54640P

 

Since I'm on the https of 'https://app.emby.media' the client sends a request to: 'http://foobar.media:8096/emby/system/info/public' which results in a 'Connection Failure'.

 

5d0174f792a24_ScreenShot20190612at53944P

 

It should automatically default to https, not http when calling the 'system/info/public' route.


Edited by roblav96, 12 June 2019 - 05:56 PM.


#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131281 posts
  • Local time: 05:28 PM

Posted 12 June 2019 - 05:55 PM

Hi, what you need to do is configure your advanced server settings so that the https address is displayed as the remote address on your emby server dashboard.



#3 roblav96 OFFLINE  

roblav96

    Member

  • Members
  • 13 posts
  • Local time: 05:28 PM

Posted 12 June 2019 - 06:02 PM

Hi, what you need to do is configure your advanced server settings so that the https address is displayed as the remote address on your emby server dashboard.

 

5d01758e33e4c_ScreenShot20190612at55658P

 

It's a browser javascript error, this method here in 'connectionmanager.js' needs to take into account the 'window.location.protocol' so it doesn't attempt an impossible request to an http url from an https url, that the browser will block.

function normalizeAddress(address) {
	return address = address.trim(),
	0 !== address.toLowerCase().indexOf("http") && (address = "http://" + address),
	address = replaceAll(address, "Http:", "http:"),
	address = replaceAll(address, "Https:", "https:")
}

Edited by roblav96, 12 June 2019 - 06:03 PM.


#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131281 posts
  • Local time: 05:28 PM

Posted 12 June 2019 - 06:09 PM

Ok you're referring to the attempt on the local address. Yes you're right. When the browser protocol is https, we should skip requests to http urls because we already know they'll fail. Thanks.



#5 roblav96 OFFLINE  

roblav96

    Member

  • Members
  • 13 posts
  • Local time: 05:28 PM

Posted 12 June 2019 - 06:14 PM

Ok you're referring to the attempt on the local address. Yes you're right. When the browser protocol is https, we should skip requests to http urls because we already know they'll fail. Thanks.

 

No worries friend, glad to help =] 


Edited by roblav96, 12 June 2019 - 06:14 PM.


#6 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131281 posts
  • Local time: 05:28 PM

Posted 15 June 2019 - 02:42 PM

Can you try this again? thanks.



#7 Luc. OFFLINE  

Luc.

    Member

  • Members
  • 11 posts
  • Local time: 11:28 PM

Posted 19 June 2019 - 09:26 AM

Same problem here. I can't add my server although it's accessible directly via its url or IP address from outside my network.



#8 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131281 posts
  • Local time: 05:28 PM

Posted 19 June 2019 - 09:48 AM

@luc why do you feel it's the same problem?

#9 roblav96 OFFLINE  

roblav96

    Member

  • Members
  • 13 posts
  • Local time: 05:28 PM

Posted 12 July 2019 - 11:10 PM

@Luke yes this works as intended now =]



#10 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 131281 posts
  • Local time: 05:28 PM

Posted 12 July 2019 - 11:15 PM

Thanks for the feedback.





Also tagged with one or more of these keywords: bug, connect, app, login

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users