Jump to content

Can't connect to server


Recommended Posts

Posted

Hello, I just installed the Emby server and it is running fine, according to the Dashboard. I am unable to access the server via either my roku boxes or just another computer on the same local network. I've added the inbound rule for port 8096, my computer is clean per a scan I just ran, no other issues, no other firewalls running. I've even checked the Emby forum and found some lengthy articles discussing the same problem. In the case of the longest thread, the user simply gave up and went to Plex.

 

I'm a pretty good troubleshooter and fairly technically savey. I've tried on two occaisions to get Emby to work, spending many hours with no success. Can somebody walk me through what has to be done? Plex wrecked their roku app, but at least they never made you jump through the sort of connection hoops that Emby seems to require.

 

Oh, I also tried using Emby Connect, with no success.

Posted

The connectivity manual didn't help (I already followed that) but I ended up fooling around with the inbound rules and was able to get it to work. First, I found that one of the automatically created rules from the software install were not enabled. Then I guessed and tried creating separate inbound rules for port access for both UDP and TCP. That seemed to let it work.

 

It would be infinitely more helpful if your install instructions stated this explicitly and/or have an install video to assist. No where did I find any exact instructions, nor screen shots of what a properly configured set of inbound rules looks like. Seems like you're depending on your user base to all be IT experts.

 

I love the operation of the server and how the roku channel works, but I think if you made the install easier for non-experts you'd tremendously widen your user base.

Posted

Hi.  We try to do this automatically wherever possible but the problem is there is not just one "correct" configuration.  Exactly how it needs to be configured depends on the exact implementation environment.  There are lots of different firewalls and other security software out there.

 

Perhaps an example screen shot of what the standard Windows Firewall rules should look like would be helpful though.

 

Thanks.

Posted

I think so, and maybe even some screenshots of inbound rule examples. Just a bit more detail would help alot, especially for those that have never delved into such things. Take me for example, I have a ton of troubleshooting experience, a fair coder, but without having ever done anything with a firewall and porting, I just sort of had to guess at things. Ends up being really frustrating. If you had some examples, that would at least give the intrepid sort a fighting chance, a place to start.

 

In the end, it's all good, and I will say again this software so far seems to be orders of magnitude better than anything else available. It's like Plex is trying their best to commit suicide, and succeeding!

 

Thanks for the Sunday reply, no rest for the wicked :)

Posted

I am having this same problem. @@coolmoss77 would you be able to provide screenshots of the rules you applied and any steps you took to get it to work, please? For the most part it seems this isn't happening to everyone using Emby but the small few that it is happening too, are struggling with a solution. At the moment, you seem to be the first person with  a resolve. I did all the troubleshooting steps you mentioned in your initial post with no success, i've also troubleshooted many things and am relatively tech savvy but can't figure this one out. Hoping you'll be able to post a tutorial of how you succeeding it get Emby to work for you. I know all of us who are searching for a solution would appreciate it very much. 

Happy2Play
Posted

What firewall rules do you currently have?

 

You could try shutting down Emby and deleting the current firewall rules, then start Emby.  This will regenerate the firewall rules.

Posted

Deezy,

 

Let me try describing what I did, and if you still need a screen shot, please ask again. I'm a bit harried at the moment with some things so need to save some time.

 

First, to be honest, I was trying all sorts of things and can't recall exactly for sure which step resolved it. Perhaps all of it is needed. First, what I did is create a single rule (per the connectivity guide where there is a link to the instructions for creating a rule). No where did it say specifically to create two rules (one for TCP and one for UDP) but that's what I ended up doing. If you look at the inbound rules list, I noticed that the rules that Emby automatically setup came in pairs, so I did the same.

 

At that point it still didn't work. This is where I get a bit foggy, but what I think happened, is I examined the enabled column in the inbound rules list and found one of the automatically setup rules not enabled. I had also checked the properties for each rule.

 

That's about all I have time for now. Let me know if you still need screen shots and I'll do it later. Each rule has a few tabs, and there are 10 emby related rules in the list, so that's a lot of screen shots and I'm not sure which ones you'd really need.

 

Good luck!

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