Jump to content

force IPV4?


Go to solution Solved by Luke,

Recommended Posts

JasonNalley
Posted

Hello good people.  I just noticed that my WAN side IP switched from the IPV4 address to the IPV6 address and I have no idea how to fix/correct that.  several users are reporting problems connecting now that this has changed.  Is there a way to force it back to the normal IPV4 address?

Happy2Play
Posted

@pir8radioyou have mentions you have no issue with IPv6, did you do anything special?

Posted

Hi, you should be able to either disable IP6 or better set IP4 to be preferred.
If you're on Windows this is pretty easy to change.
 

pir8radio
Posted
11 hours ago, Happy2Play said:

@pir8radioyou have mentions you have no issue with IPv6, did you do anything special?

no issues,  IPv6 and 4 work well with emby..   the issue use if one end doesnt support it..     If he is bound to the IPv6 address only then his emby server will ignore ipv4 requests.  if he is bound to ipv4 then emby will ignore ipv6     he needs to bind to all or do something like nginx reverse proxy, talk only ipv4 to emby let nginx handle the connections.  

I don't think emby binds to a particular nic or ip any longer right?  so I'm not sure why he is seeing this..  possibly UPNP opening the port for only one ip version?   Maybe manually open the firewall for both ip's  v4 and v6?      check os firewall too,  v4 and v6.    or do like cayars said and force ipv4 if you don't know how or want to deal with it. 

IPv6 is coming, some ISP's are forcing it and not even assigning ipv4 addresses any longer.   

pwhodges
Posted

Quite likely port forwarding in the router has been defined only for the IPv4 address; it may require a separate entry for the IPv6.  The way it works in mine (a Draytek Vigor) is that I define a name for the machine (within the router's own tables, that is) and associate it with both addresses; then I just use that name in the forwarding rules.

Paul

  • Agree 1
Posted
22 hours ago, Happy2Play said:

you have mentions you have no issue with IPv6

I wish I knew what this means.  He didn't say he didn't have an issue with IPv6.

About reverting back to IPv4, I'd think you need to ask your ISP about that, since it controls your address.

Happy2Play
Posted

 

11 hours ago, pir8radio said:

no issues,  IPv6 and 4 work well with emby

 

 

3 minutes ago, justinrh said:

He didn't say he didn't have an issue with IPv6.

Sorry I don't follow as that is what he said.  But in the end yes if ISP's are changing then just Updates many need to happen but Emby should already be reading your WAN address whether ipv4 or v6.  Now it is a matter of your hardware using the address and forwarding to correct interna LAN address.  So you many have to check your router and your firewall for issues.

  • Agree 1
JasonNalley
Posted
On 11/11/2021 at 7:05 AM, pir8radio said:

no issues,  IPv6 and 4 work well with emby..   the issue use if one end doesnt support it..     If he is bound to the IPv6 address only then his emby server will ignore ipv4 requests.  if he is bound to ipv4 then emby will ignore ipv6     he needs to bind to all or do something like nginx reverse proxy, talk only ipv4 to emby let nginx handle the connections.  

I don't think emby binds to a particular nic or ip any longer right?  so I'm not sure why he is seeing this..  possibly UPNP opening the port for only one ip version?   Maybe manually open the firewall for both ip's  v4 and v6?      check os firewall too,  v4 and v6.    or do like cayars said and force ipv4 if you don't know how or want to deal with it. 

IPv6 is coming, some ISP's are forcing it and not even assigning ipv4 addresses any longer.   

So, my ISP has had IPV6 enabled for quite some time, I use it for other things.  Emby has always displayed an IPV4 address in the WAN address slot, until this happened the other day.  All of my users connect via Emby Connect, which I'm guessing is some sort of bounce protocol.

How I *think* it works (feel free to correct me):
Server opens up, gets various network information from NIC/Network interface
Server broadcasts the WAN address to Emby connect service
Emby connect service uses this information to direct traffic once signed in.

If the above is correct, then all users (regardless if IPV6 enabled on their router/computer/isp or not) get sent to an IPV6 address, which for some of them may not be possible.  

Personally, I can connect from outside of my network using my IPV4 or IPV6 address directly, but it seems others cannot (leads me to believe something in their chain doesn't play well with IPV6).  Because I can connect using either, I don't think it's a port forwarding issue.

I have temporarily solved the problem by using DuckDNS and inputting the domain into the external domain section of network settings.  Everyone can connect again.  But this method is sort of a band-aid/stop gap.  I'm wondering if it may be a better solution for Emby Connect to utilize both IPV4 and IPV6 addresses simultaneously?  I dunno how that would work though.

Posted

Went through this same BS, figured out the solution for me, Once I found the IPV6 shut off in my Router I just disabled it, restarted my Server and it put my WAN back to IPV4 and all my remotes were happy campers, only thing was most had to to a manual connect due to a new Host IP,  So it wouldn't let them back in to their usual Accnt. Which isn't that big of a deal considering not getting in at all. Hope this helps

  • Like 1
  • Solution
Posted

Regarding ipv4/ipv6, please see my comments here:

Thanks.

JasonNalley
Posted
1 hour ago, Luke said:

Regarding ipv4/ipv6, please see my comments here:

Thanks.

Thanks Luke, that fixed it.

ThePaladinTech
Posted

When should we expect 4.6.5? none of my families servers are showing 4.6.5 yet. (is there a way to force the update??)  My Moms emby server decided to use the ipv6 so for now I disabled ipv6 on her server and it's working. Mine and my brothers seem to be working ok. All are on 4.6.4.  Is this a change that the ISP did? we are all on different ISPs.. 

Thanks

Posted

Just to be clear, you're not blocked in any way because you can always specify your remote address manually in emby server network settings. So if 4.6.5 isn't up for your platform yet, or you need immediate resolution, you can always do that.

Once you do have 4.6.5, then you'll be able to undo that and carry on like you were before. Please let us know if this helps. Thanks.

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