Jump to content

Check for application updates failed


Recommended Posts

Posted

Getting a couple of errors and wondered if it was at the server at fault or updates not working from the Emby servers.

 

Check for application updates failed

Check for plugin updates failed

 

Getting both for the past day or so.

 

 

Posted

We are not aware of any issues on our end.

Posted

Not sure then. I only have the collections and Mediaportal. No logo when I look in plugins on either of them. When I tried to view the catalogue it just gave the spinner.

Posted

That is another indication that you are unable to reach our servers.

 

Check firewall settings.

Posted

Checked the rules and they are in both inbound and outbound and open.

 

I've not changed anything on the server other than moving the metadata from C: to D: and what a right royal PITA that was!

 

The times it started was before I even started the data move though. Could it be due to Emby not being able to contact the servers for a few days? My ISP was down from Sat - Mon.

Posted

I'd say post a log but I know what we will see.  There will be a bunch of errors about not being able to get to our servers.  The only question will be is it universal - meaning can you also not get out to tmdb etc.

 

If you look in the log, pay attention to the message as to why it says you can't reach them.  Is it a time-out, or a dns error or what.

 

You may need to re-boot some things (like your router or cable interface or machine).

Posted

I just got on the server via http://app.emby.media/from the my works network and it's picking it up fine. 

 

I'll try changing the DNS servers when I get home and give the router a reboot.

 

Thanks for the suggestions.

Posted

For the past couple of days I've received the following error:

Check for plugin updates failed.
3 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
Check for application updates failed.
3 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
Check for plugin updates failed.
10 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
Check for application updates failed.
10 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
Check for application updates failed.
31 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo',
 
I've restarted my modem/router to no avail.
 
Posted

 

For the past couple of days I've received the following error:

Check for plugin updates failed.
3 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
 
Check for application updates failed.
3 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
 
Check for plugin updates failed.
10 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
 
Check for application updates failed.
10 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo', got string starting with:
 
Check for application updates failed.
31 minutes ago
Type definitions should start with a '{', expecting serialized type 'PackageInfo',
 
I've restarted my modem/router to no avail.
 

 

 

Yes that was the error.

 

I ended up doing a full reinstall as nothing I tried fixed it. 

 

I tried....

 

Firewall rules

Router ports

Running Emby server installer

Removing the plugins

 

And...

 

Swearing at Emby! (last resort before reinstall)

Posted

Try turning off all Anti-virus/anti-malware stuff.  Looks like something is mangling the input.

Posted

I tried that ebr but with no joy.

 

It's all done now apart from trying to sort out a bit of eye candy on the live tv icons in the home view and the https (refuses to work)

Posted

Was getting the same error but on Ubuntu, solution was the same, complete removal and reinstall.

Posted

Just got this error myself for the first time this morning on 1 of my Debian servers. DNS is fine and resovles. No firewall or networking setting have been chnaged in the last 72 hrs. Only thing that's chnaged is I updated this servers copy of emby to the lasted beta and my other windows servers didn't get this error last night.

Posted

Reinstalling the emby server worked for me.

I did not uninstall the server. I simply reinstalled the server and now the errors stopped.

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