Jump to content

Emby server treats local ipv4 connection as "remote connection"


Darkseidd
Go to solution Solved by Happy2Play,

Recommended Posts

Darkseidd

hi,

I run my Emby server on Docker, on OMV5 Raspberry Pi 4B. I have both ipv4 and ipv6 running at my internal network.

 

When I connect using ipv4:8096, it didn't show my admin account.

but when I am connecting via [IPv6]:8096, it shows my admin account.

 

is there anyway to define known local subnets inside Emby server?

 

Link to comment
Share on other sites

Hello Darkseidd,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

Link to comment
Share on other sites

  • Solution
Happy2Play

Have you ever logged with ipv4?  As all client/connections that have never been logged in via that method will not show user and require a manual login.

Can you post a server log but yes you can define this on Dashboard-Network, LAN Networks. 

Link to comment
Share on other sites

Darkseidd
3 hours ago, Happy2Play said:

Have you ever logged with ipv4?  As all client/connections that have never been logged in via that method will not show user and require a manual login.

Can you post a server log but yes you can define this on Dashboard-Network, LAN Networks. 

thanks! now connection from ipv4 considered local after defining the subnet.

 

do you still need the log though?

  • Like 1
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...