IP address inside of app

Apps and Virtualization
1

I apologize if this is covered somewhere else, I could not find anything that specifically fit my case.

The specific app is Emby, however I do not believe this is a specific app problem, but a system quark that I do not know how to work around.

Network 192.168.10.0/24
TrueNAS 192.168.10.16
Emby: 192.168.10.16:9096
Inside Emby server it says the server is on http://172.16.0.240:8096/

Everything works perfectly, very happy with the performance and transcoding even though I was never able to get a video card to work in the TrueNAS server. When accessing 192.168.10.16:9096 TrueNAS clearly directs me to the Emby server inside the app and I have no problems on any device.

Problem:
I have recently tried to add Live TV (thanks Olympics). It worked before when Emby was on a machine by itself. HDHomeRun works perfectly within its own app. My assumption is the Emby server thinks it is on 172.16.0.xxx and will only talk to the HDHomeRun on that LAN. The fact that the HDHomeRun box is on 192.168.10.100 I believe is why they wont talk to each other.

Attempts:

  1. I first started by adding local LAN networks inside the Emby server to include 192.168.10.0/24 as local server. This made Emby server not boot at all. (As I am writing this I see there is an override local IP, I will try that tonight maybe I can get it to accept a free 192 address. I am over VPN and can’t risk wife anger if I crash it from here)

  2. I logged into pfsense and made a new virtual network with 172.16.0.0/24. Then in the DHCP Server I assigned the HDHomeRun device to 172.16.0.100. and Bridged the 172 network with the 192 network. This did not fix anything. I then reassigned my computer to the 172 network as well. I could log into the HDHomeRun gui, but the http://172.16.0.240:8096/ did not log me into the Emby server. (I would have thought that since the networks were bridged that I could access 172. from the 192. network, however I could not, possible I did not set up the bridge properly) (That network has been removed)

Help:
If anyone could share some help on this problem, or point me in the right direction on to what even to search for. It could be any number of problems, but if I were a betting man, I think the problem is because the server inside the app thinks it is on 172 and TrueNAS is port forwarding 192 to the app. Short of going back to a stand alone server, how do I fix this? I don’t believe this is an Emby problem and posting on that forum I believe would be a waste of time.

1 Like
2

Hdhomerun works fine with Emby on Scale. Use it daily, probably 6-10 recordings a day for a few years now. Emby will easily talk to hdhomerun on your 192.168.10.0 network, not an issue. That’s handled by Scale, there is no issue there. So, you need to have premiere set up and you need to add the hdhomerun to the Settings → Live TV screen. I have 2 linked in. Then you have to add a guide source. And it of course requires Emby Premiere license to be loaded. Do not mess around with the network settings, it is not necessary. This is true of virtually any app, I have 24 of them. I would suggest undoing all that stuff you did.

On the Emby forums is in fact a Truenas thread. You can post there also if you want.

1 Like