Jump to content

EMBY Suddenly not booting up - localhost refused connection


j_harrington

Recommended Posts

j_harrington

Hey guys,

 

I have been using my emby server all day today and everything worked fine as it always has. Suddenly the server cut out, my show stopped, and when I attempted to simply restart the server, I got connection refusals.

 

I tried uninstalling and re-installing. Nothing. I tried installing on top of a previous installation. Nothing.

 

I have attached the logfile I have at the moment. Please help! I love EMBY and I hate that it 'decided' to just break on me.

server-63599469110.txt

Link to comment
Share on other sites

hi, you could try rebooting your computer. to be honest, i think you might want to consider hardware diagnostics such as windows chkdsk as well.

Link to comment
Share on other sites

j_harrington

Hey Luke,

 

Rebooting did not work :(

 

I have tried uninstalling and re-installing and the setup wizard will not fire up either. I tried updating to Windows 10, same behavior.

 

I have experimented with moving to Plex and it just isn't as good an option for me as EMBY. Is there anything else you can do to help me?

 

It is the exact same behavior every time: localhost refused connection.

 

The only other thing I will say is that when the server boots the progress bar stops about 90% of the way across the splash page - I know that probably is not helpful but I thought I would throw it out there.

Link to comment
Share on other sites

j_harrington

The set-up wizard is now up!

 

Do you have any ideas on what might have happened within my system?

 

I was watching all day, interruption occurred (I thought it was just a web gateway interruption), then it just wouldn't connect to the localhost any longer.

 

Will I need to attempt the stable release sometime in the future?

Link to comment
Share on other sites

There was an issue with the new stable release for users with a quote in the installation path. That's been resolved on the beta channel.

Link to comment
Share on other sites

CBers

There was an issue with the new stable release for users with a quote in the installation path. That's been resolved on the beta channel.

How did that not get picked up in the dev and beta builds?

 

Do we not have enough testers these days?

Link to comment
Share on other sites

We have lots and lots of people running the pre-release builds, but most of them don't actually want to participate as testers and report issues.

Link to comment
Share on other sites

Happy2Play

How did that not get picked up in the dev and beta builds?

 

Do we not have enough testers these days?

How many testers have installs like OP "C:\Users\user's Laptop\AppData\Roaming\Emby-Server"?

Link to comment
Share on other sites

MSattler

How many testers have installs like OP "C:\Users\user's Laptop\AppData\Roaming\Emby-Server"?

 

That's right, bad users for going with a naming convention that Microsoft totally supports.

 

When in doubt, blame the users.  When you cannot blame them, then just go ahead and blame the testers who don't respond.

 

Hmm perhaps it's because when testers post stuff we get replies like "Thank you for testing pre-release" or a standard "How to report an error" post.

 

If I had a nickel for every post with an issue that get's ignored I could afford a lifelong Plex subscription.

  • Like 1
Link to comment
Share on other sites

How many testers have installs like OP "C:\Users\user's Laptop\AppData\Roaming\Emby-Server"?

 

Probably a decent number of people, but most will just find their own workaround, which is usually installing stable.

Link to comment
Share on other sites

Hmm perhaps it's because when testers post stuff we get replies like "Thank you for testing pre-release" or a standard "How to report an error" post.

Actually we are in here all day long helping people, and I think everyone can see that. Ebr and I make a genuine effort to make sure that everyone gets responded to. Sometimes there will be more difficult questions that will sit in my queue for a few days, but they are never ignored.

 

There are two reasons why I respond with those thank-yous - the first being that we are genuinely thanking them for taking the time to run a test build and report their issue. The second is that many users will often forget they're running pre-release and over time their expectation levels gravitate back towards expecting a fully stable product when they are in fact running a test build. So it is there to remind them and hopefully re-calibrate their expectations of what pre-release is and what it is not.

  • Like 2
Link to comment
Share on other sites

MSattler

 

 

There are two reasons why I respond with those thank-yous - the first being that we are genuinely thanking them for taking the time to run a test build and report their issue. The second is that many users will often forget they're running pre-release and over time their expectation levels gravitate back towards expecting a fully stable product when they are in fact running a test build. So it is there to remind them and hopefully re-calibrate their expectations of what pre-release is and what it is not.

 

The problem is you say it so much, and you say it to some of the most valuable testers over and over.  Those are the people getting frustrated, and then see your reply as a smart-ass reply, and then become less wiling to post with shit.

 

If it's someone who has posted 5 times, fine remind them.  But someone with 400+ posts who is constantly posting, I'm pretty sure they are aware what they are running.

 

At least this bug fix actually made it into the release notes!

Link to comment
Share on other sites

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