Mazak15 1 Posted 3 hours ago Posted 3 hours ago I have Emby runnung on 192.168.30.35:9096 but on the dashboard it states that the server is available @ 172.16.1.2, I am not using the 172.16.1.1 subnet and I’m not allowed remote traffic to it. How or why would this be happening. I have also found in the log that the server friendly name is _secretl_ also something I didn’t setup or name. My media files are being tampered with. Can the 10.0.0.0/8 and 172.16.0.0/16 be blocked from emby?
Neminem 1538 Posted 1 hour ago Posted 1 hour ago Are you running it in docker? 172.16.1.0/24 is usually the host's internal docker network. 1
Mazak15 1 Posted 6 minutes ago Author Posted 6 minutes ago No. It runs on truenas scale. With the published subnet of 192.168.30.35:9096 this subnet is just for emby and the clients. (Two KODI boxes and one TV)
Neminem 1538 Posted 3 minutes ago Posted 3 minutes ago (edited) I have no ide how truenas does this. But I would ask in the Truenas section. Edited 1 minute ago by Neminem
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now