All Remote Connections no longer working

[iamjarbear 5]

Hey everyone,

My Server has been up for about a month now with around 20 different devices connected. Of those devices 4 are in home and pointing to the Local IP. The others are my family/friends I share with. They all Connected initially without issue and have been using it this whole time. As of today, I ended up hardwiring the server instead of it just being on WI-FI which changed the In-Home IP. That made me have to reconnect to the server on my home devices. I did so and it works without issue. However, every other device can no longer connect to the Server. The Remote IP never changed only the Local. Using either the Local or Remote IP, the remote users still cannot connect. I took out the Ethernet and switched it back to how it was prior. In doing so the IP switched back to what it was initially. However, nobody is still able to connect except for me locally. I already had them Sign out and In, Forget the server and reenter the IPs but no luck.

Main Points

1. Hardwired my server and it kicked everyone off
2. Remote Users cannot connect to server but locally I can
3. I reverted the changes I made to make it back to normal, but it still remains no one can connect.
4. Remote Users have Signed out/in. Deleted/Re-Added the server manually both to the In-home/remote IP (On Wi-Fi and while hardwired)

Any insights? I'm going crazy trying to figure out how to fix this.

Thanks,

Jared

[darkassassin07 590]

As you changed from wifi to ethernet, your server has a different LAN IP .

 

Your port forwarding rules (router settings) need to be updated to send traffic to the new LAN IP .

 

You should also look at setting a fixed LAN IP for your server, to prevent it being assigned a different one after a power outage. Either via static dhcp lease settings (router), or through your network interface settings (server).

Missing that step is likely why switching back to wifi didn't fix it.

Edited June 13, 2024 by darkassassin07

[iamjarbear 5]

2 hours ago, darkassassin07 said:

As you changed from wifi to ethernet, your server has a different LAN IP .

 

Your port forwarding rules (router settings) need to be updated to send traffic to the new LAN IP .

 

You should also look at setting a fixed LAN IP for your server, to prevent it being assigned a different one after a power outage. Either via static dhcp lease settings (router), or through your network interface settings (server).

Missing that step is likely why switching back to wifi didn't fix it.

I went through the settings on my router in my spectrum app as well as followed the How-to for Port Forwarding (Emby.Docs/Remote-Setup.md at master · EmbySupport/Emby.Docs · GitHub) and it still does not appear to be working. See below screenshot from my Router settings. Does that look correct? I also added a couple other screenshots. Im not sure what I am doing wrong as I feel like I am doing what I am supposed to.

 

 

 

 

Edited June 13, 2024 by GrimReaper
WAN IP masked

[darkassassin07 590]

As a mac address is specified, make sure it is correct. Your server will have a different one for ethernet vs the one it had for wifi.

 

You can usually find a list of connected mac addresses and their assigned IP addresses somewhere in the routers status pages.

[Happy2Play 9300]

As mentioned above this has to be a port forwarding issue as you can connect locally it should eliminate firewall issues.

@GrimReapercan you remove the WAN address above.

 

 

[iamjarbear 5]

1 hour ago, darkassassin07 said:

As a mac address is specified, make sure it is correct. Your server will have a different one for ethernet vs the one it had for wifi.

 

You can usually find a list of connected mac addresses and their assigned IP addresses somewhere in the routers status pages.

So it appears the Mac address does seem to match. Something else I noticed though, when i use Whatsmyip. Whatsmyip provides me with the IPV4 as the Remote WAN Ip (76.184...) whereas checking under my IPConfig through cmd prompt matches the In-Home Lan (192.168...)

Edited June 13, 2024 by GrimReaper
WAN IP masked

[iamjarbear 5]

1 hour ago, Happy2Play said:

As mentioned above this has to be a port forwarding issue as you can connect locally it should eliminate firewall issues.

@GrimReapercan you remove the WAN address above.

 

 

Something updated but idk why it changed the LAN access. Im even more confused now  

Edited June 13, 2024 by GrimReaper
WAN IP masked

[Happy2Play 9300]

Your router appears to have assigned a IPv6 address.  Personally I just disable it on my LAN.

[darkassassin07 590]

Odd, I don't usually see ipv6 on a lan...

 

I agree with Happy, just disable ipv6 support on the lan.

Restart the server machine and router after that change; then go back to the port forwarding setup.

[iamjarbear 5]

9 minutes ago, Happy2Play said:

Your router appears to have assigned a IPv6 address.  Personally I just disable it on my LAN.

 

1 minute ago, darkassassin07 said:

Odd, I don't usually see ipv6 on a lan...

 

I agree with Happy, just disable ipv6 support on the lan.

Restart the server machine and router after that change; then go back to the port forwarding setup.

So I disabled it using the followingand now my LAN shows blank and I cant connect at all. 

• Enter Settings > Network & Internet > Change adapter options
• Right-click the interface and select Properties
• Uncheck "Internet Protocol Version 6 (TCP/IPv6)"
• Click OK.

[darkassassin07 590]

That's disabling ipv6 on the network card of the server.

You're looking to disable it on the router itself, so that the router only hands out ipv4 addresses to lan devices (192.168....).

Be sure to restart the server machine and router after those changes.

[iamjarbear 5]

26 minutes ago, darkassassin07 said:

That's disabling ipv6 on the network card of the server.

You're looking to disable it on the router itself, so that the router only hands out ipv4 addresses to lan devices (192.168....).

Be sure to restart the server machine and router after those changes.

So since I have a Spectrum router, I apparently am not able to disable IPV6 (Yes I know I need a my own). Do you know of a way to do this without that? It worked fine for a month without any of this and I just happened to hardwire it today on a whim and now its broken entirely. There's gotta be a setting somewhere.

[rbjtech 4883]

If you did not do any manual port forwarding before (when it was on wifi) - then this implies you were using upnp to do the port forwarding.   This is also shown in the 'Enable Port Mapping' in the emby network configuration.

I would suggest removing any manually created port forwarding rules in the router (related to emby), then do a full power off and on again.    Ensure upnp is enabled in the router itself - it 'may' have turned this off if you manually added a rule.   Then power off/on your emby server - and check it has a v4 IP address - likely 192.168.1.80.   But check on the server, or the router IPv4 DHCP tables.

Check you can use emby locally.   It should have both an 'In-Home' and 'remote' ip/url - if it does, then upnp has done it's thing and automatically port forwarded your WAN IP to the new wired LAN IP.    Emby instructs it to do this.

Edited June 13, 2024 by rbjtech

[visproduction 238]

Spectrum routers apparently require you to make setting adjustments through an app and not directly to the router.  If you owned your own router, you would have a dashboard access.

To do it with the Spectrum router look here for details:
 https://www.wikihow.com/Port-Forward-on-Spectrum

More search results:
 https://duckduckgo.com/?q=spectrum+router+port+forwarding+setup&ia=web

Hope that helps.

[iamjarbear 5]

7 hours ago, rbjtech said:

If you did not do any manual port forwarding before (when it was on wifi) - then this implies you were using upnp to do the port forwarding.   This is also shown in the 'Enable Port Mapping' in the emby network configuration.

I would suggest removing any manually created port forwarding rules in the router (related to emby), then do a full power off and on again.    Ensure upnp is enabled in the router itself - it 'may' have turned this off if you manually added a rule.   Then power off/on your emby server - and check it has a v4 IP address - likely 192.168.1.80.   But check on the server, or the router IPv4 DHCP tables.

Check you can use emby locally.   It should have both an 'In-Home' and 'remote' ip/url - if it does, then upnp has done it's thing and automatically port forwarded your WAN IP to the new wired LAN IP.    Emby instructs it to do this.

So, Im not sure why now as I power cycled everything multiple times originally but after turning off the port forwarding rule in the Spectrum settings and doing another system reset this morning, it appears to be solved. I was using the Port Mapper in the Network settings with Auto port turned on and it had worked without me needing to do anything. Probably just a combination of things.

 

Thanks everyone for the assistance. I'm not sure who to assign as the Solution here to be honest but thank you all fo rthe help, I appreciate it.

[rbjtech 4883]

2 minutes ago, iamjarbear said:

So, Im not sure why now as I power cycled everything multiple times originally but after turning off the port forwarding rule in the Spectrum settings and doing another system reset this morning, it appears to be solved. I was using the Port Mapper in the Network settings with Auto port turned on and it had worked without me needing to do anything. Probably just a combination of things.

 

Thanks everyone for the assistance. I'm not sure who to assign as the Solution here to be honest but thank you all fo rthe help, I appreciate it.

The manual port forward rule may not have been correct - and by enabling it - it may have disabled upnp.    So by removing it and rebooting, I believe, as you say, it went back to how it was originally.   Sometimes routers hold onto upnp 'rules' after a reboot to keep you moving after a power outage for example - so it could be a 'time' thing.     

[iamjarbear 5]

18 minutes ago, rbjtech said:

The manual port forward rule may not have been correct - and by enabling it - it may have disabled upnp.    So by removing it and rebooting, I believe, as you say, it went back to how it was originally.   Sometimes routers hold onto upnp 'rules' after a reboot to keep you moving after a power outage for example - so it could be a 'time' thing.     

So I may have spoke to soon. While I was able to connect using no WiFi and my admin login (I assume due to Emby Connect) trying to connect on a different network/Device to the remote stuff is still not functioning. Everything's back to how it exactly was before, both the wan/lan are now appearing to be correct.  

Any additional insights/thoughts as if we're starting over from the beginning. I got my IPs bank to normal but now we're still not getting remote connection.

[Happy2Play 9300]

8 minutes ago, iamjarbear said:

So I may have spoke to soon. While I was able to connect using no WiFi and my admin login (I assume due to Emby Connect) trying to connect on a different network/Device to the remote stuff is still not functioning. Everything's back to how it exactly was before, both the wan/lan are now appearing to be correct.  

Any additional insights/thoughts as if we're starting over from the beginning. I got my IPs bank to normal but now we're still not getting remote connection.

Sorry I don't follow as your posted WAN address is accessible from the internet.  So I can only guess clients are not trying to access the correct address?

[iamjarbear 5]

Just now, Happy2Play said:

Sorry I don't follow as your posted WAN address is accessible from the internet.  So I can only guess clients are not trying to access the correct address?

I can't even access it remotely. I turned off Wi-Fi and try to connect and it says unable to reach server. Along with my brother who keeps getting the same error or booted back to the login screen. When I throw the WAN IP into a browser it pulls up but trying to point to it in the app appears to be an issue. Is it possible that the logins are 'broke' because of all the stuff I did. I had him forget the original server and readd it but it fails. Is there a way inside EMBY (logs or somewhere) where I can like see what the reason is for the Faile Login?

 

 

 

[rbjtech 4883]

Looks fine to me ..

Edited June 13, 2024 by rbjtech

[rbjtech 4883]

4 minutes ago, iamjarbear said:

 Is there a way inside EMBY (logs or somewhere) where I can like see what the reason is for the Faile Login?

The fact you have failed login attempts, says the 'connection' is good.   But for some reason, the Authentication is failing - wrong password perhaps ?

Maybe set a very basic password just to test - but don't forget to put it back when you are done testing..

[Happy2Play 9300]

Login failure provide you server is WAN accessible.  Now figuring out why username/password is broke is another story.  As I get your login page just like rbjtech posted.

I know there is a loopback issue on these garbage spectrum router as you cannot connect to WAN address inside your network.  Have not looked through the settings though.

[iamjarbear 5]

6 minutes ago, rbjtech said:

The fact you have failed login attempts, says the 'connection' is good.   But for some reason, the Authentication is failing - wrong password perhaps ?

Maybe set a very basic password just to test - but don't forget to put it back when you are done testing..

 

5 minutes ago, Happy2Play said:

Login failure provide you server is WAN accessible.  Now figuring out why username/password is broke is another story.  As I get your login page just like rbjtech posted.

I know there is a loopback issue on these garbage spectrum router as you cannot connect to WAN address inside your network.  Have not looked through the settings though.

I think I got it figured out. Its not Invalid passwords or antyhing. Looking into the User Settings all the EMAILS for each user under Emby Connect were cleared out and now theres nothing. So its like their logins are there but not there. Im going to attempt readding those emails so they can try signing into the app again. It does work by plugging directly into it like you guys are seeing on the web.

 

*Edit - not all user accounts were reset only 3 of the 8 users. The 3 users that have been attempting. Weird, but after relinking the email it allows for the connection again it appears.

Edited June 13, 2024 by iamjarbear

[Luke 39352]

Hi, they may have deleted the server from their account on the server selection screen, that’s the most likely reason for that to happen.

[iamjarbear 5]

2 hours ago, Luke said:

Hi, they may have deleted the server from their account on the server selection screen, that’s the most likely reason for that to happen.

Ya that's exactly what it was. I did not know deleting the server from the account would delink their email addresses. I had them delete it to reconnect while we were troubleshooting it earlier. Makes sense.