Jump to content

Issues with connecting remotely | Truenas Scale, emby 4.8.0.0


Go to solution Solved by Luke,

Recommended Posts

Bottomnotc
Posted

Hello all

I have recently been having issues connecting remotely to my Emby instance ever since upgrading from Truenas CORE to Truenas Scale.

I initially set up Emby through the built in apps (4.8.0.0_1.0.3) and was able to set up hosts paths to see media quite easily, no issues there.

 

The issue I have been struggling with the past few days is being able to access this server remotely.
I am able to access the server correctly on LAN through the address http://192.168.0.197:9096

I have gone through the support articles for Connectivity and Remote Setup and have still had no luck.

 

Through my router, I have ports 8096, 8920 forwarded through 192.168.0.197 TCP

I've checked Can you see me port 8096 when Emby is running, no success

firefox_w73gjs3e7b.png.dc7e57a8c8eda1c3c3657cada6d8bcb7.png

I do however find it interesting it says Connection refused instead of Connection timed out, that could possibly have something to do with it.

I'm almost certain my ISP isn't using CG-NAT, as I'm able to port forward other services fine, and when running tracert (my external IP) there is only 1 hop

 

ip addr inside pod:

Spoiler

firefox_1y1FPpzKDT.png.9bb15c17e9b70729132fa89215fc50f2.png

docker images:

Spoiler

firefox_B03KyC8Yzv.png.ab75ec4d1544c6e489b918c9280c1073.png

docker ps:

 

Spoiler

firefox_cmYQWPYNnV.thumb.png.0d4115907175f665f996a00568f09886.png

docker network ls:

Spoiler

firefox_EENvFIMugt.png.26b89d8f2b4fa3a95a833e6603813bec.png

ports forwarded on router:

Spoiler

firefox_2hqMugVSh9.png.762c7f3f900404490ecccb1ac44b2628.png

firewall on router:

Spoiler

firefox_9AwitUNxW0.png.c4a015efb0e1575fea3c2e4bd875de43.png

container application events:

2022-05-27 11:42:25
Started container emby
2022-05-27 11:42:24
Created container emby
2022-05-27 11:42:21
Container image "emby/embyserver:4.8.0.0" already present on machine
2022-05-27 11:42:21
Add eth0 [172.16.0.42/16] from ix-net
Successfully assigned ix-emby/emby-595bc56cc8-qv9mj to ix-truenas
2022-05-27 11:42:17
Created pod: emby-595bc56cc8-qv9mj
2022-05-27 11:42:17
Scaled up replica set emby-595bc56cc8 to 1
2022-05-27 11:34:38
Stopping container emby
2022-05-27 11:34:38
Deleted pod: emby-595bc56cc8-fkrvp

Also, allow remote connections to this Emby server is also checked.

If anybody has additional steps I can take to help troubleshoot, or possibly something that I'm overlooking; any information is very much appreciated!

Posted

Hi, does anything show up in the emby server log about the incoming connection?

I guess the first step is to figure out how far it's getting before being blocked.

Bottomnotc
Posted (edited)

It doesn't appear like a remote connection is appearing, I can see 192.168.0.102 (my pc accessing the interface at port 9092) but no other connection.

While debug logging was enabled, I restarted the Emby server, tried connecting to the external address on my phone (wifi off, cellular on) and tried to do an open port check on Canyouseeme

Attached is the embyserver log file

embyserver debug enabled.txt

 

Thank you for your prompt response!

Edited by Bottomnotc
typo
  • Solution
Posted

Ok it's actually port 9096 in the log but look at your router port forwarding.

  • Thanks 1
Bottomnotc
Posted (edited)

Alright, I forwarded 9096, connecting remotely seems to be fixed now!

 

In the Emby networking settings, I left the ports as 8096 and 8920.

firefox_NsQHRcdWRj.png.b60dc14ea9de7b8d7d85480b7d4e470c.png

 

firefox_3UmkZAVO6o.png.aab9f9e130ac108d4dc4a274c313742f.png

Port 9096 is the default port when creating the Emby application through Truenas (and can't be changed to anything < 9000)

 

----

I plan on configuring a reverse proxy +domain name and pointing it at this server, is there any changes you suggest I make before I proceed?

Thanks for your help thus far Luke

Edited by Bottomnotc
Posted

Thanks for the feedback.

For the reverse proxy I'd probably suggest checking out this: 

 

Bottomnotc
Posted

Thanks for that recommendation!

Got everything set up and working correctly, I appreciate you helping with my issue

 

Cheers!

  • Thanks 1
  • 1 month later...
Posted (edited)

@Bottomnotc

Hey m8, can you elaborate a few , how you solve it? I have certificate in emby, port is open.

on the dashboard my emby have the same port 9096 for http and http again for my domain , so duno what i am doing wrong.

on the kubernetes, i dont see either an https setting exposed. 

Thanks!

Edited by dgrigo

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