Search the Community

hi, Since the installation of my reverse proxy (dynamic DNS OVH) I manage to reach my server with firefox. But when I go to the application and put my URL the following error message appears. connection error ' Thank you in advance

Everything was working fine, and I noticed a few days ago that there were alerts, and all of them indicating that the check for application updates failed, and the check for the plugin updates failed. It used to work because I remember seeing the updates. Where do I start to look?

The scheduled tasks of updating application and add-ons is failing. This has happened serveral times in the past day or so. When I try and run it manually I get an error stating that the network path is not found. server-63631435452.txt server-63631440000.txt server-63631467681.txt server-63631471229.txt server-63631473274.txt unhandled_10b36f79-ae14-4c63-8f14-c9cf4a85b442.txt

Hii all Because the update process for the emby server (while it's running as a service) can be a bit annoying, so i made an application with a python script. It works no matter where it's located. You just have to unzip the *.zip file in the attachement. After that, in the unzipped folder run the "emby_update_v2.exe" as administrator. The application can be used with diffrent commandline arguments: /beta - Start normal with updating beta server, while its running as a service /dev - Start normal with updating dev server, while its running as a service /download - Start with downloading the regular version first /beta_download - Start with downloading the beta version first /dev_download - Start with downloading the dev version first /taskkill - Start with killing the process instead of stopping the service /debug - Start into the Debug Mode for debugging the functions. >> without an argument - start normal with updating the regular server, while its running as a service PLEASE NOTE: - The application normaly starts with the ability to stop the service at very first - If you know the service IS NOT running, start the application with one of the three 'download' arguments - If you have the Beta server service running, simply add the /beta argument in the commandline - If you have the Dev server service running, simply add the /dev argument in the commandline - If you have any kind of trouble, start the application with the /debug argument to try and/or debug functions Updater.zip

As per the subject line, this has recently started to happen when using MB Classic. Whenever I select an actor to see their information, the application exits. Under the new 3.0.27 beta, at least I get an "invalid application" error in Windows Media Centre. The problem does not manifest in MB Theatre, so I think something is up with my MB Classic. Has anyone else experienced this?