No longer accessible after last update

[Silentwidow 1]

Hey guys, Ive been using Emby for what feels like a year now, maybe. 

 

Anyway, It's been running flawlessly until the last update that updated it to Version 3.2.34.0

 

Remote access no longer works, I have tried changing the port from the default 8096, have tried the HTTPS port(Though I doubt that works without a cert). 

 

Port just does not open. 

 

I have multiple servers including a Plex server, a teamspeak server, and a Rust server, and have had those for a while, and they are all still functioning. It's only Emby. 

 

Any ideas? 

 

Edit: Attached Log

Emby Log.txt

Edited October 25, 2017 by Silentwidow

[Luke 42085]

Hi there, can you attach an emby server log? you can learn how to do that here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks.

[mastrmind11 722]

Same as this?  https://emby.media/community/index.php?/topic/52181-cant-access-via-http-locally-after-upgrade-to-32340/

[Luke 42085]

What exactly is the problem? You say it's no longer accessible, but in this log you were able to browse to the logs section of the server dashboard to get a log file.

[Silentwidow 1]

Mastermind, mine is fine locally. It's only remote I'm having issues. 

 

Luke, I have attached the log

server-63644529689.txt

[Silentwidow 1]

What exactly is the problem? You say it's no longer accessible, but in this log you were able to browse to the logs section of the server dashboard to get a log file.

 

Remote access is not functioning. 

 

I have rebooted my server, my switches, and my router/modem. 

 

It's only Emby that is not working remote, Plex, RUST, TeamSpeak are all functioning as intended remotely. 

[ebr 16190]

Remote access is not functioning. 

 

I have rebooted my server, my switches, and my router/modem. 

 

It's only Emby that is not working remote, Plex, RUST, TeamSpeak are all functioning as intended remotely. 

 

This is almost always a local network configuration issue.  Check your firewall, router port forwarding, that the IP address has not changed etc.

 

The Firewall will sometimes automatically create blocking rules after an update.

[Silentwidow 1]

FIgured out what caused it, apparently IPV6 was enalbed on my server, and it somehow picked up an IPV6 address, turning off IPV6 for it seems to have resolved the issue. 

 

Thanks all. 

[Luke 42085]

Thanks for the feedback.

[AmericanCrisis 28]

Today this problem began for me as well.  I've gone practically two years on cruise control with Emby Server.  Remote login for Emby has worked flawlessly for over a dozen clients.  Now all of a sudden remote clients don't have access at all.  They don't have access whether or not using Emby Connect.  I have a hostname through no-ip.  This is frustrating!!!

[Luke 42085]

Today this problem began for me as well.  I've gone practically two years on cruise control with Emby Server.  Remote login for Emby has worked flawlessly for over a dozen clients.  Now all of a sudden remote clients don't have access at all.  They don't have access whether or not using Emby Connect.  I have a hostname through no-ip.  This is frustrating!!!

 

Hi @, we're sorry to hear about your issue. It could be for any number of reasons. Please attach the information requested in how to report a problem. thanks !

[AmericanCrisis 28]

Hi @, we're sorry to hear about your issue. It could be for any number of reasons. Please attach the information requested in how to report a problem. thanks !

 

Yeah I totally understand that.  There was an Emby update and a huge Windows 10 update all in the same day on my server.  So it is either one or the other.  Considering I am unable to use my no-ip hostname to connect via Windows Remote Desktop after this update, I'm leaning towards a windows problem.  

[Happy2Play 9783]

Yeah I totally understand that.  There was an Emby update and a huge Windows 10 update all in the same day on my server.  So it is either one or the other.  Considering I am unable to use my no-ip hostname to connect via Windows Remote Desktop after this update, I'm leaning towards a windows problem.  

 

Depending on how you updated there could be firewall issues with transition to net core build.  I just updated witth installer and had to acknowledge new firewall rules.

 

https://emby.media/community/index.php?/topic/50012-emby-server-for-net-core/?p=504467

Edited October 29, 2017 by Happy2Play