Jump to content

Why does an Emby server outage make my emby very slow?


Go to solution Solved by ebr,

Recommended Posts

Posted

I would like somebody to answer this question for me. I purchased emby premier and I have been very happy with it. I don't have any Internet outages, but the outage today really made my emby server slow. It was so bad that everything was delayed.

 

When I open my Nvidia Shield I would get the Circle of Death just spinning period after a couple minutes my emby client would finally connect. But then when I went to navigate the menus it was slow.

 

I guess the thing that disappoints me is that I purchased emby so I wouldn't have to rely on an internet connection. So if for some reason I lost the internet I could still use my local emby server. With this latest outage I have learned that that is not the case. There is no reason why my emby server should be slow if the internet emby servers are down. I would think that my emby server, since it's local, would be unaffected. If I knew this was going to happen I would have considered Plex.

 

And this isn't a isolated incident. I went on the Plex Discord server and others were having the same challenge. Is this something that is going to be fixed?

 

Sent from my SM-G955U1 using Tapatalk

Posted

Hi, yes we will look at improving this so that you won't have to worry about it anymore. Thanks.

  • Like 1
Posted

Hi, yes we will look at improving this so that you won't have to worry about it anymore. Thanks.

Thank you Luke. I appreciate your efforts to make emby the best it can be. Can you give me an idea as to when we can expect a fix for this? I guess as long as this exists, I am always going to be a little leery of another denial-of-service attack bringing my emby down.

 

Sent from my SM-G955U1 using Tapatalk

Posted

Thank you Luke. I appreciate your efforts to make emby the best it can be. Can you give me an idea as to when we can expect a fix for this? I guess as long as this exists, I am always going to be a little leery of another denial-of-service attack bringing my emby down.

 

Sent from my SM-G955U1 using Tapatalk

 

As you should be DRM like this is BS and useless. They claim to be here for "us" waving there open source "flag" around. When really they're  to be worse than plex.

2018-09-06 17:49:30.865 Info HttpServer: HTTP Response 500 to 10.0.250.137. Time: 3ms. http://10.0.3.1:8096/emby/Packages/Updates?PackageType=UserInstalled 
2018-09-06 17:49:37.381 Error HttpClient: Connection to https://mb3admin.com/admin/service/registration/validate timed out
2018-09-06 17:49:37.386 Error SecurityManager: Error checking registration status of MBSupporter
	*** Error Report ***
	Version: 3.5.2.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Unix 4.9.0.7
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Processor count: 10
	Program data path: /var/lib/emby
	Application directory: /opt/emby-server/system
	MediaBrowser.Model.Net.HttpException: Connection to https://mb3admin.com/admin/service/registration/validate timed out ---> System.OperationCanceledException: The operation was canceled.
	   at System.Net.Http.HttpClient.HandleFinishSendAsyncError(Exception e, CancellationTokenSource cts)
	   at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
	   --- End of inner exception stack trace ---
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
	   at Emby.Server.Implementations.Security.PluginSecurityManager.GetRegistrationStatusInternal(String feature, Boolean forceCallToServer, String version, CancellationToken cancellationToken)
	MediaBrowser.Model.Net.HttpException
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
	   at Emby.Server.Implementations.Security.PluginSecurityManager.GetRegistrationStatusInternal(String feature, Boolean forceCallToServer, String version, CancellationToken cancellationToken)
	InnerException: System.OperationCanceledException
	System.OperationCanceledException: The operation was canceled.
	   at System.Net.Http.HttpClient.HandleFinishSendAsyncError(Exception e, CancellationTokenSource cts)
	   at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
	   at System.Net.Http.HttpClient.HandleFinishSendAsyncError(Exception e, CancellationTokenSource cts)
	   at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)

Emby became unusable again, thanks to the server issue.

Posted

I have to agree. This is DRM at its finest.

 

Sent from my SM-G955U1 using Tapatalk

Guest asrequested
Posted

It does beg the question if something catastrophic happens to the Emby server (eg natural disaster), this would pretty much screw every one of us.

 

I would be willing to pay for an unrestricted license. That is completely standalone. If I were paying a monthly subscription, then I would expect something like this. But as a lifetime, it really isn't acceptable. I know this has been discussed, and will continue to be. Because it isn't a good thing. I accept that piracy is an issue, but we should at least have the option to buy a license that doesn't require a phone home. I feel like I'm renting, not owning. And I don't like renting anything.

  • Like 1
Posted

We are looking at improving it,  thanks guys.

  • Like 1
BAlGaInTl
Posted

It does beg the question if something catastrophic happens to the Emby server (eg natural disaster), this would pretty much screw every one of us.

 

I would be willing to pay for an unrestricted license. That is completely standalone. If I were paying a monthly subscription, then I would expect something like this. But as a lifetime, it really isn't acceptable. I know this has been discussed, and will continue to be. Because it isn't a good thing. I accept that piracy is an issue, but we should at least have the option to buy a license that doesn't require a phone home. I feel like I'm renting, not owning. And I don't like renting anything.

 

I'm of a similar opinion.

 

I bought a lifetime license, and then added additional users (also lifetime).

 

Although this didn't affect me directly, it makes me worry about what would happen if the servers were down for an extended period.

 

@@Luke, Can you share in what ways you are looking to improve it?

  • Solution
Posted

I accept that piracy is an issue, but we should at least have the option to buy a license that doesn't require a phone home. 

 

We are looking for ways to streamline this as much as possible but the first part of that sentence contradicts the second part.

 

If you accept that we need to protect against piracy of our software, then you understand that it isn't currently possible to have something that can run without ever having to be validated.

 

In the end, the only impact here was some unacceptable slowness due to time outs trying to reach our servers.  This only impacted some people and did not make the apps not work (playback was still allowed).

 

So, we just need to refine how long we are willing to wait in a situation like this so that you don't see a slow down.  In the case where the network is truly not available, everything is fine and you don't see a slowdown because the network calls fail very quickly. 

Posted (edited)

We are looking for ways to streamline this as much as possible but the first part of that sentence contradicts the second part.

 

If you accept that we need to protect against piracy of our software, then you understand that it isn't currently possible to have something that can run without ever having to be validated.

 

In the end, the only impact here was some unacceptable slowness due to time outs trying to reach our servers.  This only impacted some people and did not make the apps not work (playback was still allowed).

 

So, we just need to refine how long we are willing to wait in a situation like this so that you don't see a slow down.  In the case where the network is truly not available, everything is fine and you don't see a slowdown because the network calls fail very quickly. 

 

You would need to know the users MAC address of the machine. Then in theory you could "create" maybe on the fly a download of emby server that would be allowed only on that one machine with that specific mac address when the internet is down. That part would need to be in some binary blob, without sources available, and required to be used when the internet is down and can't verify the normal way. This would prevent the piracy. When online, you could tell the MAC address isn't the same as the first install and block features from the cloned copy. But somebody would eventually "crack" that blob and how the MAC addresses were encrypted/hashed/salted/stored, but that would take alot of time. You could make it lock down to a certain MAC address once the install is made on the server, and have the server not start without internet if this doesn't match. Since you embed the MAC address of the machine into the binary at install it would make sharing harder. You have to crack what the installer does to the binary and it gets involved. This is possible to do. People with multiple servers used with their license would need 2, possibly 3 MAC addresses allowed. You could do this as they speak up, or otherwise. It can be done.

Edited by speechles
Posted

We are looking for ways to streamline this as much as possible but the first part of that sentence contradicts the second part.

 

If you accept that we need to protect against piracy of our software, then you understand that it isn't currently possible to have something that can run without ever having to be validated.

 

In the end, the only impact here was some unacceptable slowness due to time outs trying to reach our servers. This only impacted some people and did not make the apps not work (playback was still allowed).

 

So, we just need to refine how long we are willing to wait in a situation like this so that you don't see a slow down. In the case where the network is truly not available, everything is fine and you don't see a slowdown because the network calls fail very quickly.

This simply not true on multiple levels, first as I've already point out many BIG companies don't require and DRM for thier software. And piracy doesn't seem to be an issue for them..

 

Secondly playback was an issue for some of us as the art covert plugin crashing made the rokus error out instead of playing videos.

 

 

So i ask why not just remove all the drm ?

Posted

You would need to know the users MAC address of the machine. Then in theory you could "create" maybe on the fly a download of emby server that would be allowed only on that one machine with that specific mac address when the internet is down. That part would need to be in some binary blob, without sources available, and required to be used when the internet is down and can't verify the normal way. This would prevent the piracy. When online, you could tell the MAC address isn't the same as the first install and block features from the cloned copy. But somebody would eventually "crack" that blob and how the MAC addresses were encrypted/hashed/salted/stored, but that would take alot of time. You could make it lock down to a certain MAC address once the install is made on the server, and have the server not start without internet if this doesn't match. Since you embed the MAC address of the machine into the binary at install it would make sharing harder. You have to crack what the installer does to the binary and it gets involved. This is possible to do. People with multiple servers used with their license would need 2, possibly 3 MAC addresses allowed. You could do this as they speak up, or otherwise. It can be done.

 

That doesn't address the device limits...

 

However, we think we've come up with a method that would not cause any disruption in a situation like we had the other day so this will be improved.

Posted

So i ask why not just remove all the drm ?

 

I thought we had made that clear but, the short answer is because people steal.  And, if enough people steal, then we don't stay around and you don't have Emby at all :).

Posted

That doesn't address the device limits...

 

However, we think we've come up with a method that would not cause any disruption in a situation like we had the other day so this will be improved.

 

Agreed. When offline the device limit of course could be easily exceeded. But you would prevent the piracy of your main product. But then someone would just keep their server offline you are saying, and free lunch for all their 10,000 users on the pay TV service. I do agree. And this is why we cannot have nice things. But it seems ill to punish the innocent, for the guilt of a few (for lack of better words) complete a$$hole$. $ implied to mean the do it to enrich themselves through piracy. Those rich sob's should not cause harm to the consumer. But in this economy, the way prices fall and the way income levels are not in any way even, the poor and rich have such a divide. That piracy becomes a necessity for some areas. Those might be brazlilians stealing emby over the device limit. They have no other way, they profit to enrich their little area of town. With free internet, cable TV, and such. It might seem piracy to you, but to those poorer economies the realities of emby servers for-profit-motto are restricting the freedoms of consumers. Just the reality. Until you are okay with losing a few dollars from the poor who otherwise may not eat for a day or two if they were to pay you, and let them just have their little piracy ring. You are hurting us, more than you are them. Thats the true reality.

Guest asrequested
Posted

If you accept that we need to protect against piracy of our software, then you understand that it isn't currently possible to have something that can run without ever having to be validated.

That's not what I said or implied. I'll be more specific. I accept that piracy is a consideration, but we shouldn't be paying for a product that has a restricted license. As is, we can only use our purchased product as long you allow it.

 

Here's a question. If your server is inaccessible for longer than a month, two months, three months. Will we lose the use of the software we've paid for?

Posted

I thought we had made that clear but, the short answer is because people steal.  And, if enough people steal, then we don't stay around and you don't have Emby at all :).

 

I get it.  At this point, I would be happy with fixing things up to the point that a server outage on Emby's side doesn't adversely affect a product that I paid a lifetime subscription for.  As I mentioned before, the main reason I didn't go with Plex was that I could install and maintain everything locally.  Now that I learned that isn't the case in this last outage, I feel that the Emby devs can and will take action.  You guys have been awesome at listening to the community and I have faith that you guys will figure something out.

Posted

That's not what I said or implied. I'll be more specific. I accept that piracy is a consideration, but we shouldn't be paying for a product that has a restricted license. As is, we can only use our purchased product as long you allow it.

 

Here's a question. If your server is inaccessible for longer than a month, two months, three months. Will we lose the use of the software we've paid for?

 

If that were to ever happen, then we would do our best to find a way to get around it (long before month(s)).

 

And, just as a point of fact, unless you wrote it yourself, you have never "owned" a piece of software from anyone.  You have always purchased a license to use the software in some limited fashion.  That is how software must be treated and always has been.  

 

In any case, as I already stated, I think we have a solution to the issue that was encountered this week.

Posted

I get it.  At this point, I would be happy with fixing things up to the point that a server outage on Emby's side doesn't adversely affect a product that I paid a lifetime subscription for.  As I mentioned before, the main reason I didn't go with Plex was that I could install and maintain everything locally.  Now that I learned that isn't the case in this last outage, I feel that the Emby devs can and will take action.  You guys have been awesome at listening to the community and I have faith that you guys will figure something out.

 

Thanks and, yes, we already have a plan we think will make what happened this week not happen again.

Guest asrequested
Posted

If that were to ever happen, then we would do our best to find a way to get around it (long before month(s)).

 

And, just as a point of fact, unless you wrote it yourself, you have never "owned" a piece of software from anyone. You have always purchased a license to use the software in some limited fashion. That is how software must be treated and always has been.

 

In any case, as I already stated, I think we have a solution to the issue that was encountered this week.

And once again, we aren't talking about intellectual property. But ok, I own the license. Let's go with that. In this instance, the license I've bought, I don't appear to own. As it's useless without your server granting that use. There are multiple ways in which that could fall down. It's tied to an identity that we have to create with an email address. What if something outside of our control, destroys that? Let's say we use a free crappy email account, that is only used for this purpose. So we never check that email. And then that email service disappears for whatever reason. We wouldn't know, but now the Emby identity is toast. What happens?

Posted

I thought we had made that clear but, the short answer is because people steal. And, if enough people steal, then we don't stay around and you don't have Emby at all :).

As clear as mud. It's not stealing it's copy right infringement. And the only way some one could infringe on your software is if they didn't comply with the gpl version. I think emby needs to make up it's mind I'd it's really an open source project or not.

 

 

And still using your word "stealing". The people who have and would buy it still will. Drm does not it increase Revenue full case study have repeatedly proven this. case in point the music industry is still thriving, solo aetists with out labels are making it, the software industry it self asa whole is thriving, hell a lot of asia (and the rest of the world) "pirates" windows and there doing fine.

 

The emby team really should take a few economics and at least a beginners course on statistics. Then really evaluate wether drm really makes sense. No really, how much time, effort and additional costs ( hosting/domain name/etc ) go into maintainging drm VS the money your "not losing" because of it.

  • Like 1
Guest asrequested
Posted

And I'm sure you guys enjoy having to keep going over this. I don't see us complaining about it, ever going away.

  • Like 1
Posted (edited)

And I'm sure you guys enjoy having to keep going over this. I don't see us complaining about it, ever going away.

 

Yep pretty much this. As a paying customer and someone who works in IT and has to deal with many forms of it, I will complain about DRM till the day I die. It does nothing for me but cause problems and downtime. 

 

 

I am very sad to hear the Emby's DRM is so intrusive. Even if they do fix the slowness issues why does it need to call home every so often, is that really necessary?  What if I want to use Emby completely offline? Is that even possible? Isn't emby Open source, what is stopping someone from just removing the DRM code? Doesn't that just completely defeat the DRM no mater how advanced they make it? If so why make it so intrusive. Why can't we just validate codes once on life time memberships and once a month when a monthly membership expires and needs to be check for a renewal?

Edited by Catsrules
Deathsquirrel
Posted

If the system is changed such that it doesn't impact legitimate users then really, what difference does it make?  Almost all commercial software validates its license with the manufacturer at startup in some fashion or is machine-locked.  Software licensing and auditing was my business for the last decade.  This is not at all unusual and it's not going away.

 

Asking that the solution be able to survive a site outage is reasonable and they complied.  Asking that they remove the license validation isn't going to happen and is a waste of your time.

Posted

Asking that they remove the license validation isn't going to happen and is a waste of your time.

 

I disagree. If typing a rationale for your opinion is a waste of time, why are any of us posting in any threads?

 

A waste of time is adding that as the last line on your post. Nothing is a waste of time. Everything happens for a reason.

 

When things don't happen, it is either arrogance, jealously, or just plain ignorance. People expect money to mean something. In embys case, without internet, or some way for ET to phone home, your money is a waste. Time is a waste. Emby is a waste of time. That's in effect what you are saying...

Guest
This topic is now closed to further replies.
×
×
  • Create New...