[Solved] AutoUpdate not running with SquidProxy (1 Viewer)

[offbyone]

No matter what you did, you still did not run the Autoupdate of Onlinevideos inside MediaPortal. It can easily be seen from the Onlinevideos.log -> LastWriteTime: 2012-10-15 19:38:31 for all siteutil dlls which was probably when you installed OV.

 

[2102Michael]

I believe I did no mistake -> In the .zip file you will find a Config.jpg which shows the OV settings window.. On this computer Online Videos has been installed in 2011 and worked perfect until 2 weeks ago.

What about this error?
[11-05 12:10:33,382] [OVInit ] [WARN ] Error on getting sites overview from server: System.Net.WebException: Fehler bei der Anforderung mit HTTP-Status 417: Expectation failed.
bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
bei OnlineVideos.OnlineVideosWebservice.OnlineVideosService.GetSitesOverview()
bei OnlineVideos.Sites.Updater.GetRemoteOverviews(Boolean force)
[11-05 12:10:33,387] [OVInit ] [WARN ] Error on getting dlls overview from server: System.Net.WebException: Fehler bei der Anforderung mit HTTP-Status 417: Expectation failed.
bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
bei OnlineVideos.OnlineVideosWebservice.OnlineVideosService.GetDllsOverview()
bei OnlineVideos.Sites.Updater.GetRemoteOverviews(Boolean force)

 

[offbyone]

Yes the error indicates that there is a problem connecting to the server.
But I am running the same version of OnlineVideos here locally and can connect fine to it. I don't know why you are getting the error - maybe your ISP changed or you are using a proxy on your router to connect to the internet now. I can only guess. But something with your network or PC setup must have changed.

 

[2102Michael]

It was an firewall issue. This is the information I got from my firewall specialist:


http-status 417 indicates a HTTP/1.1 request-header (Expect: 100-continue) when doing a POST, which is not supported by Squid-proxy.

You can configure squid to ignore this request-header, the client will fallback without even noticing it.

Just add this line to your squid.conf:

ignore_expect_100 on

So the problem is solved now - thank you for your support!