Xavives 0 Posted April 24, 2022 Posted April 24, 2022 (edited) I have the same issue: if I try to connect remotely through app.emby.media, it shows the "Connection Failure" error. However, if I connect directly through the Remote IP address, it works. How can I solve it to connect directly through app.emby.media? Edited April 24, 2022 by Xavives
ebr 15664 Posted April 24, 2022 Posted April 24, 2022 1 hour ago, Xavives said: I have the same issue: if I try to connect remotely through app.emby.media, it shows the "Connection Failure" error. However, if I connect directly through the Remote IP address, it works. How can I solve it to connect directly through app.emby.media? Hi. That is probably an indication that your server is not discovering your public IP address properly. Make sure the WAN address shown on the dashboard is correct.
Xavives 0 Posted April 24, 2022 Author Posted April 24, 2022 (edited) When I try to connect remotely to my Emby server through app.emby.media address (both http and https), it shows the "Connection failure" error. Weirdly enough, if I connect directly through the Remote (WAN) IP address of my server, it does not show the error and I can connect normally. Any idea why this is happening? I want to share Emby with some friends and family who are not tech savvy, and would like them to enter through app.emby.media Edited April 24, 2022 by Xavives
Xavives 0 Posted April 24, 2022 Author Posted April 24, 2022 (edited) UPDATE: this is happening in both Firefox and Chrome in my computer. Weirdly enough, it works with an older version of Chrome in my phone Edited April 24, 2022 by Xavives
Xavives 0 Posted April 24, 2022 Author Posted April 24, 2022 3 hours ago, Luke said: Hi, Is your remote address http or https? http
Luke 40074 Posted April 24, 2022 Posted April 24, 2022 11 minutes ago, Xavives said: http @Xavives OK so right off the bat you will not be able to use the https version of app.emby.media as it can only connect to servers with https. What version of Chrome do you have?
Xavives 0 Posted April 27, 2022 Author Posted April 27, 2022 (edited) On 4/24/2022 at 4:50 PM, Xavives said: UPDATE: this is happening in both Firefox and Chrome in my computer. Weirdly enough, it works with an older version of Chrome in my phone On 4/24/2022 at 9:07 PM, Luke said: @Xavives OK so right off the bat you will not be able to use the https version of app.emby.media as it can only connect to servers with https. What version of Chrome do you have? In my computer, the latest version of Chrome. In my phone, version 88.0 I tried connection to https version of app.emby.media remotely and it doesn't work neither. Any idea where this error comes from? Is it my server? Router? Or wrong setup of my Emby? I find it weird that everything looks normal in my Emby server: IP address is shown correctly, and if I check the ports in canyouseeme.org they look fine. It is only when I login to app.emby.media (http and https) that it shows Connection Failure, if I put directly the IP of my server and port 8096 in the browser, it connects correctly. Edited April 27, 2022 by Xavives
Luke 40074 Posted April 27, 2022 Posted April 27, 2022 Have you setup https on your emby server? Again you will need that in order to use the https version of app.emby.media
Xavives 0 Posted May 3, 2022 Author Posted May 3, 2022 (edited) Hi Luke, I have setup https on my emby server and it still the same is happening. I believe it is an error on how the "app.emby.media" portal redirects to my remote WAN address. Somehow it is not doing it correctly. The reason why I think so is because if I put directly the remote WAN address (MYIP:8096) it works as expected after I introduce the Emby Connect username+password. Any idea on what else could I do? Edited May 3, 2022 by Xavives
Luke 40074 Posted May 3, 2022 Posted May 3, 2022 27 minutes ago, Xavives said: Hi Luke, I have setup https on my emby server and it still the same is happening. I believe it is an error on how the "app.emby.media" portal redirects to my remote WAN address. Somehow it is not doing it correctly. The reason why I think so is because if I put directly the remote WAN address (MYIP:8096) it works as expected after I introduce the Emby Connect username+password. Any idea on what else could I do? What exactly happens when you try?
Xavives 0 Posted May 7, 2022 Author Posted May 7, 2022 Hi Luke, here the detailed issue with screenshots. I am connected to a remote network (from the home network I have no issues). So first I go to "app.emby.media", and after the welcome screen it sends me to Emby Connect login page, as always: After I put my Emby Connect credentials, everything looks normal: it shows my server name and the correct remote IP address (hidden here behind red square): However, as soon as I select my server, the Connection Failure error triggers. This happens from any device (phone, another computer...): Now it comes the tricky part: I try to do exactly the same but going directly to my remote IP (MYIP:8096): And if I put my Emby Connect credentials... voilà! It works: Am I missing something? Is there anything I can do, or is it an issue with the app.emby.media webapp / Emby Connect?
seanbuff 1146 Posted May 8, 2022 Posted May 8, 2022 As Luke suggested earlier, your first 2 screenshots show you using https://app.emby.media -- you will not be able to use the secured version of the webapp if your server is only running http which you demonstrated in the subsequent screenshots. Can you try explicitly using http://app.emby.media and post your results?
Xavives 0 Posted May 11, 2022 Author Posted May 11, 2022 On 5/8/2022 at 2:55 AM, seanbuff said: As Luke suggested earlier, your first 2 screenshots show you using https://app.emby.media -- you will not be able to use the secured version of the webapp if your server is only running http which you demonstrated in the subsequent screenshots. Can you try explicitly using http://app.emby.media and post your results? I did set up the server to https last week, but the outcome was exactly the same. Once I introduced user and password, the "Connection Failure" error would trigger, but using directly the SERVER_IP:8920 worked fine. I reverted the server to http for convenience. So I guess the question is still the same? Is it an issue with the webapp?
Luke 40074 Posted May 11, 2022 Posted May 11, 2022 9 hours ago, Xavives said: I did set up the server to https last week What exactly did you do to set this up?
Xavives 0 Posted May 11, 2022 Author Posted May 11, 2022 3 hours ago, Luke said: What exactly did you do to set this up? I filled these fields with my own domain name and certificate, and setup the "Secure connection mode" to "Required for all remote connections"
Luke 40074 Posted May 11, 2022 Posted May 11, 2022 1 hour ago, Xavives said: I filled these fields with my own domain name and certificate, and setup the "Secure connection mode" to "Required for all remote connections" Where did the certificate come from?
Xavives 0 Posted May 12, 2022 Author Posted May 12, 2022 19 hours ago, Luke said: Where did the certificate come from? No-IP (noip.com)
Luke 40074 Posted May 12, 2022 Posted May 12, 2022 It's possible the browser is rejecting your certificate. Can you please supply the contents of the browser debug console? Thanks.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now