Jump to content

New Emby Setup - Can't connect to server remotely


Erighan
Go to solution Solved by Erighan,

Recommended Posts

If you try the plain http version of http://app.emby.media, does that work?

 

If you are using a self-signed ssl cert (which is the default), then the cert has to be pre-authorized onto apple devices. so that's why i would try the http version.

Link to comment
Share on other sites

techworld

Here is my test results:

 

LAN: 

External URL (HTTP/HTTPS) = Connected

https://app.emby.media = Connected

Emby app (HTTP/HTTPS) = Connected

 

WAN:

External URL (HTTP/HTTPS) = Connected

https://app.emby.media = Not Connected

http://app.emby.media = Not Connected

Emby app (HTTP) = Not Connected

Emby app (HTTPS) = Not Connected

 

I'm using the default self-cert.

 

How do I pre-authorize the my iPhone?

Edited by techworld
Link to comment
Share on other sites

Did you enable the option in Advanced -> Hosting to report https as the external address? if you did, try disabling that, then restart the server and try http://app.emby.media

 

Thanks.

Link to comment
Share on other sites

techworld

It worked on Emby app if I use http like you instructed.

 

This is interesting...

 

Disabled " report https as the external address" made a difference.

 

Why it wouldn't work on HTTPS via Emby app?

 

WAN:

External URL (HTTP/HTTPS) = Connected

https://app.emby.media = Connected

http://app.emby.media = Connected

Emby app (HTTP) = Not Connected

Emby app (HTTPS) = Not Connected

Edited by techworld
Link to comment
Share on other sites

The server ships with a self-signed cert. Most devices are going to reject those unless you configure them otherwise. (Or unless we configure the app to allow it, which we do when possible, like on android).

 

So if you want to use https, your options paying for a cert from a trusted authority, or configuring each device to accept the self-signed cert that we setup by default.

 

If you notice the chrome browser initially gives you that warning about the cert not being trusted and gives you the option to override. Chrome has done it in a friendly way. Other browsers and devices have not and the procedure is not as obvious.

Link to comment
Share on other sites

techworld

I'm thinking the self cert is the issue.

 

 

I bought the Emby app last night, and I wan to use it via https.

How do I go about it?

 

If not, then I can authorize my iPhone to accept the self-cert.

I can't find the option to pre-authorize my iPhone.

Are you prefering to the API Keys in the Security option?

 

Update: I imported my pfx into my iPhone, and to Emby server, but I still unable to connect via HTTPS on Emby Connect.

 

Note: report https as the external address is Enabled.

 

After I imported my pfx key into my iPhone, here's the results:

 

WAN:

External URL (HTTP/HTTPS) = Connected

https://app.emby.media = Connected , but Inconsistent

http://app.emby.media = Connected

Emby app (HTTP) = Connected

Emby app (HTTPS) = Not Connected

Edited by techworld
Link to comment
Share on other sites

  • 3 weeks later...
techworld

I finally manage to convert Let's Encrypt cert and got it to work on Emby app with SSL.

 

You can close this thread now.

 

Thanks.

Link to comment
Share on other sites

  • 3 weeks later...
Junior90210

Hey I'm having the same problem I opened up port 80 and still could not connect with my portable computer.  I can connect with the computer that has my server on it though.  Please help?

Link to comment
Share on other sites

Hey I'm having the same problem I opened up port 80 and still could not connect with my portable computer.  I can connect with the computer that has my server on it though.  Please help?

 

Hi, welcome. You should not need to touch port 80. did you customize the ports in server settings?

Link to comment
Share on other sites

  • 4 weeks later...
scharbag

I have run into a similar problem today.  My server is setup report HTTPS as the external address.

 

I have port forwarding setup on my router.  Here is what I can connect to:

 

HTTP Web browser HTTP - NOT connected (router port not forwarded, so this is OK)

HTTPS Web browser HTTPS - connected

HTTP Emby.Media (laptop and phone over cell phone connection) - not tested

HTTPS Emby.Media (laptop and phone over cell phone connection) - connected

HTTP iOS Emby App - not tested (I think)

HTTPS iOS Emby App (cell connection) - NOT connected (failure to connect to server error message given)

 

I have the server running within a VirtualBox VM.  The Windows Firewall service is disable on that server and Emby is the only thing it runs and the only port that can reach it is a custom TCP port (not 8920).

 

If I test the iOS Emby App while on WiFi, and I use the Emby Connect username, the phone will connect (is this somehow using the HTTP port internally?).  If I try with my phones on LTE, it fails to connect to the server as listed above.  I can connect via Safari on the phone and I have trusted the certificate both on WiFi and LTE.

 

If I try to use the IP address within the Emby App on iOS, it will not connect on WiFi or LTE when using the HTTPS address.

 

Any help with this would be awesome as I do NOT want non-HTTPS traffic leaving my network.

 

Crappy thing is I am sure this was working not that long ago, but then I moved my servers around.

 

Cheers,

Link to comment
Share on other sites

What kind of ssl cert do you have? the default one installed by emby server or your own? The key issue is whether or not your browsers & devices are going to trust the cert.

Link to comment
Share on other sites

scharbag

I use the default cert.  The web browsers are fine after I tell them to trust the cert.  The Emby app just says the server cannot be connected to.

 

If it is an SSL error, it would be great to have that as a specific error.  And then have an ability to trust the cert within the app.

 

Not a big deal cause I can just login remotely using Safari (via both direct address and Emby Connect) but I am positive it worked before I moved my server to a windows VM.

 

Cheers,

Link to comment
Share on other sites

Yea we do this for android it's just not quite as easy with iOS. I do plan to revisit it again in the near future though.

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