Jump to content

Refuses to connect FreeNAS plugin


NinthWave
Go to solution Solved by MRobi,

Recommended Posts

NinthWave
On 1/14/2021 at 8:25 PM, MRobi said:

This is for updating manually.

A fresh install is similar, check out these instructions for the beta. You can change the release link for any version on the github page.

https://emby.media/freebsd-server.html

This is assuming you know how to create a jail in FreeNAS, you can do this easily with the GUI. Everything else is in shell.

 

The plugin way went through but I could not access the GUI.

I deleted everything and did this manual install.  Still no GUI.

Firefox says it's not available while Edge says "connection refused".

Is it just me?  Where to start ?

@Happy2Play please move my posting to a new topic. thanks.

Link to comment
Share on other sites

11 hours ago, NinthWave said:

The plugin way went through but I could not access the GUI.

I deleted everything and did this manual install.  Still no GUI.

Firefox says it's not available while Edge says "connection refused".

Is it just me?  Where to start ?

@Happy2Play please move my posting to a new topic. thanks.

Are you browsing to http://IPADDRESS:8096? Have you started the emby service and is it for sure running in the jail?

Link to comment
Share on other sites

NinthWave
1 hour ago, MRobi said:

Are you browsing to http://IPADDRESS:8096? Have you started the emby service and is it for sure running in the jail?

image.png.12067bbe6433a384a8697caf3e0a0f13.png

Link to comment
Share on other sites

NinthWave
9 minutes ago, MRobi said:

And you're navigating to the right ip with port?

Yes,
As mentioned in OP, I setup everything right in VM on an M3 server.

Now that I am on production on a PowerEdge in baremetal, it is not working.  Strange.

 

Link to comment
Share on other sites

Happy2Play
17 hours ago, NinthWave said:

Firefox says it's not available while Edge says "connection refused".

Is everything in the same subnet/network?  Connection Refused usually means rejected remote connection.

@NinthWave split to new topic, please follow this one.

Link to comment
Share on other sites

NinthWave
4 hours ago, Luke said:

@NinthWave are you still having an issue with this?

@MRobi may have some tips.

Yes, I still have the problem.  Neither the NAT plugin nor the manual way allowed me to access the GUI with IP:port so I resolved to install the other plugin (DHCP) which created a new IP address.

But I am not far in the process and I would prefer the NAT problem to be solved than having another IP address.

Link to comment
Share on other sites

NinthWave
On 2/20/2021 at 2:54 PM, Happy2Play said:

Is everything in the same subnet/network?  Connection Refused usually means rejected remote connection.

@NinthWave split to new topic, please follow this one.

Sorry, follow which one?  There is no link to another topic.

Link to comment
Share on other sites

Happy2Play

@NinthWave Do you have "Allow remote connections" enabled? Dashboard-Network, there is a per user setting also.  If you enable this and connections work, this means Emby does not know your LAN networks.

It sounds like you need to identify your LAN networks via Dashboard-Network to let the server know your LAN networks.

2 hours ago, NinthWave said:

Sorry, follow which one?  There is no link to another topic.

Same as other topic, click follow on this new topic.

Link to comment
Share on other sites

  • Solution
On 21/02/2021 at 19:40, NinthWave said:

Yes, I still have the problem.  Neither the NAT plugin nor the manual way allowed me to access the GUI with IP:port so I resolved to install the other plugin (DHCP) which created a new IP address.

But I am not far in the process and I would prefer the NAT problem to be solved than having another IP address.

If DHCP works then the issue is in your network configuration. I've never configured NAT, saw no use for it. I do know you need BPF off and that you need to manually configure the port forwarding options in the jail when you create it. I simply assign a static ip when creating the jail and put them in order. 192.X.X.100, 192.X.X.101, 192.X.X.102.....

Link to comment
Share on other sites

NinthWave
8 hours ago, MRobi said:

If DHCP works then the issue is in your network configuration. I've never configured NAT, saw no use for it. I do know you need BPF off and that you need to manually configure the port forwarding options in the jail when you create it. I simply assign a static ip when creating the jail and put them in order. 192.X.X.100, 192.X.X.101, 192.X.X.102.....

Well, I have made some progress in the setup so I won't bother reverting to NAT.

Edited by NinthWave
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...