Jump to content

Question about remote access when using domain


Go to solution Solved by Luke,

Recommended Posts

Posted

Hi all,

 

I am having an issue whereby I am unable to connect to my Emby Server remotely when using a domain.

 

I have a SSL certificate that is correctly associated with the domain and works as it should.

 

I have port forward setup on my router, and as a test I have used the external IP of my router as the external domain and this worked correctly and allowed me to access remotely.

 

I've taken a log to show that it accepts the connection via the external IP as the external domain.

 

If you require any further information please let me know.

 

Thanks,

 

Michael 

Posted

Hi there, what exactly is happening?

Posted

Hi Luke,

 

I am trying to use a domain name but it doesn't appear to work.

 

I own the domain, and the domain has an SSL certificate on which I have added to the Emby Server as well.

 

Thanks,

 

Michael

Posted

Hi there, what do you mean by doesn't work? What happened when you tried to connect? What kind of SSL cert?

Posted

Hi,

 

When I try connecting, either putting in the server address and port manually or logging in using a Emby Connect account that is available to connect remotely, I get the error;

 

"Connection Failure. We're unable to connect to the selected server right now. Please ensure it is running and try again".

 

The SSL certificate is a .pfx certificate, also known as a P12 which is what it says Emby requires.

Posted

@@MickyG1989, where did the SSL certitifcate come from? Because there could be a couple possible explanations. 

 

One is that it is just a network connection error. The other possibility is that the device (browser?) you're trying to connect with is rejecting your SSL certificate.

Posted

Can you capture the browser debug console contents when you try to connect? Thanks.

Posted

@@Luke,

 

Please find attached the logs requested.

 

Thanks,

 

Michael

Posted

Hi, did you forget to attach it?

Posted (edited)

My bad, see attached.

Edited by MickyG1989
Posted

This is the emby server log. Can you please attach the browser debug console contents from the browser that you're trying to connect with? Thanks.

Posted (edited)

@@Luke,

 

Apologies, I misunderstood.

 

Please find attached debug console logs from Google Chrome.

 

Thanks,

 

Michael

Edited by MickyG1989
Posted

Ok so if you look at the console contents you can see the connection is timing out. That suggests a general problem of network connectivity.

 

Have you checked out our Connection Troubleshooter?

Posted

Thanks for the response and the link to the support section.

 

I believe I may have misunderstood how the remote connection works.

 

From reading the support page I wanted to clarify something; to perform an external connection you have to use the external IP address of the network Emby Server is on locally?

  • Solution
Posted

 

 

to perform an external connection you have to use the external IP address of the network Emby Server is on locally?

Yes, or the domain name, if you have a domain name.

  • Like 1
Posted

@@Luke,

 

Thanks for the prompt response and assistance with this. In the end it was down to my misunderstanding.

 

I'm happy for this to be closed off.

Posted

Thanks for the feedback !

  • 1 month later...
Posted

Hey Guys,

 

I am receiving the following error from NGINX logs. Also to note, when launching the program, it opens and closes instantly. The log is as follows.

 

2020/04/09 19:29:42 [notice] 3360#552: Fatal: wait for sockapi failed
2020/04/09 19:35:50 [notice] 1324#6576: Fatal: wait for sockapi failed
2020/04/09 19:36:02 [notice] 5812#2284: Fatal: wait for sockapi failed
2020/04/09 19:48:26 [notice] 1212#4912: Fatal: wait for sockapi failed
 
I have been trying to connect my domain emby.mydomain.com, using cloudflare and NGINX, to no avail. I am never able to get a remote connection. cloudflare returns error 522.
 
Thanks.
Posted

 

Hey Guys,

 

I am receiving the following error from NGINX logs. Also to note, when launching the program, it opens and closes instantly. The log is as follows.

 

2020/04/09 19:29:42 [notice] 3360#552: Fatal: wait for sockapi failed
2020/04/09 19:35:50 [notice] 1324#6576: Fatal: wait for sockapi failed
2020/04/09 19:36:02 [notice] 5812#2284: Fatal: wait for sockapi failed
2020/04/09 19:48:26 [notice] 1212#4912: Fatal: wait for sockapi failed
 
I have been trying to connect my domain emby.mydomain.com, using cloudflare and NGINX, to no avail. I am never able to get a remote connection. cloudflare returns error 522.
 
Thanks.

 

 

Hi there, have you compared your nginx config to that of @@pir8radio?

pir8radio
Posted

 

Hey Guys,

 

I am receiving the following error from NGINX logs. Also to note, when launching the program, it opens and closes instantly. The log is as follows.

 

2020/04/09 19:29:42 [notice] 3360#552: Fatal: wait for sockapi failed
2020/04/09 19:35:50 [notice] 1324#6576: Fatal: wait for sockapi failed
2020/04/09 19:36:02 [notice] 5812#2284: Fatal: wait for sockapi failed
2020/04/09 19:48:26 [notice] 1212#4912: Fatal: wait for sockapi failed
 
I have been trying to connect my domain emby.mydomain.com, using cloudflare and NGINX, to no avail. I am never able to get a remote connection. cloudflare returns error 522.
 
Thanks.

 

 

that error means you are trying to have nginx listen on a port your computer is already using...      Why do you need nginx, and cloudflare?  you can use a domain name and still have it point directly to emby.    Usually only need cloudflare if you have lots of users, and/or users in other countries.    and you usually only need nginx if you run multiple servers on one domain name. 

Posted

I don't need nginx, I thought it would help me fix the problem. I was not able to get it to work with just cloudflare so I had to do this. I followed swynol's tutorial exactly, but I get the same issue. Cloudflare 522. Do I need to you cloudflare proxy, or can I use DNS only with lets encrypt certs straight on emby.

.

pir8radio
Posted (edited)

I don't need nginx, I thought it would help me fix the problem. I was not able to get it to work with just cloudflare so I had to do this. I followed swynol's tutorial exactly, but I get the same issue. Cloudflare 522. Do I need to you cloudflare proxy, or can I use DNS only with lets encrypt certs straight on emby.

.

 

you dont need cloudflare,  i would say get it working with just emby, then start adding bells and whistles..     I think the issue people run into is with lets encrypt not being trusted by all streaming devices, where as with cloudflare i have not seen any ssl issues.  but i may be wrong, never used lets encrypt

Edited by pir8radio
Posted

How would I do it without cloudflare? I tried to use a ddns service like cloudns, and then used cloudflare to set a cname to cloudns to my domain.com. Then I downloaded certificates from zerossl.com to my domain.com. It still did not work. 

 

What process would you recommend? If it helps, I purchased the domain from Njal.la, and set the cloudflare nameserves. 

pir8radio
Posted

so if you are already using CF for your DNS servers then might as well use it to point to your emby server...   where are you stuck?    Can you connect directly to your emby server with your emby server internet IP?  thats the first step to get working,  then you can point CF to your IP address (a name) then test that.    in order to use CF you have to change your emby external ports to 443 (https) and 80 (http)

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