Help Required New User

[joolsclop 1]

I downloaded the Emby Server to a windows machine and all seems OK . It shows that the server is up to date and shows the IPs to connect. I then tried Android TV app on my Shield but no connection, then tried from my Android phone No connection just shows the Emby Icon in a black screen , nothing else. Then UI trtied Emby Theatre on a different windows PC. Same again sometimes it show the server named but I cant conncet to it , other time iti just shows Emby icon in the centre of a black screen. I opened 8096 port on the server firewall.

I've been trying for hours and am near to giving up. Please help. 

ALL logs attached

hardware_detection-63720139241.zip

[Luke 42079]

Hi there, I would suggest checking out our Connection Troubleshooter:

https://support.emby.media/support/solutions/articles/44001849007-connectivity

 

Please try the steps listed there and let us know which ones succeed and which ones do not. Thanks !

[joolsclop 1]

I'd already read through that. I can access via localhost on the same device but not on anything else.

[Happy2Play 9780]

I'd already read through that. I can access via localhost on the same device but not on anything else.

What firewall rules do you have for embyserver.exe?

 

What network type is your pc network set to Public and Private?

[rbjtech 5284]

"I opened 8096 port on the server firewall."

 

Can you share the rule as I suspect (as Happy2Play says) your Inbound firewall rule is possibly incorrect (Outbound is usually not restricted anyway) and/or and on the wrong 'profile' because emby works on the local machine.

 

It's also worth disabling the Port Mapper plugin, but check the firewall rule first.

Edited March 19, 2020 by rbjtech

[joolsclop 1]

"I opened 8096 port on the server firewall."

 

Can you share the rule as I suspect (as Happy2Play says) your Inbound firewall rule is possibly incorrect (Outbound is usually not restricted anyway) and/or and on the wrong 'profile' because emby works on the local machine.

 

It's also worth disabling the Port Mapper plugin, but check the firewall rule first.

Thanks for your assistance. Firewall rule image attached.  Still no joy, have tried everything I know .nothing connects. I noticed on the server under Users there is nothing and the roundal keeps spinning forever?

Edited March 19, 2020 by joolsclop

[Luke 42079]

 

 

I noticed on the server under Users there is nothing and the roundal keeps spinning forever?

Please attach the emby server log. thanks.

[joolsclop 1]

Please attach the emby server log. thanks.

Logs attached

hardware_detection-63720154794.zip

[Luke 42079]

Are you using some kind of reverse proxy or vpn?

[joolsclop 1]

Yes VPN on the router and all clients are connected to the router

[Luke 42079]

Hmm, I'd like to know what it sends in it's http headers for x-forwarded-for and x-real-ip. Do you know by any chance? 

[joolsclop 1]

In a word no, but I'm now suspecting it's my setup causing the problems. I have a two router setup.Router two is connected to R1 and R2 runs a VPN client and is connected to a NAS storing the movies etc, R2 is setup as gateway so the NAS does not route via R1. Clients that use storage on the NAs are connected to R2.

Make sense?

[Luke 42079]

Can you install the beta server? I'm pretty sure that will resolve this, but once you're in I'd like to have you play a video and then attach the server log. I'd like to see the http headers that it sends so that we can make possible adjustments. Thanks.

[joolsclop 1]

Thanks , yes I'll give it a go to tomorrow and post back then.

[Luke 42079]

Thanks.

[rbjtech 5284]

Thanks for your assistance. Firewall rule image attached.  Still no joy, have tried everything I know .nothing connects. I noticed on the server under Users there is nothing and the roundal keeps spinning forever?

 

What is in 'scope' ?  Local subnet only ?  If you are using multiple routers/VPN's/networks/VLAN's - then you'll need to include all the networks in the scope.

 

Also worth running "netstat -a | find "8096" to confirm that emby is listening on IP x and port 8096. 

 

If you have another PC on the same network as the emby server, then does that connect ok ?  Lets start with the basics ..

[joolsclop 1]

What is in 'scope' ?  Local subnet only ?  If you are using multiple routers/VPN's/networks/VLAN's - then you'll need to include all the networks in the scope.

 

Also worth running "netstat -a | find "8096" to confirm that emby is listening on IP x and port 8096. 

 

If you have another PC on the same network as the emby server, then does that connect ok ?  Lets start with the basics ..

OK , as you say back to basics with this thing. I have now connected both server and clients to router 1 instead of the VPN router 2. Happliy Im getting somewhere and now the clients can see the library files which I continue to have on the NAS connected to router 2. All play OK so now I'm down to the business of fine tuning the look and feel of it.

Two problems immediately arise but probably for other forums. Neither Cover Art nor BlurN nor Trailers plugins appear to work even though it says I have 14 days trial??? Since this is the first time I've used Emby that is not very helpful to test ..

I must say I'm looking to move from Plex which has run fine until the latest changes and despite being a Pass holder I'd be willing to move to Emby if I could get it set up nicely, so far things are proving problematic but I am grateful for the help received thus far which is significanlty better than Plex offers.

[joolsclop 1]

Thanks , yes I'll give it a go to tomorrow and post back then.

BTW the beta server didn't help at all and I was unable to access anything let alone play a video other than on localhost.

[Luke 42079]

BTW the beta server didn't help at all and I was unable to access anything let alone play a video other than on localhost.

 

Can you please attach the emby server log? Thanks.

[joolsclop 1]

Can you please attach the emby server log? Thanks.

Here they are. These are from my original setup on the  server connected to VPN router

Thanks

embyserver.txt

[Luke 42079]

Here they are. These are from my original setup on the  server connected to VPN router

Thanks

 

That log looks fine. What was the problem? Can you try to play something using the web interface, then attach a new log? thanks.

[rbjtech 5284]

OK , as you say back to basics with this thing. I have now connected both server and clients to router 1 instead of the VPN router 2. Happliy Im getting somewhere and now the clients can see the library files which I continue to have on the NAS connected to router 2. All play OK so now I'm down to the business of fine tuning the look and feel of it.

Two problems immediately arise but probably for other forums. Neither Cover Art nor BlurN nor Trailers plugins appear to work even though it says I have 14 days trial??? Since this is the first time I've used Emby that is not very helpful to test ..

I must say I'm looking to move from Plex which has run fine until the latest changes and despite being a Pass holder I'd be willing to move to Emby if I could get it set up nicely, so far things are proving problematic but I am grateful for the help received thus far which is significanlty better than Plex offers.

 

ok - so this is now making more sense from a networking perspective.

 

Your router 1 and router 2 on the LAN side are by the looks of it on the same network - thus local (LAN) clients can connect to it fine and emby can get it's media via the router2/switch - and the firewall rule allows these incoming connections.  Scope = Local Subnet most likely, so all working. 

 

If you have a VPN setup on router 2 however, then remote users need to be NAT'd back to your local subnet to get through your Windows firewall and onto emby.

 

Before we get to that though - the next basic step is getting normal remote users working (ie non-vpn) - assuming you have the correct port forwarding working - then this should be NATing your WAN address to your LAN address.  Does this work ok ?  ie can you get to your emby server via a public IP address ?

Edited March 20, 2020 by rbjtech

[joolsclop 1]

ok - so this is now making more sense from a networking perspective.

 

Your router 1 and router 2 on the LAN side are by the looks of it on the same network - thus local (LAN) clients can connect to it fine and emby can get it's media via the router2/switch - and the firewall rule allows these incoming connections.  Scope = Local Subnet most likely, so all working. 

 

If you have a VPN setup on router 2 however, then remote users need to be NAT'd back to your local subnet to get through your Windows firewall and onto emby.

 

Before we get to that though - the next basic step is getting normal remote users working (ie non-vpn) - assuming you have the correct port forwarding working - then this should be NATing your WAN address to your LAN address.  Does this work ok ?  ie can you get to your emby server via a public IP address ?

Thanks for taking the time to look at this for me. I am pleased to say I've sorted this out and am able to connect both non-vpn and vpn traffic so that I can access the server both locally and remotely (thanks to DDNS).

[Luke 42079]

Thanks for the feedback !