New update broke remote use for me?

[Boodikii 5]

Server was working fine, had 2 remote streams going at the time I updated and restarted the server.

Upon restarting I can no longer connect remotely on any platform.

I tried to change that new option that was added but neither of the two options did anything.

Only changing variable was the server update, everything should just be how it's always been otherwise.

Unsure on how to proceed from here Help would be appreciated, please and thank you

embyserver.txt

[Luke 39684]

Hi there, what exactly happens when you try to connect?

[Boodikii 5]

Just now, Luke said:

Hi there, what exactly happens when you try to connect?

So it just gives me a loading circle and then a popup that says "We're unable to connect to the selected server right now. Please ensure it is running and try again."

But it is running. When it restarted I started watching something completely fine afterwards through a local connection and didn't even know it was down until I was notified by somebody else.

[Luke 39684]

Have you setup remote access for your server?

Connecting from Client Apps

[Boodikii 5]

10 minutes ago, Luke said:

Have you setup remote access for your server?

Connecting from Client Apps

Absolutely. I have a couple remote users who use this regularly, they were using it up until I updated it and I use this as my music player when I deliver for work. Everything worked perfectly fine up until the 4.9.0.43 update. It's still set up exactly how it was. Remote option is checked, ports are open correctly, Domain and SSL are up to date. I haven't altered any settings from when it was working, aside from applying the update.

Edited April 1 by Boodikii

[Luke 39684]

OK can you test it yourself?

[Boodikii 5]

31 minutes ago, Luke said:

OK can you test it yourself?

I've been trying to connect via mobile network remotely since I was notified by a user.

 

[Luke 39684]

11 minutes ago, Boodikii said:

I've been trying to connect via mobile network remotely since I was notified by a user.

 

How exactly are you trying that?

[Boodikii 5]

1 minute ago, Luke said:

How exactly are you trying that?

The way I would normally connect remotely? By going into the emby app and clicking on my server. Normally it would just take me into my server upon launching the app but I'm getting the "unable to reach Jesi's emby" error. If I connect to my wifi, it boots up like normal.

[Luke 39684]

OK. I would suggest checking out our Connection Troubleshooter:

Connecting from Client Apps

Please try the steps listed there and let us know exactly which ones succeed and which ones do not .Thanks !

[Boodikii 5]

19 minutes ago, Luke said:

OK. I would suggest checking out our Connection Troubleshooter:

Connecting from Client Apps

Please try the steps listed there and let us know exactly which ones succeed and which ones do not .Thanks !

Well, from what I can tell, none of this applies.

I'm not using a VPN, 

Firewalls and anti-malware is all good, 

ip didn't change and the router settings are the same as they ever were,

there isn't another server running on this machine or port,

I don't have another router,

I've verified that my ISP is not blocking it.

I went through the server setup instructions just to make sure it checked out and it does.

I don't think any of that is likely to have occurred in the 3 minutes it took me to update my server though lol

Remote was working prior to updating and all the settings are exactly as they were when it worked, it was working just prior to me updating it this afternoon, just to clarify.

Is it possible to downgrade to the previous build?

[Happy2Play 9359]

54 minutes ago, Boodikii said:

I've verified that my ISP is not blocking it.

Are you saying a site like canyouseeme.org shows Emby port is open?

55 minutes ago, Boodikii said:

Is it possible to downgrade to the previous build?

Technically you have the previous version renamed to system.old in C:\Users\jesim\AppData\Roaming\Emby-Server.  So I can guess you can test that theory if previous version still works.

[Luke 39684]

Quote

I've verified that my ISP is not blocking it.

hi, how did you do that?

[Boodikii 5]

Okay I've figured this out.

So to elaborate, I ran that command from the article you posted to verify if my ISP is not blocking it.

The port website was giving me timeout errors, but my ports are open on every possible platform,

what resolved it was going into my network settings on Emby and reintroducing the path to the certificate .pfx file.

I am no longer getting timeout errors from that website and now I can connect remotely.

 

Thanks for your help~

Edited April 1 by Boodikii

[Luke 39684]

Thanks for following up.

[Boodikii 5]

3 hours ago, Luke said:

Thanks for following up.

Okay so a follow up to my follow up
(Not because I still have a problem, I did have one prompting me to come here again but I've resolved the issue with a brain-blast, and I don't want to bother you guys anymore, I'm sure you're busy and I appreciate that you've replied, but more for you guys to have some context at this point, maybe it'll help in some way?, Or for anybody who is experiencing this problem.)

I had gotten it to work last night, I was able to log in from an external network, simply remounting it was enough to let me log in remotely. it showed my port as open on that canyouseeme website, Emby showed that the port is open and running on my external port with the Domain address attached, however, upon waking up I found that I couldn't connect anymore even though everything looked exactly the same as it did when I went to bed and it was working.
so I tried restarting the server, restarting the server computer, remounting that .pfx again, remaking the .pfx with fresh files and using the new one, all with no results.

It was working pre-update, I got it to work post update. Everything looked right.
Turns out, for the first time in this router's life, the IPv6 changed. (I didn't notice it with a skim over, but, in my defense, it was like 4am.)
I'm like, 98% positive the update is the culprit and the way it interacted with my network upon implementing.
According to the logs in my router, the DNS error started around implementation.
But it explains everything as far as I can tell? Again I'm not network savvy and I could be way off base.
I imagine when I got it to work, that was really just me connecting to some sort of temp router network cache?

It's working now that I've swapped to the new IPv6 on my domain's dashboard that I got from my router's dashboard. I've tested it, my buddy a couple cities over tested it, my other buddy from across my city tested it. As of this moment, everything is Golden and it hasn't changed to a new IPv6, especially upon introducing multiple connections, so it doesn't seem like it will be a continuous problem.

Thank you both for your time and effort. It is much appreciated.