UPNP setup of Emby Server has suddenly stopped working remotely

[Luke 43099]

3 minutes ago, Beta8088Proto said:

whether or not my ISP is using CGNat (I don't pay the bill in my household and I doubt the one who does would know what that even is)

It's probably something you should look at and determine because it is happening all the time. We go over how to do that here:

Connecting from Client Apps

Quote

I am using the link exactly as the server has given me

In some rare cases the server may detect the wrong remote address. It's not an exact science, so it's a good idea to know your router's public facing remote ip address.

[TaprootCI 0]

2 hours ago, Luke said:

It's probably something you should look at and determine because it is happening all the time. We go over how to do that here:

Connecting from Client Apps

In some rare cases the server may detect the wrong remote address. It's not an exact science, so it's a good idea to know your router's public facing remote ip address.

In order from that document (that I've done pretty much everything in that is practical for me to do) here's why it has not helped for over a year:
 

• In-Network Connections is fine and works correctly, so inapplicable.
• "Switch to a private network" (it is)
• "Turn on network discovery/file sharing" (it's on already)
• "Open TCP Ports 8096 / 8920 & UDP Port 7359 on your server's firewall" (I'm not running a firewall on my NAS, or my PC)
• "Run an AntiVirus Scan" (it's running on Terramaster OS 5, inapplicable)
• "Check "LAN Networks" server Network setting" (LAN works perfectly fine, so inapplicable)
• "Router AP Isolation" (inapplicable, all devices work on LAN, including over Wifi)
• "Use of VPN" (I don't use a VPN, inapplicable)
• "CORS Mixed Content Block" (I get the same WAN misbehaviour when I use http explicitly)
• "Turn on Remote Access" (it's always been on)
• "Enable Automatic Port Mapping" (it's been enabled this whole time)
• -UPnP Wizard, I just ran, and it thinks my server doesn't exist when accessing its local URL through LAN, so it wasn't able to do anything. Maybe that's an indication of something, but it's not helpful.
• "Setup Port Forwarding" (I've done this literally dozens of times over the past year and this has literally never once worked for me, no matter which tutorials I follow, or what ports I use)
• "Multiple Emby servers on the network" (inapplicable, I have one)
• "Double NAT" problem (funnily enough this wasn't a problem until last week, as I was able to connect using Emby Connect remotely, in spite of the downstairs network being in a double NAT situation, and it would ONLY work in said double NAT situation and refused to work unless I had the downstairs router in Router mode, with the upstairs router as its DHCP server)
• "Locate Your External Address & Public Port" (I have, it doesn't work directly connecting to what my server tells me, as previously stated, ad nauseum)
• "Verify Your External IP Address" (this I have never been able to get a positive result with, hence why I was using Emby Connect when it worked, and it worked despite, as you have previously stated, it shouldn't have)
• "VPN, external firewalls and antivirus" (inapplicable, Terramaster OS)
• "Local IP Address change" (I was using DHCP and, again, attempting to connect to the port and IP that Emby Server gave me)
• "cgNAT Double NAT" (there are no 100.x.x.x IP's in this house's network, only 10.0 and 192.168.1.x and as previously stated, double NAT wasn't a problem until about a week ago, and in fact, was the ONLY way remote connections would work at all, and ONLY through Emby Connect, NOT the direct address)
• "External Public IP Address change" (nothing I can do about this and I have tried setting up DDNS, and I have likewise never gotten this working, also, my public IPV4 is, in fact, what Emby Server says it is, and yet it still does not work)
• ISP Blocking (I have run the command and found no indication of an ISP block)
• "use Emby Connect" (what I'm trying to do and what suddenly broke)
• The other suggestions are largely inapplicable, but "clear the UPnP cache by restarting Emby" (I've done this at least six times with no improvement, I have even updated Emby Server).

The rest is just repetitions of previous steps, but rest assured, if these steps actually were of any use to me in the last year, I wouldn't be here, I would have fixed this problem a year ago.

[Luke 43099]

Quote

ONLY through Emby Connect, NOT the direct address

I think we need to learn more about this because the rule of thumb is get the direct address working first because Emby Connect is just a shortcut for that. If they are truly acting differently then it is likely because they are using different addresses, so we should get to the bottom of that. There's no magic involved here.

And if they are using the same address, then we need to look at what exactly is happening that's leading you to say "not working". For example, a user who can't login to their server might also describe it as "remote connection not working", when in fact they can connect, but just had trouble signing in after that.